That is a very good log extract. From that extract WeeWX seems to be running just fine with no errors. The lines similar to: Feb 18 21:05:40 raspberrypi weewxd[35139]: DEBUG weewx.reportengine: Cannot read localization file /etc/weewx/skins/neowx-material/lang/en.conf for report 'StandardReport': Config file not found: "/etc/weewx/skins/neowx-material/lang/en.conf". Feb 18 21:05:40 raspberrypi weewxd[35139]: DEBUG weewx.reportengine: **** Using defaults instead. mean than an English language config file could not be found and the defaults are being used instead. If your skin files are being generated in the correct language you can ignore this.
The neowx-material SyntaxWarnings are exactly that, a warning and do not appear to be causing a problem. If they are causing a problem then you should take this up with the neowx-material author. If your system is running error free and you are having problems viewing current pages/plots in a browser the first thing to do is to clear the browser cache. How you do this varies from browser to browser. A few additional comments. First you seem to have the neowx-material skin being run under the StandardReport report. This is not a problem as the report name merely needs to be a unique (compared to other report names) string. However, considering that WeeWX ships with a skin called Standard that is run under a report named StandardReport you might find it less confusing (especially if you need outside help in the future) to give the report that runs the neowx-material skin a more descriptive name, eg Neowx-MaterialReport. The order of your enabled reports under [StdReport] in weewx.conf appears to be SeasonsReport, FTP, StandardReport (which runs the neowx-material skin). Again this runs without error, but it means you Seasons skin files are generated, your files are uploaded by FTP then the neowx-material skin files are generated. The result is that when the FTP report uploads your files it uploads the just generated Seasons skin file, but it then uploads the previously generated neowx-material skin files. In other words, on you web server you will see the current Seasons skin files but your neowx-material files will always be at least five minutes old. Under [StdReport] the order of the report stanzas matters. I suspect you would be better off changing the order of your enabled reports to SeasonsReport, StandardReport,FTP. Finally, your driver version is 0.4.2KW, I have no idea where you sourced this driver from as I have never released such a version and have no idea what modifications may have been made to the driver. The current Ecowitt gateway (nee GW1000) driver is v0.6.0, so depending on your requirements you might want source a more up to date version. Gary On Monday 19 February 2024 at 06:26:07 UTC+10 Thomas Hackler wrote: > Thomas Hackler schrieb am Sonntag, 18. Februar 2024 um 21:25:40 UTC+1: > >> ok thanks, I was not ready for version 5 and start reading the docs >> attached there is a 15 minutes log, I guess now is everything working >> My edge browser didn't show me the actual pictures from the season skin, >> neo wx is working >> but firefox show me both >> thanks for the support and documentation (helps to learn a lot) >> >> gjr80 schrieb am Sonntag, 18. Februar 2024 um 11:01:53 UTC+1: >> >>> A couple of things. First, you appear to be using systemd and if you >>> are running a WeeWX v5 Debian install you should be using systemctl >>> <http://weewx.com/docs/5.0/usersguide/running/#running-as-a-daemon> and >>> to start/stop and otherwise control the WeeWX service. >>> >>> Second, your log extract covers just over one minute with WeeWX already >>> running. That really is not enough log for us to be of any help. You need >>> to capture the full WeeWX startup, this contains important config >>> information. You also need a longer log extract, if your archive interval >>> is five minutes then we need to see at least 10 minutes of log. >>> >>> Gary >>> >>> PS. For what it is worth I see no problems in the log extract that was >>> posted. >>> On Sunday 18 February 2024 at 19:13:28 UTC+10 Thomas Hackler wrote: >>> >>>> Hello, >>>> thank you for your help! >>>> I don't know why but now weewx seems to work again but something is >>>> still wrong. >>>> Attached you can find a complete log file. I had another issue on my Pi >>>> which I solved now, I run out of space on the SD card, maybe this effected >>>> the access to the gw1000 driver. >>>> My neo WX skin works, the standard season skin don't show me pictures >>>> for today. >>>> If I use these commandos there is no reaction in syslog: >>>> >>>> sudo /etc/init.d/weewx start >>>> sudo /etc/init.d/weewx stop >>>> sudo /etc/init.d/weewx restart >>>> >>>> i cannot start or stop weewx. >>>> >>>> I think with the permissions everything is ok? >>>> >>>> pi@raspberrypi:~ $ groups >>>> pi adm dialout cdrom sudo audio video plugdev games users input render >>>> netdev lpadmin weewx gpio i2c spi iobroker >>>> >>>> pi@raspberrypi:~ $ grep User /usr/lib/systemd/system/weewx.service >>>> User=weewx >>>> >>>> After I restored the SD card with my old image from January I replaced >>>> the weewx.sdb with the newer one, but this should have no effect or not ? >>>> >>>> Do you need more information ? >>>> >>>> >>>> gjr80 schrieb am Sonntag, 18. Februar 2024 um 02:04:29 UTC+1: >>>> >>>>> Your Ecowitt gateway driver issue is that the driver is unable to >>>>> contact your gateway device, this is causing WeeWX to exit. This could be >>>>> due to any number of reasons, it's impossible to say much more without >>>>> seeing the full log from startup to failure. Refer to the How to get >>>>> a good, useful log section >>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#how-to-get-a-good-useful-log> >>>>> >>>>> of the Help! Posting to weewx-user Wiki page >>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> for >>>>> how to get a good log extract. Note that you will likely need to use the >>>>> instructions for journalctl rather than syslog. >>>>> >>>>> Gary >>>>> On Saturday 17 February 2024 at 19:58:48 UTC+10 Thomas Hackler wrote: >>>>> >>>>>> I am sorry: >>>>>> >>>>>> pi@raspberrypi:~ $ systemctl status weewx >>>>>> ● weewx.service - WeeWX >>>>>> Loaded: loaded (/lib/systemd/system/weewx.service; enabled; >>>>>> vendor preset: enabled) >>>>>> Active: failed (Result: exit-code) since Sat 2024-02-17 10:18:36 >>>>>> CET; 38min ago >>>>>> >>>>>> Docs: https://weewx.com/docs >>>>>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, >>>>>> status=4) >>>>>> Main PID: 606 (code=exited, status=4) >>>>>> CPU: 621ms >>>>>> >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>> **** self.mac = self.get_mac_address() >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>> **** File "/etc/weewx/bin/user/gw1000.py", line 3625, in >>>>>> get_mac_address >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>> **** return self.send_cmd_with_retries('CMD_READ_STATION_MAC') >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>> **** File "/etc/weewx/bin/user/gw1000.py", line 3808, in >>>>>> send_cmd_with_retries >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>> **** raise GW1000IOError(_msg) >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>> **** user.gw1000.GW1000IOError: Failed to obtain response to command >>>>>> 'CMD_READ_STATION_MAC' after 3 attempts >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable to >>>>>> load driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' >>>>>> after 3 attempts >>>>>> >>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: **** >>>>>> Exiting... >>>>>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main process >>>>>> exited, code=exited, status=4/NOPERMISSION >>>>>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with >>>>>> result 'exit-code'. >>>>>> >>>>>> michael.k...@gmx.at schrieb am Samstag, 17. Februar 2024 um 10:53:49 >>>>>> UTC+1: >>>>>> >>>>>>> It will definitely help if you'd attach the log files as a whole, it >>>>>>> see> >>>>>>> ms > >>>>>>> the> >>>>>>> lo> >>>>>>> g ab> >>>>>>> ove is not showing all the relevant data. >>>>>>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:41:33 >>>>>>> UTC+1: >>>>>>> >>>>>>>> pi@raspberrypi:~ $ apt policy weewx >>>>>>>> weewx: >>>>>>>> Installed: 5.0.2-1 >>>>>>>> Candidate: 5.0.2-1 >>>>>>>> >>>>>>>> >>>>>>>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:39:13 >>>>>>>> UTC+1: >>>>>>>> >>>>>>>>> here are some more information, something seems to be wrong with >>>>>>>>> the gw1000 driver, but I changed nothing: >>>>>>>>> >>>>>>>>> pi@raspberrypi:~ $ systemctl status weewx* >>>>>>>>> ● weewx.service - WeeWX >>>>>>>>> Loaded: loaded (/lib/systemd/system/weewx.service; enabled; >>>>>>>>> vendor preset:> >>>>>>>>> Active: failed (Result: exit-code) since Sat 2024-02-17 >>>>>>>>> 10:18:36 CET; 17mi> >>>>>>>>> Docs: https://weewx.com/docs >>>>>>>>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf >>>>>>>>> (code=exited, status=4) >>>>>>>>> Main PID: 606 (code=exited, status=4) >>>>>>>>> CPU: 621ms >>>>>>>>> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>>>>> **** s> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>>>>> **** Fil> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>>>>> **** r> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>>>>> **** Fil> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>>>>> **** r> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL weewx.engine: >>>>>>>>> **** user.> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: Unable >>>>>>>>> to load driv> >>>>>>>>> Feb 17 10:18:36 raspberrypi weewxd[606]: CRITICAL __main__: >>>>>>>>> **** Exiting... >>>>>>>>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Main >>>>>>>>> process exited, cod> >>>>>>>>> Feb 17 10:18:36 raspberrypi systemd[1]: weewx.service: Failed with >>>>>>>>> result 'exit> >>>>>>>>> lines 1-18/18 (END)...skipping... >>>>>>>>> ● weewx.service - WeeWX >>>>>>>>> Loaded: loaded (/lib/systemd/system/weewx.service; enabled; >>>>>>>>> vendor preset: enabled) >>>>>>>>> Active: failed (Result: exit-code) since Sat 2024-02-17 >>>>>>>>> 10:18:36 CET; 17min ago >>>>>>>>> Docs: https://weewx.com/docs >>>>>>>>> Process: 606 ExecStart=weewxd /etc/weewx/weewx.conf >>>>>>>>> (code=exited, status=4) >>>>>>>>> Main PID: 606 (code=exited, status=4) >>>>>>>>> CPU: 621ms >>>>>>>>> >>>>>>>>> Thomas Hackler schrieb am Samstag, 17. Februar 2024 um 10:35:25 >>>>>>>>> UTC+1: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> I use weewx on a raspberry Pi 4. My system crashed and I had to >>>>>>>>>> go back to an SD card image from January. It was a state were weewx >>>>>>>>>> was >>>>>>>>>> runing normally. >>>>>>>>>> But now I don't know why weewx is not working anymore. >>>>>>>>>> I get no reaction for commands like >>>>>>>>>> >>>>>>>>>> sudo /etc/init.d/weewx stop >>>>>>>>>> sudo /etc/init.d/weewx start >>>>>>>>>> >>>>>>>>>> debug = 1 and I don't see something in syslog: >>>>>>>>>> >>>>>>>>>> sudo tail -f /var/log/syslog | grep weewx >>>>>>>>>> >>>>>>>>>> in January I had a weewx 4 and with apt upgrade I guess I changed >>>>>>>>>> to version 5 now but this was not a problem during my last update. >>>>>>>>>> >>>>>>>>>> Any ideas? Thank you! >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> Thomas >>>>>>>>>> >>>>>>>>> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7d65cc47-4f66-43c9-840b-1bb6d92e16d5n%40googlegroups.com.
