OK ... purge again ... but this time I did not installed MQTT (it seems creating issues every time).
Seems OK now, but after reinstalling Apache2, and set the directory, I cannot see it. How to set the "public_html" directory for weewx? Usually is it there: /var/www/weewx/* but it does not work YM Le mardi 11 juillet 2023 à 18 h 47 min 46 s UTC-4, Yves Martin a écrit : > OK, I purge all, delete old directories ... and keep my old weewx.conf > file. > > Now I have this error : > > Configuration file '/etc/weewx/weewx.conf' > ==> File on system created by you or by a script. > ==> File also in package provided by package maintainer. > What would you like to do about it ? Your options are: > Y or I : install the package maintainer's version > N or O : keep your currently-installed version > D : show the differences between the versions > Z : start a shell to examine the situation > The default action is to keep your current version. > *** weewx.conf (Y/I/N/O/D/Z) [default=N] ? > > Traceback (most recent call last): > File "/usr/share/weewx/wee_config", line 128, in <module> > main() > File "/usr/share/weewx/wee_config", line 122, in main > config_mgr.run(args, options) > File "/usr/share/weewx/weecfg/config.py", line 125, in run > weecfg.modify_config(config_dict, stn_info, self.logger, options.debug) > File "/usr/share/weewx/weecfg/__init__.py", line 313, in modify_config > config_dict['StdReport']['Defaults']['unit_system'] = > stn_info['unit_system'] > File "/usr/lib/python3/dist-packages/configobj.py", line 554, in > __getitem__ > val = dict.__getitem__(self, key) > KeyError: 'Defaults' > dpkg: error processing package weewx (--install): > installed weewx package post-installation script subprocess returned > error exit status 1 > Processing triggers for systemd (241-7~deb10u9+rpi1) ... > Errors were encountered while processing: > weewx > > (...) > > YM > > Le mardi 11 juillet 2023 à 18 h 31 min 24 s UTC-4, Tom Keffer a écrit : > >> Note that with packaged installs, if you remove a package, it does not >> remove weewx.conf unless you "purge" it. >> >> *sudo apt purge weewx* >> >> >> Take a look at the bottom of your weewx.conf under [Engine]. You have >> user.mqtt specified somewhere in there. >> >> >> >> On Tue, Jul 11, 2023 at 3:21 PM Yves Martin <[email protected]> wrote: >> >>> I've reinstalled all ... still have critical issues >>> >>> debug=1 is already set >>> >>> Last error : >>> >>> /etc/init.d/weewx start >>> /etc/init.d/weewx status >>> >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** File "/usr/share/weewx/weewxd", line 148, in main >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** engine = weewx.engine.StdEngine(config_dict) >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** File "/usr/share/weewx/weewx/engine.py", line 93, in __init__ >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** self.loadServices(config_dict) >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** File "/usr/share/weewx/weewx/engine.py", line 161, in >>> loadServices >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** obj = weeutil.weeutil.get_object(svc)(self, config_dict) >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** File "/usr/share/weewx/weeutil/weeutil.py", line 1335, in >>> get_object >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** mod = __import__(module) >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** ModuleNotFoundError: No module named 'user.mqtt' >>> Jul 11 17:17:09 weewx4-raspi python3[375]: weewx[375] CRITICAL __main__: >>> **** Exiting. >>> >>> I have disabled MQTT in weewx.conf but I have till this error. >>> >>> One week now I'm trying to reinstall weewx, I'm a bit desperated... >>> >>> YM >>> >>> >>> Le lundi 10 juillet 2023 à 21 h 19 min 34 s UTC-4, Tom Keffer a écrit : >>> >>>> Please set debug=1, then restart weewx. Post the log from startup >>>> through the exception. >>>> >>>> On Mon, Jul 10, 2023 at 2:50 PM Yves Martin <[email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> Since I've upgraded weewx from 3.9.2 to 4.10.2 I have a couple of >>>>> error. >>>>> >>>>> This one seems critical : >>>>> >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** Traceback (most recent call last): >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** self.console = loader_function(config_dict, self) >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 40, in >>>>> loader >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** return VantageService(engine, config_dict) >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 1989, in >>>>> __init__ >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** Vantage.__init__(self, **config_dict[DRIVER_NAME]) >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 534, in >>>>> __init__ >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** self._setup() >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 1394, in >>>>> _setup >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** self.hardware_type = self._determine_hardware() >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 1385, in >>>>> _determine_hardware >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** raise weewx.WeeWxIOError("Unable to read hardware type") >>>>> Jul 10 17:46:34 meteo-raspi weewx[4390] CRITICAL weewx.engine: >>>>> **** WeeWxIOError: Unable to read hardware type >>>>> >>>>> Any suggestion? >>>>> >>>>> Regards, >>>>> Yves >>>>> >>>>> -- >>>>> 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/fd6e8299-3b73-4cd8-92ac-22f9087228f5n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/weewx-user/fd6e8299-3b73-4cd8-92ac-22f9087228f5n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> 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/80ce2801-f109-476c-a8b4-94e1950460a4n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/80ce2801-f109-476c-a8b4-94e1950460a4n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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/0aa0e2df-1190-4d79-8d26-3f7bd4e789ebn%40googlegroups.com.
