[tor-relays] tor fails on start-up after yum update

[Eddie]

Running a CentOS 7.9 system, pulling tor updates from 
https://rpm.torproject.org/centos/$releasever/$basearch

The last 2 times that tor has been yum updated, the restart of the 
service has just stopped, at exactly the same point:

Jun 18 06:46:50.000 [notice] Tor 0.4.6.5 opening log file.
Jun 18 06:46:50.830 [notice] We compiled with OpenSSL 100020bf: OpenSSL 
1.0.2k  26 Jan 2017 and we are running with OpenSSL 100020bf: 
1.0.2k-fips. These two versions should be binary compatible.
Jun 18 06:46:50.831 [notice] Tor 0.4.6.5 running on Linux with Libevent 
2.0.21-stable, OpenSSL 1.0.2k-fips, Zlib 1.2.7, Liblzma 5.2.2, Libzstd 
1.5.0 and Glibc 2.17 as libc.
Jun 18 06:46:50.831 [notice] Tor can't help you if you use it wrong! 
Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 18 06:46:50.831 [notice] Read configuration file 
"/usr/share/tor/defaults-torrc".
Jun 18 06:46:50.831 [notice] Read configuration file "/etc/tor/torrc".
Jun 18 06:46:50.833 [notice] Based on detected system memory, 
MaxMemInQueues is set to 6342 MB. You can override this by setting 
MaxMemInQueues by hand.
Jun 18 06:46:50.833 [notice] You configured a non-loopback address 
'192.168.0.254:9100' for SocksPort. This allows everybody on your local 
network to use your machine as a proxy. Make sure this is what you wanted.
Jun 18 06:46:50.833 [notice] Opening Socks listener on 192.168.0.254:9100
Jun 18 06:46:50.833 [notice] Opened Socks listener connection (ready) on 
192.168.0.254:9100
Jun 18 06:46:50.833 [notice] Opening Control listener on 127.0.0.1:9051
Jun 18 06:46:50.833 [notice] Opened Control listener connection (ready) 
on 127.0.0.1:9051
Jun 18 06:46:50.833 [notice] Opening OR listener on 0.0.0.0:9001
Jun 18 06:46:50.834 [notice] Opened OR listener connection (ready) on 
0.0.0.0:9001
Jun 18 06:46:50.834 [notice] Opening Directory listener on 0.0.0.0:9030
Jun 18 06:46:50.834 [notice] Opened Directory listener connection 
(ready) on 0.0.0.0:9030
Jun 18 06:46:51.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.

Starting the service then it starts correctly.  I also couldn't see 
anything out of the ordinary in the main system logs, other than it 
echoing the above.

Any ideas on what's going on here.

Also, what is the correct setting for systemctl enable/disable 
tor/tor-master  (I don't have any tor@ services), because I get 
inconsistent results using tor-master.  Issuing "systemctl stop 
tor-master" will stop the accompanying tor instance, but "systemctl 
start tor-master" doesn't start it, but a "systemctl restart tor-master" 
does do a stop/start.  I haven't had time to experiment with what 
happens on a re-boot (yet).

Cheers.