No updates after upgrade to Bullseye

[dan...@gmail.com]

I've had WeeWx running happily along on a Raspberry Pi 3B for some time.  Then I decided to upgrade that system to Bullseye.  And, well, I apparently broke it.

I first tried an in-place upgrade, rebooted, and it wasn't sending updates--the last line in the log file indicated that it would send updates to WeatherCloud, but then nothing was happening.  So, figuring that the OS upgrade had gone south, I decided to reinstall from scratch.

I downloaded weewx.conf from the Raspberry Pi, along with the .zip files for the extensions I'd installed.  Then put a fresh image of RaspberryPiOS onto the card, copied over those saved files, installed WeeWx, used wee_extension to install the extensions, copied weewx.conf into /etc/weewx/, and restarted weewx.  But sadly, no dice.  Here's what I get in the system log when it tries to start:

Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Initializing weewx version 4.5.1
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Using Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Platform Linux-5.10.63-v7+-armv7l-with-glibc2.31
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Locale is 'en_US.UTF-8'
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: PID file is /var/run/weewx.pid
Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Debug is 1
Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: StdConvert target unit is 0x1

As you see, debug is enabled, but that's the last entry as of almost 15 minutes ago.  Where should I be looking to sort this out?

[vince]

Restart it via 'systemctl start weewx' and then do a 'systemctl status weewx' and see what it thinks.   IYou might also try "journalctl -xe" to see what systemd thinks is going on.

Try running it interactively:

        python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf

(hit control-C to exit that)

FWIW - I just installed weewx using that apt-get method on a bullseye pi and it runs fine for me here.

[... editorial comment follows...]

You didn't mention 'which' system log, but on a pi you generally want to look in /var/log/syslog and not /var/log/messages

Lots of things are possible including your .zip files having old extensions that don't support python3.  You didn't mention 'which' extensions and versions of those.

[dan...@gmail.com]

> You didn't mention 'which' system log, but on a pi you generally want to look in /var/log/syslog and not /var/log/messages

Well, it seems some messages are going to messages, and others to syslog--no, that isn't confusing at all.  "systemctl status weewx" showed that the MySQL connector package wasn't installed ("apt install python3-mysqldb").  Another restart and status check showed it was also missing paho-mqtt ("apt install python3-paho-mqtt").  And with that, it's now working.  Thanks for the push in the right direction.

[vince]

Yes, you kinda have to install the required packages when you add things or use a different type of db.   You might want to write down your additional steps someplace for the next time you flatten the system since you're not running the no-extensions sqlite3 default setup.

The 'which log to look into' question depends on what kind of message is being logged and what severity the message has.

My /etc/rsyslog.conf file has the following content:

*.*;auth,authpriv.none -/var/log/syslog

*.=info;*.=notice;*.=warn;\

auth,authpriv.none;\

cron,daemon.none;\

mail,news.none -/var/log/messages

So everything (*.* meaning all syslog 'facilities' and all severities) goes into /var/log/syslog, but only certain things go into /var/log/messages.

(tl;dr answer - just go with what they give you from the os and don't worry it)

It's possible to set up rsyslog to put weewx-specific things in its own file (it's in the wiki someplace) but I never do that.  I just grep for weewx in /var/log/syslog.