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

Update troubleshooting for non-existent cored problem.

Browse source
This commit is contained in:
tomh.org 2009-07-29 23:32:59 +00:00
parent b0bbc8782f
commit abdf04d752
1 changed files with 10 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
wiki/Troubleshooting.wiki
View file

@ -2,14 +2,20 @@
== General == == General ==
* *Issue:* when starting CORE GUI, you get a console message such as
== Linux OpenVz version ==
* *Issue:* I start Core and place a host into the GUI and press Start. I get the following error for just doing that
{{{
can not find channel named "-1"
can not find channel named "-1"
}}}
also, my console may display this error:
{{{ {{{
Connecting to 127.0.0.1:4038... Connecting to 127.0.0.1:4038...
Failed to open API channel to 127.0.0.1:4038: couldn't open socket: connection refused 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. * *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.
== Linux OpenVz version ==
== FreeBSD version == == FreeBSD version ==
Add your content here. Add your content here.