Graphs not updating

[michael form]

I have Weewx 3.9.2 running on a Raspberry Pi 3 using the Debiam install. Until this morning, everything was working fine. When I went to look at the web page this afternoon, the system was unresponsive. This included the Pi itself. I rebooted the system and it came up OK but now the graphs on the web page are not updating, although it seems that the sensors are sending back valid data, that is the temperature readings are reasonable and the date and time are correct. However, the graphs are not updating and are stuck at around 3:00 AM this morning, which is when the system seems to have stopped. 

I have no idea on why things got stuck, as the system has been running without a problem for over a month. The problem could be with the Pi and/or Raspbian, but that does not explain why everything rebooted and is working except the plots.

Any ideas on where to look?

Thanks.

Michael

[Tom Keffer]

Impossible to say with the limited information you're giving us. At a minimum, how about the type of station, and the log?

See the Wiki article Help! Posting to weewx-user.

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e2d9a7dc-0cd1-4013-a817-2d58123b16deo%40googlegroups.com.

[michael form]

I have attached a section of the syslog file. Somewhere around 3:13:54 AM on 20 June the system seems to have lost track of the time. If you need me to supply a more detailed log with debug=1, let me know.

The station type is USB using a DS9490 USB to 1-Wire interface with OWFS.

I have confirmed that the Pi has the correct date and time and that the database has current correct values even though the graphs/plots are not updating.

Questions:

1. How to get the plots to update correctly now that the system has been rebooted?

2. Why did the system get confused with the time? This is probably more difficult to answer. How to prevent this in the future, if possible?

Thanks.

Michael

On Sunday, June 21, 2020 at 3:01:59 PM UTC-4, Tom Keffer wrote:

Impossible to say with the limited information you're giving us. At a minimum, how about the type of station, and the log?

See the Wiki article Help! Posting to weewx-user.

On Sun, Jun 21, 2020 at 11:45 AM michael form <mike...@gmail.com> wrote:

I have Weewx 3.9.2 running on a Raspberry Pi 3 using the Debiam install. Until this morning, everything was working fine. When I went to look at the web page this afternoon, the system was unresponsive. This included the Pi itself. I rebooted the system and it came up OK but now the graphs on the web page are not updating, although it seems that the sensors are sending back valid data, that is the temperature readings are reasonable and the date and time are correct. However, the graphs are not updating and are stuck at around 3:00 AM this morning, which is when the system seems to have stopped. 

I have no idea on why things got stuck, as the system has been running without a problem for over a month. The problem could be with the Pi and/or Raspbian, but that does not explain why everything rebooted and is working except the plots.

Any ideas on where to look?

Thanks.

Michael

--
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 weewx...@googlegroups.com.

[Tom Keffer]

1. Just delete the plots. They will all get regenerated.

2. You had the classic "no clock" symptoms: when the reboot happened, the system started with the last time it had saved, which was hours old. This always causes unpredictable results. See the wiki article Raspberry Pi.

It's well worth spending the $5 and installing a realtime clock.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a05202cc-820c-4f37-989d-a23cef4182eco%40googlegroups.com.

[michael form]

I just checked and things seem to be working once  again. However, data is missing around 03:00 yesterday until around 14:00 today. I was planning on installing the RTC but saw no need since I assumed that the system would get the correct time from a time server. This, evidently, was an incorrect assumption. Do you have any idea on why this did not happen? Why did it take so long to begin displaying "correctly" again. I would have thought that it would start up right after the reboot. Does Weewx itself query a time server or do I have to explicitly do this? 

Speaking of "explicitly", I wanted to explicitly thank you and other  group members for their help for those of us that need it. Thank you.

Michael

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a05202cc-820c-4f37-989d-a23cef4182eco%40googlegroups.com.

[vince]

On Sunday, June 21, 2020 at 3:54:56 PM UTC-7, michael form wrote:

...saw no need since I assumed that the system would get the correct time from a time server.

 [...]

 I would have thought that it would...

Not usually a good move to assume anything.   You have to understand how the computer you're running on does (or does not) achieve accurate time.

On a Raspberry Pi I'd suggest doing both A+B on the link Tom provided.   If you install+enable+start ntpd, then the systemd time daemon stuff gets superseded with something that actually works.   Disabling the fake-hwclock thing better ensures that the system doesn't try to save a (possibly bogus) time and reinitialize to that on the subsequent power-up.

If your pi never takes a power down/up, the software solution usually works ok, but a RTC would belt+suspenders things even more.

[michael form]

I am not sure why the Pi would restart as it is powered by a UPS so the issue is somewhat of a mystery why it got confused. A second Pi, also running Weewx, powered by the same UPS did not run into any problems. In any event, I have ordered two RTC modules and will install them on the two Pis when they arrive later this week and hopefully, the problem will never come up again.

Thanks for your response.

Michael

[Glenn McKechnie]

On 22/06/2020, michael form <mike...@gmail.com> wrote:
> I am not sure why the Pi would restart as it is powered by a UPS so the
> issue is somewhat of a mystery why it got confused. A second Pi, also
> running Weewx, powered by the same UPS did not run into any problems.

Have a look in syslog (or syslog.1 or older gz file) and see if there
is a hint in there.
It may have run out of memory in which case they will reboot if the
memory killer can't resolve it.


--


Cheers
Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie