hobbitd keeps dying, cannot bind...
list Kent Brodie
Same cluster setup - the node I'm having all my issues with is my cluster head node- the one that's the server, and also the proxy server. I am having a devil of a time keeping hobbit running. Sometimes I can get it going... but it never seems to stay up for more than 5 minutes, and even after a full clean reboot, I can't get hobbitd to start at all. Here's my relevant log info: Hobbitlaunch.log: 2006-07-24 11:28:27 hobbitlaunch starting 2006-07-24 11:28:27 Loading tasklist configuration from /home/hobbit/server/etc/hobbitlaunch.cfg 2006-07-24 11:28:27 Loading hostnames 2006-07-24 11:28:27 Loading saved state 2006-07-24 11:28:27 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:27 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:27 Task hobbitd terminated, status 1 2006-07-24 11:28:32 Loading hostnames 2006-07-24 11:28:32 Loading saved state 2006-07-24 11:28:32 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:32 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:32 Task hobbitd terminated, status 1 2006-07-24 11:28:37 Loading hostnames 2006-07-24 11:28:37 Loading saved state 2006-07-24 11:28:37 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:37 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:37 Task hobbitd terminated, status 1 2006-07-24 11:28:42 Loading hostnames 2006-07-24 11:28:42 Loading saved state 2006-07-24 11:28:42 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:42 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:42 Task hobbitd terminated, status 1 2006-07-24 11:28:47 Loading hostnames 2006-07-24 11:28:47 Loading saved state 2006-07-24 11:28:47 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:47 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:47 Task hobbitd terminated, status 1 2006-07-24 11:28:52 Loading hostnames 2006-07-24 11:28:52 Loading saved state 2006-07-24 11:28:52 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:52 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:52 Task hobbitd terminated, status 1 Bbproxy.log: 2006-07-24 11:28:27 bbproxy version 4.2-RC-20060712 starting 2006-07-24 11:28:27 Listening on 0.0.0.0:1984 2006-07-24 11:28:27 Sending to BBDISPLAY(s) 141.106.224.202:1984 2006-07-24 11:28:27 Sending to BBPAGER(s) 141.106.224.202:1984 Is there some conflict having a hobbit server and proxy going at once?
list Steve Aiello
2006-07-24 11:28:27 Setting up network listener on 0.0.0.0:1984 I believe means it is binding on every IP address on port 1984. Thus bbproxy & hobbit are figting. To have bbproxy listen to one particular IP, use the "--listen=IPAddress:port". You can use the same option when starting hobbitd, too.
▸
-----Original Message-----
From: Brodie, Kent [mailto:user-8fbf1c81e97c@xymon.invalid]
Sent: Monday, July 24, 2006 12:33 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] hobbitd keeps dying, cannot bind...
Same cluster setup - the node I'm having all my issues with is my
cluster head node- the one that's the server, and also the proxy
server.
I am having a devil of a time keeping hobbit running. Sometimes I can
get it going... but it never seems to stay up for more than 5 minutes,
and even after a full clean reboot, I can't get hobbitd to start at all.
Here's my relevant log info:
Hobbitlaunch.log:
2006-07-24 11:28:27 hobbitlaunch starting
2006-07-24 11:28:27 Loading tasklist configuration from
/home/hobbit/server/etc/hobbitlaunch.cfg
2006-07-24 11:28:27 Loading hostnames
2006-07-24 11:28:27 Loading saved state
2006-07-24 11:28:27 Setting up network listener on 0.0.0.0:1984
2006-07-24 11:28:27 Cannot bind to listen socket (Address already in
use)
2006-07-24 11:28:27 Task hobbitd terminated, status 1
2006-07-24 11:28:32 Loading hostnames
2006-07-24 11:28:32 Loading saved state
2006-07-24 11:28:32 Setting up network listener on 0.0.0.0:1984
2006-07-24 11:28:32 Cannot bind to listen socket (Address already in
use)
2006-07-24 11:28:32 Task hobbitd terminated, status 1
2006-07-24 11:28:37 Loading hostnames
2006-07-24 11:28:37 Loading saved state
2006-07-24 11:28:37 Setting up network listener on 0.0.0.0:1984
2006-07-24 11:28:37 Cannot bind to listen socket (Address already in
use)
2006-07-24 11:28:37 Task hobbitd terminated, status 1
2006-07-24 11:28:42 Loading hostnames
2006-07-24 11:28:42 Loading saved state
2006-07-24 11:28:42 Setting up network listener on 0.0.0.0:1984
2006-07-24 11:28:42 Cannot bind to listen socket (Address already in
use)
2006-07-24 11:28:42 Task hobbitd terminated, status 1
2006-07-24 11:28:47 Loading hostnames
2006-07-24 11:28:47 Loading saved state
2006-07-24 11:28:47 Setting up network listener on 0.0.0.0:1984
2006-07-24 11:28:47 Cannot bind to listen socket (Address already in
use)
2006-07-24 11:28:47 Task hobbitd terminated, status 1
2006-07-24 11:28:52 Loading hostnames
2006-07-24 11:28:52 Loading saved state
2006-07-24 11:28:52 Setting up network listener on 0.0.0.0:1984
2006-07-24 11:28:52 Cannot bind to listen socket (Address already in
use)
2006-07-24 11:28:52 Task hobbitd terminated, status 1
Bbproxy.log:
2006-07-24 11:28:27 bbproxy version 4.2-RC-20060712 starting
2006-07-24 11:28:27 Listening on 0.0.0.0:1984
2006-07-24 11:28:27 Sending to BBDISPLAY(s) 141.106.224.202:1984
2006-07-24 11:28:27 Sending to BBPAGER(s) 141.106.224.202:1984
Is there some conflict having a hobbit server and proxy going at once?
list Rob MacGregor
▸
On 7/24/06, Brodie, Kent <user-8fbf1c81e97c@xymon.invalid> wrote:
Is there some conflict having a hobbit server and proxy going at once?
Only one process can listen on a given port (and interface).
You'll either have to change the port one uses (probably break
something), have one listen on a virtual interface, or move one to
another host.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
list Kolbjørn Barmen
▸
On Mon, 24 Jul 2006, Brodie, Kent wrote:
2006-07-24 11:28:27 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:27 Cannot bind to listen socket (Address already in use)
Shot in the dark... is the box configured with IPv6 perhaps? -- Kolbjørn Barmen UNINETT Driftsenter
list Henrik Størner
▸
On Mon, Jul 24, 2006 at 11:33:29AM -0500, Brodie, Kent wrote:
2006-07-24 11:28:27 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:27 Task hobbitd terminated, status 1
Is there some conflict having a hobbit server and proxy going at once?
Yes, you should only have one of those running on the same node. In your setup, there is no reason to run the [hobbitd] task on your cluster master-node. The master node should only run the [bbproxy], [bbnet] and [hobbitclient] tasks. For the last two items, remove the "NEEDS hobbitd" line or they won't start up. Regards, Henrik