This commit is contained in:
tomh.org 2009-08-05 17:48:19 +00:00
parent 50d1181062
commit 928bfd1da8

View file

@ -24,7 +24,7 @@ Failed to open API channel to 127.0.0.1:4038: couldn't open socket: connection r
* *Resolution:* This suggests that cored was not running or is hung. Try "sudo killall cored", and if no process was killed, check also that there is not a /var/run/cored.pid file lying around. Try restarting cored in verbose mode: "sudo /usr/local/sbin cored -v" and if that works, restart it in daemon mode such as: "sudo /usr/local/sbin/cored -d". Check the log file in /var/log/cored.log if all else fails. * *Resolution:* This suggests that cored was not running or is hung. Try "sudo killall cored", and if no process was killed, check also that there is not a /var/run/cored.pid file lying around. Try restarting cored in verbose mode: "sudo /usr/local/sbin cored -v" and if that works, restart it in daemon mode such as: "sudo /usr/local/sbin/cored -d". Check the log file in /var/log/cored.log if all else fails.
* *Issue:* when starting multiple quagga routers, only some come up into operational state. * *Issue:* when starting multiple quagga routers, only some come up into operational state.
* *Resolution:* This is flakiness with the OpenVz version of CORE. I have noticed that sometimes the containers start without interface lo in an "UP" state, and that zebra sometimes does not start successfully. If you find a node in this state, here are some suggested resolution steps: * *Resolution:* This is flakiness with the OpenVZ version of CORE. I have noticed that sometimes the containers start without interface lo in an "UP" state, and that zebra sometimes does not start successfully. If you find a node in this state, here are some suggested resolution steps:
{{{ {{{
killall zebra ospfd ospf6d killall zebra ospfd ospf6d
ifconfig lo up ifconfig lo up