Upgraded to v4.3. Set weewx to use my current (4.2) weewx.conf. After confirm 4.3 conf is ok, set weewx to use it.

[John Mora]

I just upgraded my Raspberry Pi 4 weewx installation to v4.3 from v 4.2 and everything appears to be working as expected. Being the paranoid sort that I am, when the upgrade process prompted me to overwrite or save/use my current weewx.conf I told it to use my current one. After doing so and saving multiple versions of weewx.conf, the system reported that it is using weewx.conf-4.2.0.

Now that I have verified that the new, combined weewx.conf will be ok to use, how do I get weewx to use the combined weewx.conf instead of the old weewx.conf-4.2.0?

I couldn't find any specific information on how to verify the version of weewx.conf weewx was using when it started running. Also, I didn't see anything is the syslog when I restarted weewx that would lead me to know which weewx.conf it was running with.

Upgrade process console output below,

Thanks in advance

pi@raspberrypi1:~ $ sudo apt-get update
Get:1 http://weewx.com/apt/python3 buster InRelease [3,906 B]
Get:2 http://weewx.com/apt/python3 buster/main all Packages [1,725 B]                                                
Get:3 http://archive.raspberrypi.org/debian buster InRelease [32.7 kB]                             
Get:4 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]                   
Get:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [349 kB]
Get:6 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]    
Fetched 13.4 MB in 8s (1,664 kB/s)                                                                                                                  
Reading package lists... Done
pi@raspberrypi1:~ $ sudo apt-get install weewx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  lxplug-volume python-cheetah python-configobj python-usb
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  sqlite ftp
The following packages will be upgraded:
  weewx
1 upgraded, 0 newly installed, 0 to remove and 39 not upgraded.
Need to get 1,201 kB of archives.
After this operation, 18.4 kB disk space will be freed.
Get:1 http://weewx.com/apt/python3 buster/main all weewx all 4.3.0-1 [1,201 kB]
Fetched 1,201 kB in 1s (1,731 kB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 102302 files and directories currently installed.)
Preparing to unpack .../archives/weewx_4.3.0-1_all.deb ...
Unpacking weewx (4.3.0-1) over (4.2.0-1) ...
Setting up weewx (4.3.0-1) ...
Installing new version of config file /etc/weewx/skins/Mobile/skin.conf ...

Configuration file '/etc/weewx/skins/Seasons/skin.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   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.
*** skin.conf (Y/I/N/O/D/Z) [default=N] ? n
Installing new version of config file /etc/weewx/skins/Smartphone/skin.conf ...
Installing new version of config file /etc/weewx/skins/Standard/skin.conf ...
Installing new version of config file /etc/weewx/udev/rules.d/cc3000.rules ...
Installing new version of config file /etc/weewx/udev/rules.d/weewx.rules ...

Configuration file '/etc/weewx/weewx.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   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] ? n
Installing new version of config file /etc/weewx/weewx.conf.dist ...
saving previous config file as /etc/weewx/weewx.conf-4.2.0
saving distribution config file as /etc/weewx/weewx.conf-4.3.0
merging previous and distribution into /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf-4.2.0
Processing triggers for systemd (241-7~deb10u5+rpi1) ...

[Tom Keffer]

You probably already are using the new version. By default, weewx uses whatever is in /etc/weewx/weewx.conf.

You can check by looking at the log when weewxd starts up. It will have an entry such as 

Jan  5 15:33:11 nuc weewx[37193] INFO __main__: Initializing weewx version 4.3.0
Jan  5 15:33:11 nuc weewx[37193] INFO __main__: Using Python 2.7.18 (default, Dec 15 2020, 08:30:09) #012[GCC 9.3.0]
Jan  5 15:33:11 nuc weewx[37193] INFO __main__: Platform Linux-5.4.0-59-generic-x86_64-with-debian-bullseye-sid
Jan  5 15:33:11 nuc weewx[37193] INFO __main__: Locale is 'en_US.UTF-8'
Jan  5 15:33:11 nuc weewx[37193] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Jan  5 15:33:11 nuc weewx[37193] INFO __main__: Debug is 1

--
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/54d82ead-1eb6-4a88-ac51-d92956ebe842n%40googlegroups.com.

[John Mora]

Thank you for the quick response.
You, of course, are correct. Those log entries are exactly what the log file does show when I look at the file itself. Unfortunately while viewing the syslog file in the console after restarting weewx with "sudo tail -f /var/log/syslog" I see one entry:
Jan  5 16:28:38 raspberrypi1 weewx[8051] INFO __main__: Starting up weewx version 4.3.0
but that is the only startup message with "__main__" within it that is printed to console. If I had seen the other relevant entries which are actually in the log, I would have seen that weewx actually did start using weewx.conf.

I will know to look at the actual log whenever anything is in question in the future and not fully trust the console output. Once again, thank you for your time.

Cheers!