Bit hard to read but it still appears that you have at least two WeeWX instances running:
Jul 8 08:41:33 raspberrypi weewx[1942] DEBUG weewx.drivers.vantage: Gentle wake up of console successful Jul 8 08:41:36 raspberrypi weewxd: restx: MQTT: Failed upload attempt 2: [Errno -3] Temporary failure in name resolution Jul 8 08:41:36 raspberrypi weewx[1400] ERROR weewx.drivers.vantage: ip-read error: timed out I also suspect you have some remnants of running WeeWX directly as well (the weewxd: entries) The following lines seem to indicate that one WeeWX instance (1942) is communicating with the logger just fine: Jul 8 08:41:28 raspberrypi weewx[1942] DEBUG weewx.drivers.vantage: Retrieving 5 page(s); starting index= 1 Jul 8 08:41:29 raspberrypi weewx[1942] DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2021-07-07 10:50:00 BST (1625651400) less than final timestamp 2021-07-08 06:20:00 BST (1625721600) Jul 8 08:41:29 raspberrypi weewx[1942] DEBUG weewx.drivers.vantage: Catch up complete. Jul 8 08:41:29 raspberrypi weewx[1942] INFO weewx.engine: Starting main packet loop. Jul 8 08:41:29 raspberrypi weewx[1942] DEBUG weewx.drivers.vantage: Gentle wake up of console successful Judging by that portion of the log I suspect you probably have corrupt station memory and will likely ultimately have to clear the logger memory. But first you need to kill the competing WeeWX instances or you will continue to chase your tail. I suggest you: 1. Attempt to stop the WeeWX daemon using $ sudo systemctl stop weewx or whatever command you are used to using. 2. Check for any remaining running WeeWX instances using: $ ps -aux|grep weewx This will give you a list of processes that include the text 'weewx' somewhere in them, the list of entries will look something like: bill 12631 0.0 0.0 6488 392 pts/1 S+ 17:01 0:00 tail -f -n 50 /var/log/weewx/weewx.log root 12676 16.3 5.8 191520 55824 ? Sl 17:01 26:13 /usr/bin/python3 /home/weewx/bin/weewxd --daemon --log-label weewx --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf The number in the second column is the process ID (PID) and the last column is the text after the last time column is the command being run. In the above case PID 12676 is a running WeeWX instance but PID 12631 is not (it's just tailing the WeeWX log) 3. Kill any running WeeWX instances by using the kill command as follows to kill the PID(s) concerned. In the above case you would use: $ sudo kill -9 12676 Again, in your case, I suspect you may well have PIDs of 1400 and/or 1942. You will probably also see one for weewxd, kill that PID too. 4. Run the ps command at 2. above and check there are no WeeWX instances still running (other PIDs that include the text 'weewx', such as the tail [PID 12631] above, are fine). 5. Restart WeeWX using $ sudo systemctl start weewx 6. Monitor the log from startup, you will initially two difference PIDs being used for WeeWX but once the WeeWX daemon is up and running there should only be one PID appearing in the log. Take a copy of the log from startup through until 10 minutes have passed (from startup) and post the log back here. Gary -- 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/046b0dbd-756e-4e59-8c4b-0947e1ab05fdn%40googlegroups.com.
