Forum

Update to 9.3 on HA cluster

JanH
15 November 2013, 12:16
Hi Hugo,

on HA cluster, important services are managed by heartbeat. Therefore, all runlevels for hiawatha are disabled by default.
Automatic update fails for both active and inactive HA servers and has to be performed manually.

ACTIVE SERVER (Hiawatha is running):
#dpkg -i hiawatha_9.3_amd64.deb
(Reading database ... 69507 files and directories currently installed.)
Preparing to replace hiawatha 9.2 (using .../hiawatha_9.3_amd64.deb) ...
Stopping webserver: Hiawatha
Unpacking replacement hiawatha ...
Setting up hiawatha (9.3) ...
Configuration file `/etc/hiawatha/hiawatha.conf'
==> Modified (by you or by a script) since installation.
Version in package is the same as at last installation.
==> Keeping old config file as default.
insserv: warning: current start runlevel(s) (empty) of script `hiawatha' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `hiawatha' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `hiawatha' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `hiawatha' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `hiawatha' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `hiawatha' overrides LSB defaults (0 1 6).
Processing triggers for man-db ...
Hiawatha webserver successfully updated to v9.3.
# /etc/init.d/hiawatha status
Hiawatha is not running

PROBLEM: Update process stopped Hiawatha on active server, but didn't started it afterwards,
this has to be performed manually.

INACTIVE SERVER (Hiawatha is stopped):
# dpkg -i hiawatha_9.3_amd64.deb
(Reading database ... 51734 files and directories currently installed.)
Preparing to replace hiawatha 9.2 (using hiawatha_9.3_amd64.deb) ...
Hiawatha is not running
invoke-rc.d: initscript hiawatha, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 7
dpkg: trying script from the new package instead ...
Hiawatha is not running
invoke-rc.d: initscript hiawatha, action "stop" failed.
dpkg: error processing hiawatha_9.3_amd64.deb (--install):
subprocess new pre-removal script returned error exit status 7
insserv: warning: current start runlevel(s) (empty) of script `hiawatha' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `hiawatha' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `hiawatha' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `hiawatha' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `hiawatha' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `hiawatha' overrides LSB defaults (0 1 6).
Errors were encountered while processing:
hiawatha_9.3_amd64.deb

PROBLEM: This is much worse, Hiawatha did't update at all just because it was not running!

SUGGESTED BEHAVIOR:
Hiawatha has to update, regardless of its status (started/stopped). After Update, it should come back to it's previous status,
no matter how the runlevels are set.

JanH.




Hugo Leisink
16 November 2013, 22:46
Hiawatha itself doesn't do anything with runlevels. So, it must be somewhere in the Debian init script. I have no time to look into this heartbeat thing, so please let me know what to change.
JanH
19 November 2013, 09:03
Unfortunately, my workload will be too high in the next 3-4 weeks. I'll look into it later, if it's not repaired by then by someone else.
This topic has been closed.