afonso/core-extra
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

add some notes about OpenVz/quagga flakiness

Browse source
This commit is contained in:
tomh.org 2009-08-05 17:47:48 +00:00
parent 9aee51f855
commit 50d1181062
1 changed files with 13 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

14
wiki/Troubleshooting.wiki
View file

@ -6,6 +6,7 @@
* `/var/log/coreexecd.log` - CORE execution daemon log file may indicate failed jobs, those commands exiting with a non-zero status
== Linux OpenVZ version ==
* *debugging commands:*
* `vzlist` - lists all running containers
* `brctl show` - lists all bridge devices, see if container veth devices have joined the correct bridges
@ -15,13 +16,24 @@
can not find channel named "-1"
can not find channel named "-1"
}}}
also, my console may display this error:
also, my console may display this error:
{{{
Connecting to 127.0.0.1:4038...
Failed to open API channel to 127.0.0.1:4038: couldn't open socket: connection refused
}}}
* *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.
* *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
ifconfig lo up
zebra -d
ospf -d
ospf6d -d
vtysh -b
}}}
== FreeBSD version ==
* *debugging commands:*
* `vimage -l` - lists all running vimages