Hi, In short no there should not be five WeeWX PIDs, though it's impossible to say much more without seeing some output. By all means post the htop output but what really matters is the log. Might be interesting to see the log for a few report cycles before the system locked up. Suggest killing all the WeeWX PIDs, then restarting WeeWX.Check there is only one WeeWX instance running (the log will show this clearly). If anything odd appears or the system locks up again then the post the log showing WeeWX startup and a few report cycles and also the last few report cycles leading up to the system locking up.
Gary On Tuesday, 11 June 2019 08:58:17 UTC+10, CablDeViL wrote: > > Good Day all! > > I have a question. I just clean and nuke my pi to get a fresh install of > debian for my outdated pi. I installed weewx and manually updated my config > file from my hand print out of the old one. > > I found my pi locked up 28 hours later. I rebooted and did a htop to find > muti PIDs of weewx. 2 of which pegged the cpu for over 2 minutes each time > and heating up the older pi. > > Is that normal to have so many instances? > > Also I have no use for the html files being generated as I don't host. Can > I change the config to stop that execution and save resources? > > Thank you in advance. > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/687e55b3-da9a-47e4-b267-7172b6e09091%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
