Re: Koan 111 Connection Refused errors

[Michael DeHaan]

On 07/10/2009 08:59 PM, William Sweat wrote:
>  Hello,
>
>  May be this has been addressed, but I still haven't found anything in 
>  the archives about this yet.
>
>  I've done a basic cobbler setup and whenever I run "koan 
>  --list-profiles --s someserver" I get the error:
>
>  [root@localhost ~]# koan --list-profiles -s someserver Traceback (most 
>  recent call last):
>
>    File "/usr/lib/python2.4/site-packages/koan/app.py", line 440, in 
>  get_profiles_xmlrpc
>
>      data = self.xmlrpc_server.get_profiles()
>
>    File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__
>
>      return self.__send(self.__name, args)
>
>    File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request
>
>      verbose=self.__verbose
>
>    File "/usr/lib64/python2.4/xmlrpclib.py", line 1129, in request
>
>      self.send_content(h, request_body)
>
>    File "/usr/lib64/python2.4/xmlrpclib.py", line 1243, in send_content
>
>      connection.endheaders()
>
>    File "/usr/lib64/python2.4/httplib.py", line 804, in endheaders
>
>      self._send_output()
>
>    File "/usr/lib64/python2.4/httplib.py", line 685, in _send_output
>
>      self.send(msg)
>
>    File "/usr/lib64/python2.4/httplib.py", line 652, in send
>
>      self.connect()
>
>    File "/usr/lib64/python2.4/httplib.py", line 636, in connect
>
>      raise socket.error, msg
>
>  error: (111, 'Connection refused')
>
>  Could not communicate with someserver:25151
>
>  My cobbler server is not running any firewall and selinux is disabled 
>  (and have even removed it).  I can telnet to port 111 with no problem, 
>  but when I telnet to 25151 I get a connection refused.  So the server 
>  is accepting the connection, but something in the python code (or 
>  maybe apache) is kicking it out.
>  

Seems like a simple configuration issue to me.

Make sure cobblerd is running on the remote end and you have the right 
files in /etc/httpd/conf.d ... checking for any .rpmnews there (if this 
was an upgrade), and then restart httpd.

--Michael