Pity you are not starting off with a standard installation first and then added sofaskin networked external archive database forecast networked external forecast database one by one to have made it easier to locate/identify what, if anything, is/was causing your problems!!
Best of luck though - hope it all works out just fine- just try and change one thing at a time though as it really does make problem identification so much easier .... On Saturday, 7 January 2017 06:29:49 UTC+2, Marc Aubry wrote: > Hi guys, > Little update about my situation after Christmas new year break. > Happy new year to all of you. > first of all to avoid to monitor constantly the weewx rpi during that busy > period for us, i setup a CRON reboot every hour on the Rpi, it's just > hiding the problem and doesn't help to find a solution but at least my > weather station is reporting almost non stop with a maximum break of 1 hour. > in the same time i have setup a RPI 3 with the following config: > > jessie 8 krnl 4.4.34-v7+ > weewx 3.6.2 > sofaskin1.1 > forecast 3.2.9 > > Weather station simulator driver > external mysql archive and forecast database > external ftp server with ftp skin > > The rpi is connected to the LAN via ethernet wire (wifi has been disabled) > The ftp server is a iis webserver hosted on my local network, the archive > and forecast database are hosted on the same linux server as the faulty > weewx config. > i did not setup remote syslog or ramdisk for the local rpi webserver. > the config is running with the simulator without any issue for few day. > It is now time to connect this config with the USB WH23XX driver. > I will as well change the database target with the previous one to > continue on the same database to avoid the long 3 years cumulus import file > process. > if everything run smoothly (which i hope) then i will activate report to > WU and the FTP target to my internet server in the weewx.conf file. > I keep you updated. > > > > > > > > > > > On Monday, January 2, 2017 at 3:28:23 AM UTC+7, Tom Keffer wrote: >> >> Per, >> >> Weewx should not crash. If it does, that's a bug, and we would very much >> like to hear about it. Post the logs! >> >> Most installations run nonstop for months without any problems. >> >> -tk >> >> >> On Sun, Jan 1, 2017 at 12:11 PM, Per Edström <peredst...@gmail.com> >> wrote: >> >>> My Weewx tend to stop for various reasons so I restart Weewx every hour >>> by a cronjob: >>> >>> # m h dom mon dow command >>> 59 * * * * /etc/init.d/weewx stop >>> 0 * * * * /etc/init.d/weewx start >>> >>> -- >>> 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. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
