Ok, Joe, I think the bug I mentioned earlier is what is causing the problem. The simplest fix is:
- rename the existing /home/weewx/bin/user/wdSearchX3.py to, say, /home/weewx/bin/user/wdSearchX3_orig.py - download the updated wdSearchX3.py from the weewxwd bitbucket site using: wget https: //bitbucket.org/ozgreg/weewx-wd/raw/103afd92d02e1a343b3239fad828c45eb0689ead/bin/user/wdSearchX3.py - copy the newly downloaded wdSearchX3.py in place of the old renamed, version - stop then start weewx - watch the weewx logs for any errors during the report cycle - let us know ifd the issue persists Gary On Friday, 2 September 2016 10:06:29 UTC+10, jmltech wrote: > > Thanks Gary. I did check /var/log/syslog before I stopped weewx to > install cmon. I didn't see any errors. I had loaded weewx-wd right after > I had installed weewx on this server (this is a new installation. I have > an existing VWS at another house that I'm planning on converting to weewx > once I load the historic records over). From the previous views from log > files, I never saw any weewx errors. > Attached is the wee_debug log that you requested. > > >> -- 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.
