Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Jun 08, 2016 at 01:14:07PM +1000, Adam Goryachev wrote: > From my previous thread which started talking about problems compiling the > kernel module, now talking about problems with a satellite node. > > On 08/06/16 00:14, Roland Kammerer wrote: > >>>it seems my satellite node can't connect to any other nodes... > >They don't connect, they listen for connections from their control node. > > > >>>This is one of the other nodes: > >For all list-* commands, use the "-p" option, it generates > >readable/pastable output for mailing lists/bug reports. > > > >To make sure the satellite node starts as satellite, add this to > >/etc/drbdmanaged.cfg: > >ctrl-volume-access-mode = satellite > > > >Then "drbdmanage restart -q" on the satellite > Did that and got this: > root at xen6:/etc# drbdmanage restart -q > ERROR:dbus.proxies:Introspect error on :1.5:/interface: > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message > recipient disconnected from message bus without replying > Attempting to startup the server through D-Bus activation... > ERROR:dbus.proxies:Introspect error on :1.6:/interface: > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message > recipient disconnected from message bus without replying > > D-Bus connection FAILED -- the D-Bus server may have been unable to activate > the drbdmanage service. > Review the syslog for error messages logged by the D-Bus server > or the drbdmanage server. Hi, please make sure that there is no leftover drbdmanaged process running. - drbdmanage shutdown -q - ps aux | drbdmange # and kill if necessary. -drbdmanage uninit -q # get rid of the control volume if for whatever reason it was created - drbdmanage startup Regards, rck