UPDATE: 1. The bad news:
I tried to solve this by upgrading my OS on my Raspberry Pi from Raspbian stretch to Raspbian buster in the hope that this might reset everyting and solve the IP-errors, and also made python 3 the preferred python version, as I read that this is preferred for weewx 4.10 (which is the version I am using). However, weewx failed even quicker than before, with errors that appear unrelated to the ip-errors. Here is an extract from the syslog. Any ideas as to what is causing this? I possibly did something dumb when upgrading the OS. ********************************************* Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** self.loadServices(config_dict) Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** obj = weeutil.weeutil.get_object(svc)(self, config_dict) Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** File "/usr/share/weewx/weeutil/weeutil.py", line 1335, in get_object Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** mod = __import__(module) Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** File "/usr/share/weewx/user/mqtt.py", line 196 Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** except KeyError, e: Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** ^ Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** SyntaxError: invalid syntax Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** Exiting. Dec 21 15:16:12 raspberrypi kernel: [ 1174.418150] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:fb:72:be:d8:62:83:0f:08:00:46:00:00:20:e4:51:00:00 SRC=192.168.0.218 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=58449 PROTO=2 Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** self.loadServices(config_dict) Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** obj = weeutil.weeutil.get_object(svc)(self, config_dict) Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** File "/usr/share/weewx/weeutil/weeutil.py", line 1335, in get_object Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** mod = __import__(module) Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** File "/usr/share/weewx/user/mqtt.py", line 196 Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** except KeyError, e: Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** ^ Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** SyntaxError: invalid syntax Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: **** Exiting. ********************************************** So having failed at that, I went back to my old set up (yes, I took a back-up of the SD cared before upgrading the OS) and the IP-errors were, as expected, the same as before. So, I decided to give up on the weaterlink IP device, and ordered a Meteo-Pi HAT to provide a direct link between my Vantage Pro2 console and my Raspberry Pi running weewx. 2. The good news: We had a power cut in our area in the UK for 6 hours last night. Power was restored overnight. Very annoying, but I awoke this morning to a weewx system with no errors (ie still using the weatherlink IP logger). So presumably, the reboot of my network router sorted out the IP errors. Strange, as I think I tried rebooting the router earlier in the evolution of these errors. Sods law, but the Meteo-Pi arrived on the same morning (today) that the weewx system started working without errors. A future back-up option perhaps - or I may return it to the supplier. David. On Tuesday 19 December 2023 at 04:59:57 UTC Dominic Reich wrote: > * David Hindley <hind...@gmail.com> [Mon, Dec 18 2023 08:09 +0000]: > > >When I type > > > >ps -aux|grep weewx > > > >I get > > > >root 535 5.6 6.1 117524 58128 ? Sl 10:16 2:42 python2 > >/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid > >/etc/weewx/weewx.conf > >pi 2130 0.0 0.0 4368 564 pts/0 S+ 11:04 0:00 grep > >--color=auto weewx > > > >And, then typing > > > >sudo /etc/init.d/weewx stop > > > >produces > > > > Stopping weewx (via systemctl): weewx.service. > > > >but then repeating the grep command, still shows the 535 process still > >running? > > > >How do I stop weewx - do I have to use kill 535 perhaps? > > That is an option, but I'd first confirm that weewx is not getting > stopped (that can take some seconds to happen though). > > If you confirm weewx unstopped after 10 seconds you could kill the > process number with `sudo kill 535` (sending TERM signal to the process) > and if that does not work either you can KILL the process with > `sudo kill -9 535` which will force the process to kill. > > You would normally kill a process with TERM, which tells the process to > save and finish, KILL will quit the process regardless of unfinished > operations of that process. > > This is usually described in the `signal(3)` manpage, but could differ on > your operating system. > > You could also use the pid file of weewx, which could look something > like that to force kill the process: > `sudo kill -9 $(cat /var/run/weewx.pid)` > > HTH > > - dominic > > > > >Thanks > > > >David. > > > >On Sat, 16 Dec 2023 at 19:39, vince <vince...@gmail.com> wrote: > > > >> Sorry - we can't fix your network. Lots of legacy embedded type 2.4GHz > >> wifi things have issues staying on the network and stable. I'd suggest > >> you try to see if your wifi is being interfered with from a neighbor > >> perhaps. Maybe you can switch which channel your wifi is on. > >> > >> FWIW, we have too many neighbors here with misconfigured wifi to even > >> count, depending on who moves in/out and who visits them occasionally. > >> What I eventually needed to do was (a) move everything in the house that > >> could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and > basically > >> try to out-radiate the neighbors. Problem went away at that point. > >> > >> > >> -- > >> 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/q67cvEsXtjQ/unsubscribe. > >> To unsubscribe from this group and all its topics, send an email to > >> weewx-user+...@googlegroups.com. > >> To view this discussion on the web visit > >> > https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com > >> < > https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%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 weewx-user+...@googlegroups.com. > >To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/CAHtYHVLtTSA9rq-fKN%2BPaDMJazz41B1OdBVfxHxKJa%3DZ%2BRim4A%40mail.gmail.com > . > > -- > The weak are always anxious for justice and equality. > The strong pay no heed to either. > - Aristotle > -- 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/3d732d36-e25c-494f-9ab1-032d51980491n%40googlegroups.com.
