From abdf04d7525a00a0d168d58e797c16b2c11ac3e7 Mon Sep 17 00:00:00 2001 From: "tomh.org" Date: Wed, 29 Jul 2009 23:32:59 +0000 Subject: [PATCH] Update troubleshooting for non-existent cored problem. --- wiki/Troubleshooting.wiki | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/wiki/Troubleshooting.wiki b/wiki/Troubleshooting.wiki index f4c3391a..bd76703d 100644 --- a/wiki/Troubleshooting.wiki +++ b/wiki/Troubleshooting.wiki @@ -2,14 +2,20 @@ == 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... 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. -== Linux OpenVz version == - == FreeBSD version == -Add your content here. +Add your content here. \ No newline at end of file