FWIW, I have seen this as well ... usually after a weekend. In my mind
I have been blaming logrotate. My fix is the same as Jan's, stop dhcpd,
stop cobblerd, start cobblerd and finally start dhcpd and all is well.
I have been running this on a RHEL 5 server if it matters.
Marc Mondragon
Fox River Partners LLC./CRT Trading LLC.
2100 Enterprise Avenue
Geneva, IL 60134
marcmo@foxriver.com
> Date: Tue, 05 Feb 2008 00:34:21 +0100
> From: Jan Wildeboer <jwildebo@redhat.com>
> Subject: Re: [et-mgmt-tools] re: "invalid kernel" -- found the
> problem!
> To: Fedora/Linux Management Tools <et-mgmt-tools@redhat.com>
> Message-ID: <1202168061.4093.66.camel@jhwx61.muc.redhat.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Some more details.
>
> I hammered cobbler sync, initiated by webui and console and could not
> reproduce.
>
> But a simple service cobbler restart did the trick. Now I have dhcpd
> listening on 25152 and a b0rk3d xmlrpc for cobbler.
>
> In the cobbler.log I see (not surprising):
>
> 2008-02-05 00:26:30,696 - cobbler.cobblerd - DEBUG - started
> 2008-02-05 00:26:30,865 - cobbler.cobblerd - INFO - XMLRPC running on
> 25151
> 2008-02-05 00:26:30,868 - cobbler.cobblerd - INFO - Exception occured:
> socket.error
> 2008-02-05 00:26:30,869 - cobbler.cobblerd - INFO - Exception value:
> (98, 'Address already in use')
> 2008-02-05 00:26:30,871 - cobbler.cobblerd - INFO - syslog running on
> 25150
> 2008-02-05 00:26:30,893 - cobbler.cobblerd - INFO - Exception Info:
> File "/usr/bin/cobblerd", line 66, in ?
> app.core(logger=logger)
> File "/usr/lib/python2.4/site-packages/cobbler/cobblerd.py", line
44,
> in core
> do_xmlrpc_tasks(bootapi, settings, xmlrpc_port, xmlrpc_port2,
> logger)
> File "/usr/lib/python2.4/site-packages/cobbler/cobblerd.py", line
55,
> in do_xmlrpc_tasks
> do_xmlrpc_rw(bootapi, settings, xmlrpc_port2, logger)
> File "/usr/lib/python2.4/site-packages/cobbler/cobblerd.py", line
> 114, in do_xmlrpc_rw
> server = remote.CobblerReadWriteXMLRPCServer(('127.0.0.1', port))
> File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line
805,
> in __init__
> SimpleXMLRPCServer.SimpleXMLRPCServer.__init__(sel f,args)
> File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 473, in
> __init__
> SocketServer.TCPServer.__init__(self, addr, requestHandler)
> File "/usr/lib/python2.4/SocketServer.py", line 330, in __init__
> self.server_bind()
> File "/usr/lib/python2.4/SocketServer.py", line 341, in server_bind
> self.socket.bind(self.server_address)
> File "<string>", line 1, in bind
>
> service dhcpd restart cleans up that part:
>
> [root@vinf02 ~]# service dhcpd restart
> Shutting down dhcpd: [ OK ]
> Starting dhcpd: [ OK ]
> [root@vinf02 ~]# netstat -alp | grep 25
> tcp 0 0 *:25151 *:*
> LISTEN 30016/python
> udp 0 0 *:25150 *:*
> 30013/python
>
> But now still a missing 25152, so lets try with
>
> [root@vinf02 ~]# service cobblerd stop
> Stopping cobbler daemon: [ OK ]
> [root@vinf02 ~]# service cobblerd start
> Starting cobbler daemon: [ OK ]
> [root@vinf02 ~]# netstat -alp | grep 25
> tcp 0 0 localhost.localdomain:25152 *:*
> LISTEN 30105/python
> tcp 0 0 *:25151 *:*
> LISTEN 30106/python
> udp 0 0 *:25150 *:*
> 30103/python
> unix 2 [ ] DGRAM 3825
> 1144/rpc.statd
>
>
> All fine again.
>
> Now for debugging that - not today, I am off to bed.
>
> Jan
>
> --
> Jan H Wildeboer |
> Solution Architect, RHCE | Office: +49 (0)89 205071-207
> Red Hat GmbH | Mobile: +49 (0)174 33 23 249
> Otto-Hahn-Str.20 | Fax: +49 (0)89 205071-111
> D-85609 Dornach/Munich | eMail: jan.wildeboer@redhat.com
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
02-05-2008, 04:27 PM
Michael DeHaan
et-mgmt-tools Digest, Vol 18, Issue 7
Marc Mondragon wrote:
FWIW, I have seen this as well ... usually after a weekend. In my mind
I have been blaming logrotate. My fix is the same as Jan's, stop dhcpd,
stop cobblerd, start cobblerd and finally start dhcpd and all is well.
Older versions of cobbler didn't restart cobblerd on logrotate. What
version are you running?
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools