On 29/04/2016 18:40, Roland Kammerer wrote:
On Fri, Apr 29, 2016 at 09:21:17AM +1000, Adam Goryachev wrote:
When upgrading from python-drbdmanage 0.94-1 to 0.95-1 using the packages
available at:
http://oss.linbit.com/drbdmanage/packages/drbdmanage-0.95/debian-jessie/
The following is the output:
dpkg -i python-drbdmanage_0.95-1_all.deb
(Reading database ... 48347 files and directories currently installed.)
Preparing to unpack python-drbdmanage_0.95-1_all.deb ...
Unpacking python-drbdmanage (0.95-1) over (0.94-1) ...
Setting up python-drbdmanage (0.95-1) ...
Job for drbdmanaged.socket failed. See 'systemctl status drbdmanaged.socket'
and 'journalctl -xn' for details.
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
systemctl status drbdmanaged.socket
● drbdmanaged.socket - DRBDManage Service
Loaded: loaded (/lib/systemd/system/drbdmanaged.socket; enabled)
Active: inactive (dead) since Fri 2016-04-29 09:15:04 AEST; 46s ago
Listen: [::]:6996 (Stream)
drbdmanage still shows that it is running and working (presumably the old
version). Doing a reboot solves the problem, but I would think the package
upgrade should handle this more smoothly. Any suggestions or ideas?
Is this a satellite node or a control node?
Control node.
I repeated the same upgrade on a second control node, with identical
results.
How was that enabled at all in the first place? By you or was it picked
up "magically" by systemd?
I didn't do anything more than install the python-drbdmanage package, so
either the package did something to make it work, or else systemd
"magically" picked it up.
Regards,
Adam
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
