Thanks for that Tom, I have no doubt that you are correct....as usual. I will dig around as you propose and see what I can find.
On Sunday 1 September 2024 at 12:10:14 UTC+12 Tom Keffer wrote: > Monica: you're going to have to do a little investigation. Take a look in > /home/weatherpi/backup_weewx.sh. Anything in there that could cause a > weekly reboot? > > Also the path /etc/cron.weekly is a directory. You'll have to look inside > for any files. Could any of them cause a weekly boot? > > How about the file /home/weatherpi/camera_image1.sh? > > I encourage you to do a little investigative forensics on your computer. > It's hard to diagnose these remotely. > > I could be wrong, but I really doubt this is a weewx problem. It's > something specific to your computer. > > -tk > > On Sat, Aug 31, 2024 at 5:05 PM Monica Mulholland <[email protected]> > wrote: > >> Thank you for that. Here the screenshot of the files. >> >> On Sunday 1 September 2024 at 11:08:37 UTC+12 Tom Keffer wrote: >> >>> These four lines are interesting: >>> >>> Sep 01 00:00:01 weatherpi CRON[10907]: (weatherpi) CMD >>> (/home/weatherpi/backup_weewx.sh) >>> Sep 01 00:00:01 weatherpi CRON[10906]: (weatherpi) CMD >>> (/home/weatherpi/camera_image1.sh) >>> Sep 01 00:00:01 weatherpi sudo[10911]: weatherpi : PWD=/home/weatherpi ; >>> USER=root ; COMMAND=/usr/bin/systemctl stop weewx >>> Sep 01 00:00:01 weatherpi sudo[10911]: pam_unix(sudo:session): session >>> opened for user root(uid=0) by (uid=1000) >>> >>> First some sort of backup shell script /home/weatherpi/backup_weewx.sh >>> is invoked, then something for a camera image. Then the user identified by >>> uid 1000 (presumably user 'weewx'?) got elevated privileges using "sudo", >>> then used them to terminate weewxd. This is happening at the same time as >>> the backup script. >>> >>> It feels like the backup script is deliberately terminating weewxd >>> before starting the backup. Take a look in the script >>> /home/weatherpi/backup_weewx.sh >>> >>> As for why this is happening at midnight Sunday morning, perhaps the >>> backup script, or something else, is invoked by crontab. Look in >>> /etc/crontab and in /etc/cron.weekly. >>> >>> -tk >>> >>> On Sat, Aug 31, 2024 at 3:51 PM Monica Mulholland <[email protected]> >>> wrote: >>> >>>> This is the log from last night from before and after the time it shuts >>>> down each week and does not restart unless the Rpi is rebooted. >>>> >>>> On Thursday 29 August 2024 at 09:30:46 UTC+12 Monica Mulholland wrote: >>>> >>>>> Thank you! >>>>> >>>>> >>>>> On Thursday 29 August 2024 at 09:16:41 UTC+12 gjr80 wrote: >>>>> >>>>>> I have no idea what might be causing your nightly stoppage, but from >>>>>> the most recent log posted you almost certainly have corrupt station >>>>>> memory. The clues are in hardware record generation being used, WeeWX >>>>>> talking to the console/logger but no archive records being dowloaded and >>>>>> reports are generated normally but with no new data. The net effect is >>>>>> that >>>>>> WeeWX can obtain loop packet data from the console but it cannot obtain >>>>>> archive records. You might want to work through the Corrupt station >>>>>> memory >>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory> >>>>>> >>>>>> section of the Troubleshooting the Davis Vantage station wiki page >>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> >>>>>> . >>>>>> >>>>>> As for the nightly stoppage, once you get your station working again >>>>>> you might want to leave debug = 1 and post a log extract covering >>>>>> say 30 minutes either side of the stoppage time. >>>>>> >>>>>> Gary >>>>>> >>>>>> On Thursday 29 August 2024 at 06:53:02 UTC+10 [email protected] >>>>>> wrote: >>>>>> >>>>>>> But, it is not running at all at the moment.....it is not showing on >>>>>>> the website. On Wunderground it says offline. Despite repeated reboots, >>>>>>> it >>>>>>> has not run in nearly a week. >>>>>>> >>>>>>> On Thursday 29 August 2024 at 05:57:50 UTC+12 vince wrote: >>>>>>> >>>>>>>> Let it run through the weekend and if it fails again this Saturday >>>>>>>> post whatever is logged please. >>>>>>>> >>>>>>>> On Wednesday, August 28, 2024 at 12:55:24 AM UTC-7 dunbrokin wrote: >>>>>>>> >>>>>>>>> OK, lets see if I can get it right this time! >>>>>>>>> mylog >>>>>>>>> <https://drive.google.com/file/d/11Ho3ZSODZgTH-WZ39Ak_JBqNh9YaTSMZ/view?usp=drive_web> >>>>>>>>> >>>>>>>>> On Tue, Aug 27, 2024 at 2:15 PM vince <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> Set debug=1 and maybe we can figure it out >>>>>>>>>> >>>>>>>>>> On Monday, August 26, 2024 at 1:02:43 PM UTC-7 dunbrokin wrote: >>>>>>>>>> >>>>>>>>>>> Oops Sorry, I thought I had hardwired in debug=1.....bottom of >>>>>>>>>>> the class for me on this one I think....made all the rookie >>>>>>>>>>> mistakes. >>>>>>>>>>> Apologies for wasting your time! >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, Aug 27, 2024 at 4:20 AM vince <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Sigh - as always, set debug=1 and let it run for more like 35 >>>>>>>>>>>> minutes. You have an archive period of 10 minutes if it's running >>>>>>>>>>>> off the >>>>>>>>>>>> hardware interval of 600 seconds so we need to see a few cycles. >>>>>>>>>>>> >>>>>>>>>>>> On Monday, August 26, 2024 at 1:38:03 AM UTC-7 dunbrokin wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Apologies, yes it's always a good idea. >>>>>>>>>>>>> >>>>>>>>>>>>> For the last 3 weeks on Sat night at 11.50 it stopped >>>>>>>>>>>>> recording.....but rebooting started it again the next day. >>>>>>>>>>>>> However this >>>>>>>>>>>>> week after rebooting it stopped at 11.10 am and despite >>>>>>>>>>>>> rebooting, it never >>>>>>>>>>>>> started recording again. >>>>>>>>>>>>> >>>>>>>>>>>>> So I ran the log as per the instructions....but it only ran >>>>>>>>>>>>> for about 6 minutes. Attached is all that was recorded in almost >>>>>>>>>>>>> 15 minutes. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Sun, Aug 25, 2024 at 1:33 PM vince <[email protected]> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Your system logs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Saturday, August 24, 2024 at 4:16:58 PM UTC-7 Monica >>>>>>>>>>>>>> Mulholland wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Every week, on Saturday night at 11.50 pm my station stops >>>>>>>>>>>>>>> reporting and needs to be rebooted. I am on a RPi4 (recently >>>>>>>>>>>>>>> upgraded). >>>>>>>>>>>>>>> Other than this little glitch, which is annoying, it is running >>>>>>>>>>>>>>> very well >>>>>>>>>>>>>>> since I upgraded to the RPi4. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Any suggestions of where I might look to try and sort this >>>>>>>>>>>>>>> issue? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Any help greatly appreciated. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> 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]. >>>>>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/68cf6bec-901e-449d-b75a-45b3fc7c75b5n%40googlegroups.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/68cf6bec-901e-449d-b75a-45b3fc7c75b5n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>>>>> . >>>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>> 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]. >>>>>>>>>>>> >>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/79829310-aa83-4281-9244-7cc9adbc0037n%40googlegroups.com >>>>>>>>>>>> >>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/79829310-aa83-4281-9244-7cc9adbc0037n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>>> . >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>> 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]. >>>>>>>>>> >>>>>>>>> To view this discussion on the web visit >>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/ef35ee91-7527-4e17-93a4-f3f7d5bf91c8n%40googlegroups.com >>>>>>>>>> >>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/ef35ee91-7527-4e17-93a4-f3f7d5bf91c8n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>> . >>>>>>>>>> >>>>>>>>> -- >>>> 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]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/a90e0cb4-8728-443c-a04c-bd4f21cee9f1n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/a90e0cb4-8728-443c-a04c-bd4f21cee9f1n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/4efe8b66-2352-4707-bae5-e0b01a3976a1n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/4efe8b66-2352-4707-bae5-e0b01a3976a1n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/407dffe9-0e89-4be3-a676-5544a7b6d52en%40googlegroups.com.
