Hi, The reboot is due to the genset change every 12 hours (shift day night, i'm living off grid) and the rpi3 is not connected to an UPS, as well for the router on which the rpi is connected on. the rpi boot probably faster than my router. So it is not exactly a reboot but a power shut down.
For the rsync error, i did not setup anything in weewx conf, because i'm not using rsync. i leave it by default.i'm just using ftp skin for normal ftp generator. The weather station is connected to the pi via USB Nothing else is connected to the pi. it is running in headless mode (no keyboard no monitor) i access to the pi via ssh or vnc. this pi is dedicated to weewx. About hardware problem, if you look above on this thread you will notice that i have had the exact same problem on rpi2 with the same config and i did change it to rpi3 to validate the hardware. it is a fresh install from scratch by following the instructions in the weewx doc or forecast doc or the sofaskin doc. I did run the config with weewx, forecast and sofaskin with the simulator for a week flawlessly (while my buggy rpi2 config connected to the weaher station was still reporting with CRON scheduled reboot every hour to hide the problem). The weewx stop reportin only after i have connected the WH23xx driver to the weather station. I choose this approach because my online weather station website is a part of my cross referencing SEO strategy and is running since 2014 (with cumulus) and i prefer not to stop this flow of data to the web. I will try to connect the RPI to an UPS but i will need some work to bring the UPS cable to it... About hard power shut down of the RPI, i know that it is not recommended and that i risk SD card problem but i have a fresh image backup of every config, i have 3 other RPI working the same way without any problem. one with Rasplex Open elec config for my plex media player working since more than a year without problem one with repetier server for my 3d printer one with home made radio player (in python) to stream the music from my mpd server. I hope this can help to diagnose the problem thanks for your help. On Tuesday, January 17, 2017 at 11:41:26 AM UTC+7, mwall wrote: > > > > On Friday, January 13, 2017 at 8:27:31 PM UTC-5, Marc Aubry wrote: >> >> maybe i'm wrong here but i suspect a WH23XX driver problem in between >> weewx and my weather station. >> >> Please find attached syslog file, weewx_debug file, skin.conf file. >>> >>> >>>>>> > from the attached syslog.1 we see: > > - you have temporal chaos and an unorderly network startup. the pi starts > up with the wrong time. weewx starts and attempts to connect to a mysql > database, but the network is not up yet, so weewx sleeps for 2 minutes. > meanwhile the system continues to boot up. eventually the network comes up > and the clock is reset by ntp. > > - at Jan 13 17:53:26 weewx[672] makes a log entry about decoded data. the > next log entry is Jan 13 17:17:04 by syslog, followed by what appears to be > a boot sequence. what caused the reboot? why are there no more messages > in the log? (an orderly shutdown should have resulted in some log > messages, no?) > > - at Jan 13 17:17:04 weewx[645] makes its first log entry. at Jan 13 > 17:17:05 the weewx[645] process attempts to connect to the mysql database > and fails, so it sleeps for 2 minutes. > > - at Jan 13 17:17:19 the clock jumps to Jan 13 17:54:15 > > - at Jan 13 20:50:51 the process weewx[645] reports 'rsync upload not > requested'. the next log entry is Jan 13 21:17:01, followed by a bunch of > rsyslogd-2007 and CRON messages at what appear to be one hour intervals. > > - at Jan 14 06:25:07 rsyslogd was HUPed (that and the apache message > before it are probably due to logrotate doing its thing) > > none of that tells us anything. it kind of looks like there is a hardware > problem. in the case of the 645 process, the reporting continued for a > little while (it is a separate thread), but then it stopped reporting too. > so nothing in the log directly indicates that there is a problem in the > driver. > > what is causing the system reboots? if you are causing the system to > reboot, how are you doing it? > > how is the wh2310 connected to the pi? > > what else is connected to the pi? what else is running on the pi? > > if you want to figure out if the driver is the problem, then you need to > run weewx with only the driver and with no other services. that means > local database, not mysql. that means no other skins or reports other than > the standard skin - no forecast. > > based on our experience with those other parts, they are probably not the > problem. but anything other than the problem confounds your ability to > find the problem. > > m > -- 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.
