Thanks everyone.

Some responses:
- the log I showed in the OP was from journalctl - thanks for the 
suggestion though
- I didn't think that weewx as doing something special during the 
'genStartupRecords' step but I just wanted to check
- I did Google those messages and (as with the replies here) they so often 
degenerate into a 'systemd is bad/dumb/<expletive>' argument without 
addressing the underlying issue/questions being asked; also running the 
latest Rasbian versions you don't really have a choice as the SysV init 
files are used to dynamically create the service files - that is why I 
created my own as the conversion did not do any of the required dependency 
checking.
- weewx *is * being stopped and started again as the snippets of  the log 
show - and there is only one process with weewx running in it on the system 
as a 'ps -aux' shows
- learning what I can about systemd, I suspect that the message about 
monitoring the PID file is a bit misleading; it would appear to come up 
when systemd finds a PID file already in existence but the process not 
running and restarts a new process - the new PID file does hold the new 
Process ID and the PID reported is the correct new one
- mwall - the thread you referenced has my comments in it already; the key 
difference is that the original question there does not reference any error 
messages before the crash - at least I'm getting that one about the holdoff 
timer (even if I still don't understand why). Also the system  itself keeps 
running in my case rather than what appears to be a (silent) system crash

So the question now seems to be why systemd is not detecting (on its own) 
that weewx is running while it is reading the historical records, but is 
detecting that it is running once that is complete?

Back to the books (err Google searches).

Thanks all

Susan

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to