mesh-watcher: read the working program's journal each round; a stuck read is a finding #733
@@ -23,6 +23,12 @@ without that read on each machine the module is wanted on.
|
||||
Loop: wait with `mesh_wait` on the event family (its answer only wakes you), then read the state from the verb
|
||||
the handover names; never report a state you did not read in that round.
|
||||
|
||||
**A state that does not change is not "nothing happened".** A reservation, a queue or a key can stay as it was while
|
||||
the work behind it already failed. Each round, also read the journal of the program that does the work
|
||||
(`<node>/node-service-manager.journal` with its unit, the last lines since your previous read) and report any failure
|
||||
line word for word. A verb that times out or refuses twice is a finding of its own: report it at once, never read
|
||||
around it. You have no clock: take times from the tools' answers, never guess them.
|
||||
|
||||
**A report along the way does not end you.** Your final message ends you, and then nothing watches. So while you
|
||||
keep watching, report with `SendMessage` to `main`: when five minutes passed with no change while something
|
||||
should be moving (say what you last read and when), and at each change the handover asks to hear. Then go on
|
||||
|
||||
Reference in New Issue
Block a user