The debug option tells the system to "log up to" syslog.DEBUG, instead of
the default. So, more information is kept in the log. I don't have a
Raspbian machine around me right now, but I would be surprised if it
changed the destination.
In any case, it's a better idea to look at /var/log/syslog,
As asked earlier in this thread I changed debug=0 to debug=1 in
weewx..conf. From then it started to log to /var/log/weewx.log.
I thought this was the normal behaviour? Before, when debug=0, it all was
logged to /var/log/syslog.
I am a bit confused now on what to show you here from what logfile.
It looks to me that neither of these last two log excerpts correspond with
the earlier ones you posted. The first is the wrong date (the crash
happened on the 24th, not the 25th), and the second is too early in the day.
I'm surprised you are not seeing weewx entries in /var/log/syslog. Did you
Hi Thomas.
We are looking at /var/log/weewx.log
This is the output of /var/log/syslog around the time of the first error
Dec 25 17:11:51 Grandix rngd[526]: stats: entropy added to kernel pool:
724608
Dec 25 17:11:51 Grandix rngd[526]: stats: FIPS 140-2 successes: 39
Dec 25 17:11:51 Grandix
Could be a systemd issue. Perhaps your RPi was low on memory, and systemd
had to kill weewxd?
Things to try:
1. Which log are we looking at here? If it's a systemd issue, it should
have told us that it is killing a process. But, not all logs show all
messages, so it's possible that the systemd
1. I obeserved this until now and had some time without errors. But
suddenly on Christmas Eve there they were again. The system is installed on
a fresh SANDISK sd-card with latest weewx on a RPi B. In my log file I find
this:
Dec 24 17:15:22 Grandix weewx[629]:
On Monday, November 4, 2019 at 1:35:30 AM UTC-8, Franklin Bockstael wrote:
> The uptime is not so important I guess. Everytime this error occurs the pi
> becomes unresponsive and I have to reboot. Iti s not a real long time that
> it is on because this happens sometimes twice a day and then not
Hi Susan,
Also thanks for responding.
I can't recall I did something more last time then just rebooting and
starting weewx.
Now I see this:
*pi@Grandix:/home/weewx $ ps -C weewx | wc -l*
*1*
There is just one weewx process running at this moment.
How could it be possible that other weewx
Hello Vince,
Thanks for responding.
The uptime is not so important I guess. Everytime this error occurs the pi
becomes unresponsive and I have to reboot. Iti s not a real long time that
it is on because this happens sometimes twice a day and then not for a few
weeks.
I turned on debug now and
Also note that the process ID changes at that point as well (614 to 558)
Further there is another change of process ID to 583, then one entry of 475
and back to 583.
I'd say you have multiple sessions running.
Susan
--
You received this message because you are subscribed to the Google Groups
On Sunday, November 3, 2019 at 10:36:39 AM UTC-8, Franklin Bockstael wrote:
>
>
> Everyting is fine and suddenly we go back in time from 21.25 to 21.17 as
> if a second session of weewx is starting.
>
The clock going backwards and the process id going down looks to me like
your pi rebooted on
11 matches
Mail list logo
