That is odd. I don't see why that would have anything to do with anything. Could you include the log from the run?
-tk On Wed, Sep 26, 2018 at 8:31 AM Charles Ross <[email protected]> wrote: > I ran wee_database with the --update token and that cleaned things up. > Thanks for all the help and suggestions. Good learning experience. > > Chuck > > On Wednesday, September 26, 2018 at 10:47:37 AM UTC-4, Thomas Keffer wrote: >> >> Then perhaps you are using a different weewx.conf when running >> wee_database, versus weewxd. Try an explicit path. For example (assuming a >> setup.py install): >> >> *wee_database /home/weewx/weewx.conf* >> >> -tk >> >> On Wed, Sep 26, 2018 at 7:26 AM Charles Ross <[email protected]> wrote: >> >>> Weird, I have no other issues, weewx stops, starts, performs fine. I >>> see no error messages in the logs, only when I run the wee_database command >>> do I have problems. >>> >>> I'll keep digging. >>> >>> CR >>> >>> On Wed, Sep 26, 2018 at 10:15 AM Thomas Keffer <[email protected]> wrote: >>> >>>> You have an error in your weewx.conf file. The error message suggests >>>> it's in the very first line. >>>> >>>> -tk >>>> >>>> On Wed, Sep 26, 2018 at 7:07 AM Charles Ross <[email protected]> >>>> wrote: >>>> >>>>> Thanks all for the help. >>>>> >>>>> I started from scratch this morning. I stop weewx and run >>>>> '*wee_database >>>>> weewx.conf --drop-daily*' I am getting the following feedback right >>>>> at the start: >>>>> >>>>> Traceback (most recent call last): >>>>> File "/usr/bin/wee_database", line 793, in <module> >>>>> main() >>>>> File "/usr/bin/wee_database", line 133, in main >>>>> config_path, config_dict = weecfg.read_config(options.config_path, >>>>> args) >>>>> File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config >>>>> config_dict = configobj.ConfigObj(config_path, file_error=True) >>>>> File "/usr/lib/python2.7/dist-packages/configobj.py", line 1230, in >>>>> __init__ >>>>> self._load(infile, configspec) >>>>> File "/usr/lib/python2.7/dist-packages/configobj.py", line 1320, in >>>>> _load >>>>> raise error >>>>> configobj.ConfigObjError: Parsing failed with several errors. >>>>> First error at line 1. >>>>> >>>>> -Chuck >>>>> >>>>> >>>>> >>>>> On Wednesday, September 26, 2018 at 8:53:47 AM UTC-4, Thomas Keffer >>>>> wrote: >>>>>> >>>>>> OK. Try this. >>>>>> >>>>>> Check the date & time on the NOAA HTML pages. How old are they? Make >>>>>> sure that they have, in fact, been recently generated. If they are old, >>>>>> delete them, and WeeWX will regenerate. On the other hand, if they have >>>>>> been recently generated, then the problem lies deeper. >>>>>> >>>>>> But, to do that will require more information, such as what values >>>>>> you are trying to fix and their timestamps. We will need to check both >>>>>> the >>>>>> archive and daily summaries for the values. >>>>>> >>>>>> -tk >>>>>> >>>>>> On Wed, Sep 26, 2018 at 5:43 AM Charles Ross <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Yes I did, I followed that web page exactly yesterday. >>>>>>> >>>>>>> >>>>>>> On Wednesday, September 26, 2018 at 8:37:22 AM UTC-4, Thomas Keffer >>>>>>> wrote: >>>>>>>> >>>>>>>> Did you follow the directions in the Wiki entry, *Cleaning up old >>>>>>>> 'bad' data >>>>>>>> <https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data>* >>>>>>>> ? >>>>>>>> >>>>>>>> -tk >>>>>>>> >>>>>>>> On Wed, Sep 26, 2018 at 5:18 AM Charles Ross <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> Yesterday two pieces of bad temperature and dewpoint data made >>>>>>>>> it's way into the weewx.sdb archive database. I removed the bad >>>>>>>>> data but >>>>>>>>> my NOAA September and yearly files are still corrupt this morning. >>>>>>>>> >>>>>>>>> Can someone please guide me on how to fix the reports so I can >>>>>>>>> have correct NOAA reports? >>>>>>>>> >>>>>>>>> Thank you for taking the time to help, >>>>>>>>> >>>>>>>>> Chuck Ross >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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. >>>>>>>>> >>>>>>>> -- >>>>>>> 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. >>>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "weewx-user" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/weewx-user/--ofTjRbzII/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> 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 [email protected]. >>> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
