G'day Gary,
If you look closely at the PID you'll see that the log I posted ( in my
opening email ) had weewx running on [56*5*].
The rasp pi is running headless, so I simply ssh'd into it and issued a
('sudo reboot' command). If you look closely at the second log, you'll see
it running on PID [56*4*] ( you can't get any closer than that :-) ). Plus
if you look at the new log you can see the actual rasp pi booting up and
the relevant timestamps kicking in.
I really think that everything is ok now. My guess ( as per prior email )
is that the clean out of the archive fixed this issue.
Cheers mate.
Benjamin
ps. BTW: It's been running now for 50 minutes and still going strong. I'm
tailing the log still and nothing untoward is appearing in the logs.
On Monday, January 15, 2018 at 8:40:22 PM UTC+11, gjr80 wrote:
>
> I'm not sure everything is fine, well at least not according to the log
> extract you posted. Did you stop then start weeWX and post the log extract
> from when you started weeWX or did you maybe post an old log extract? The
> reason I ask is that weeWX is running with process id 564 from before your
> ntp synced, if weeWX was stopped then started it would have a new process
> id.
>
> Gary
>
--
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.
