Hi, On Monday, 27 November 2017 20:11:37 UTC+10, jmviper wrote: > > > Can it be fixed ?? >
Of course, the trick is in finding out the issue. In this case I suspect something is causing the thread that generates the gauge-data.txt file to die, we need to find out what. There are a few things you can do/info you can provide that will help track down the issue: 1. It's not apparent what version of weeWX you are running but if it is v3.4.0 or later please run the wee_debug utility <http://weewx.com/docs/utilities.htm#wee_debug_utility> and post its output. Before posting the output make sure you check through it to ensure there is no sensitive info remaining, wee_debug does a pretty good job at sanitising weewx.conf contents but its not perfect. If running an earlier weeWX version it is likely wee_debug is not installed so please just post a copy of your weewx.conf, again make sure you check through the file and remove any sensitive info. 2. Edit weewx.conf, set debug=3, save weewx.conf then stop/start weeWX. Let weeWX run for at least two archive periods and then post a copy of the log from when you started weeWX making sure there is at least two archive periods in the output. Do not edit the log entries. 3. Stop weeWX and then run weeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly>. You should see a series of entries appearing on your screen starting with LOOP: and the occasional REC:; these are the loop packets and archive records being received from your station, please capture these and post them from when you started weeWX until after the first REC: entry. REC: should appear once every archive period at the end of the period. Gary -- 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.
