Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 8/06/2016 18:01, Roland Kammerer wrote: > 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 > root at xen6:~# drbdmanage shutdown -q ERROR:dbus.proxies:Introspect error on :1.9:/interface: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying root at xen6:~# ps axu | grep drbdmanage root 1309 0.0 0.0 12744 2200 pts/1 S+ 22:02 0:00 grep drbdmanage root at xen6:~# drbdmanage uninit -q Failed to find logical volume "drbdpool/.drbdctrl_0" Failed to find logical volume "drbdpool/.drbdctrl_1" root at xen6:~# drbdmanage startup Attempting to startup the server through D-Bus activation... ERROR:dbus.proxies:Introspect error on :1.11:/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. Here are the logs from syslog Jun 8 22:02:58 xen6 drbdmanaged[1330]: INFO DRBDmanage server, version 0.96.1 -- initializing on node 'xen6' Jun 8 22:02:58 xen6 DRBDmanage:1333: spawning ['drbdadm', 'adjust', '.drbdctrl']no resources defined! Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: .drbdctrl: No such resource Jun 8 22:02:58 xen6 drbdmanaged[1330]: INFO DRBDManage starting as satellite node Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: Traceback (most recent call last): Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/bin/dbus-drbdmanaged-service", line 27, in <module> Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: drbdmanage_server.main() Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/lib/python2.7/dist-packages/drbdmanage_server.py", line 38, in main Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: server.run() Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/lib/python2.7/dist-packages/drbdmanage/server.py", line 547, in run Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: self._proxy.start() Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/lib/python2.7/dist-packages/drbdmanage/proxy.py", line 216, in start Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: self._tcp_server = ThreadedTCPServer((self._host, self._port), ThreadedTCPRequestHandler) Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/lib/python2.7/SocketServer.py", line 417, in __init__ Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: self.server_bind() Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/lib/python2.7/SocketServer.py", line 431, in server_bind Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: self.socket.bind(self.server_address) Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: File "/usr/lib/python2.7/socket.py", line 228, in meth Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: return getattr(self._sock,name)(*args) Jun 8 22:02:58 xen6 org.drbd.drbdmanaged[478]: socket.error: [Errno 98] Address already in use root at xen6:/var/log# netstat -anp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:52134 0.0.0.0:* LISTEN 407/rpc.statd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 337/rpcbind tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 793/sshd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1047/exim4 tcp 0 0 192.168.5.16:22 10.97.0.6:41016 ESTABLISHED 1053/sshd: root at pts tcp 0 132 192.168.5.16:22 192.168.5.100:63011 ESTABLISHED 1277/sshd: root at pts tcp6 0 0 :::111 :::* LISTEN 337/rpcbind tcp6 0 0 :::6996 :::* LISTEN 1/init tcp6 0 0 :::22 :::* LISTEN 793/sshd tcp6 0 0 :::60952 :::* LISTEN 407/rpc.statd tcp6 0 0 ::1:25 :::* LISTEN 1047/exim4 udp 0 0 0.0.0.0:48671 0.0.0.0:* 407/rpc.statd udp 0 0 0.0.0.0:111 0.0.0.0:* 337/rpcbind udp 0 0 0.0.0.0:937 0.0.0.0:* 337/rpcbind udp 0 0 127.0.0.1:1007 0.0.0.0:* 407/rpc.statd udp6 0 0 :::52122 :::* 407/rpc.statd udp6 0 0 :::111 :::* 337/rpcbind udp6 0 0 :::937 :::* 337/rpcbind I'm not sure which "address" is in use? Regards, Adam