On Thu, 2010-01-14 at 11:49 +0100, Eelco Jepkema wrote: > Steven Dake wrote: > > Are you using network manager? > > I'm sorry, i don't know what network manager is and therefore don't > understand the question. >
Network manager is a daemon that manages your network connections. It sometimes downs and ups interfaces and changes interface IPs with dhcp. Corosync doesn't like this and does not interoperate with Network Manager at this time. To see if its running you can use chkconfig on Fedora/RHEL systems. Not sure about other oses. [sd...@localhost rc3.d]$ chkconfig --list NetworkManager NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off You see above in runlevels 2,3,4,5 network manager is on. That means it is running. > > If you still have corosync running, you can killall -SEGV corosync and a > > event trace will be generated. This event trace can be printed with > > corosync-fplay. The thing I would be interested to see is if one of > > your network interfaces became bound to 127.0.0.1. This might be in > > your syslog as well. > > I'm sorry, I already fixed the issue by manually restarting corosync > because this was a production environment so I can't give you the event > trace. > No problem > I can't find anything in my syslogs to suggest binding to 127.0.0.1 but > must admit I don't quite know what I'm looking for. Is there a string I > could grep for? grepping 127.0.0.1 or 127 or lo from my logs didn't find > anything. > What OS and version are you running? Regards -steve > Best regards, > Eelco Jepkema _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
