Failure to restart after upgrade

[verdurin]

We upgraded at our site to version 3.3.3 overnight and the daemon failed to restart after the upgrade. A manual restart fixed this.

[ljanyst]

Can you give more details on the config you're running? Especially the user and group settings from /etc/sysconfig/xrootd?

[verdurin]

XROOTD_USER=xrootd
XROOTD_GROUP=xrootd

Let me know if you need any other information.

[dougbenjamin]

I have see the same behaviour -
Here is the time stamp from yum auto update -

Jul 25 03:11:19 Updated: 1:xrootd-libs-3.3.3-1.slc6.x86_64
Jul 25 03:11:19 Installed: 1:xrootd-client-libs-3.3.3-1.slc6.x86_64
Jul 25 03:11:19 Installed: 1:xrootd-server-libs-3.3.3-1.slc6.x86_64
Jul 25 03:11:19 Installed: 1:xrootd-3.3.3-1.slc6.x86_64
Jul 25 03:11:19 Updated: 1:xrootd-client-3.3.3-1.slc6.x86_64
Jul 25 03:11:19 Updated: 1:xrootd-fuse-3.3.3-1.slc6.x86_64
Jul 25 03:11:22 Updated: 1:xrootd-debuginfo-3.3.3-1.slc6.x86_64
Jul 25 03:11:22 Erased: xrootd-server

here is the code snippet from the xrootd log -

130725 03:11:22 15454 usatlas3.2009:24@atlasgridftp02 XrootdFile: closing r dummy
130725 03:11:22 15454 usatlas3.2009:24@atlasgridftp02 XrootdResponse: 0100 sending OK
130725 03:11:22 15454 XrootdXeq: usatlas3.2009:24@atlasgridftp02 disc 0:00:01

[dougbenjamin]

Further information. After the yum auto update -
[root@atl012 ~]# chkconfig --list xrootd
service xrootd supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add xrootd')
[root@atl012 ~]# chkconfig --list cmsd
service cmsd supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add cmsd')

I know that prior to the update xrootd and cmsd were set to restart at levels 345

[dougbenjamin]

Further information for debugging the problem.

Initially on a RHEL 6.4 node I had running xrootd and cmsd with these packages installed -

Installed Packages
xrootd-client.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-client-devel.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-debuginfo.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-fuse.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-libs.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-libs-devel.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-server.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable
xrootd-server-devel.x86_64 1:3.3.1-1.slc6.xu @xrootd-stable

xrootd and cmsd would automatically restart on reboot -

[root@atlfs03 ~]# chkconfig --list xrootd
xrootd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@atlfs03 ~]# chkconfig --list cmsd
cmsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

After issuing the command

[root@atlfs03 ~]# yum update xrootd*

I had installed -

[root@atlfs03 ~]# yum list installed xrootd*
Loaded plugins: rhnplugin
This system is receiving updates from RHN Classic or RHN Satellite.
Installed Packages
xrootd.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-client.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-client-devel.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-client-libs.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-debuginfo.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-devel.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-fuse.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-libs.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-server-devel.x86_64 1:3.3.3-1.slc6 @xrootd-stable
xrootd-server-libs.x86_64 1:3.3.3-1.slc6 @xrootd-stable

and neither xrootd nor cmsd are set to restart after reboot:
[root@atlfs03 ~]# chkconfig --list xrootd
service xrootd supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add xrootd')
[root@atlfs03 ~]# chkconfig --list cmsd
service cmsd supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add cmsd')

In addition -
[root@atlfs03 ~]# service xrootd status
[default] xrootd is stopped
[root@atlfs03 ~]# service cmsd status
[default] cmsd (pid 1921) is running...

[ljanyst]

Thank you for testing guys! It looks like this issue has been caused by somewhat retarded behavior of RPM scriptlet calling sequence when names of packages change.

In this case the the sequence, surprisingly, looked like this:

1. the %pre scriptlet of the new xrootd RPM has been called (sets up the user accounts if needed)
2. the %post scriptlet of the new xrootd RPM has been called (sets up the init scripts and start-up sequences)
3. the %preun scriptlet of the old xrootd-server RPM has been called (stops all the services and cleans up the autostart settings)
4. the %postun scriptlet of the old xrootd-server RPM has been called (does nothing in this case)

Since this problem only appears when the names of the packages are changed (we don't plan to do this anymore) and it's not really clear how I could fix it. I will leave it as it is.