I finally was able to take a little time to dig through some of the scripts, and after deleting pid file, and issuing a "systemctl daemon-reload", and then weewx service finally restarted. It took a little while to dump and record the missed records.
I think I am good now. Thanks for everyone's assistance. On Wed, Dec 27, 2017 at 7:15 AM, Mike Dame <[email protected]> wrote: > Tried a delete from archive after midnight 12/25 that did not work after > drop and rebuild still did not start. So per request, I have attached the > message logs from the 22nd till 26th. > > I tried turning on debug in the config file, still did not log anything or > start.... > Anyway to start in foreground to see if there is any clue why it is not > starting up.... > > On Tue, Dec 26, 2017 at 10:54 PM, gjr80 <[email protected]> wrote: > >> I'm not necessarily seeing anything wrong here. I would take it from the >> top again and this time post the entire log, covering the wee_database >> operations and weeWX startup and any errors. Better to post an full and >> complete log rather than disjointed excerpts, far easier to read what is >> happening. systemctl status is great for looking at the state of the weeWX >> daemon but not much chop for looking at logs, it is like reading them >> through a drinking straw. >> >> Gary >> >> -- >> 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/to >> pic/weewx-user/RezDiRbbCks/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.
