Status not available message at /hobbit-cgi/bb-hostsvc.sh?HOSTSVC=...
Hey guys, please forgive the newbie...
Installed hobbit yesterday, and very happy... been fighting with big brother issues for too long :)
I keep ending up getting 'Status not available' messages when I click on any of the icons to view the current state of a service... For a while after I start hobbit (using starthobbit.sh), the pages work fine, then I end up getting the 'Status not available' page, accompanied by the following in the hobbitlaunch.log file.
2005-02-11 14:02:19 Setting up network listener on 10.2.0.9:1984 2005-02-11 14:02:19 Cannot bind to listen socket (Address already in use)
I also notice that hobbitd and it's accosiated services have stopped.
Any known issues?
Thanks in advance,
...Steve...
On Fri, Feb 11, 2005 at 02:10:12PM -0800, Anonymous wrote:
Hey guys, please forgive the newbie...
Installed hobbit yesterday, and very happy... been fighting with big brother issues for too long :)
I keep ending up getting 'Status not available' messages when I click on any of the icons to view the current state of a service...
This indicates that either you're asking for a status that does not exist, or the Hobbit daemon (hobbitd) is not running.
2005-02-11 14:02:19 Setting up network listener on 10.2.0.9:1984 2005-02-11 14:02:19 Cannot bind to listen socket (Address already in use)
Sounds like something else (Big Brother ?) is now running and has taken over port 1984.
I also notice that hobbitd and it's accosiated services have stopped.
Any known issues?
This sounds mostly like a local setup problem, with Hobbit and Big Brother struggling over the same ressources. If hobbitd cannot start, then all of the other Hobbit tasks will not run either.
Henrik
Morning, and happy monday...
I would agree with this, save for the fact that bigbrother has been completely removed from the system, and hobbit starts and runs wonderfully for 5 minutes exactly. After the 5 minutes is up, hobbitd terminates with a sig 6 (I assume intentionally from hobbitlaunch), and tries to restart within a second... It tries to restart 5 times (correctly), and fails each time, saying that the address is already in use. 10 minutes later, it starts without issue... I've included the relevant log file at the end...
My guess would be that the service is trying to start before all resources relating to it have been freed (socket, specifically). Is there any easy way to introduce a delay to test this?
Another question... I've hardcoded 10.2.0.9 into my hobbitlaunch.cfg. Why is the servier still trying to start listening on 0.0.0.0?
Cheers...
...Steve...
Here is the log file...
2005-02-14 10:58:28 hobbitlaunch starting 2005-02-14 10:58:28 Loading tasklist configuration from /usr/local/hobbit/server/etc/hobbitlaunch.cfg 2005-02-14 10:58:28 Task hobbitd started with PID 18467 2005-02-14 10:58:28 Setting up network listener on 0.0.0.0:1984 2005-02-14 10:58:28 Setting up signal handlers 2005-02-14 10:58:28 Setting up hobbitd channels 2005-02-14 10:58:28 Setting up logfiles 2005-02-14 10:58:28 Setup complete 2005-02-14 10:58:33 Task bbhistory started with PID 18470 2005-02-14 10:58:33 Task bbenadis started with PID 18472 2005-02-14 10:58:33 Task bbpage started with PID 18473 2005-02-14 10:58:33 Task larrdstatus started with PID 18474 2005-02-14 10:58:33 Task larrddata started with PID 18478 2005-02-14 10:58:33 Task bbdisplay started with PID 18479 2005-02-14 10:58:33 Task bbnet started with PID 18480 2005-02-14 10:58:33 Task bbretest started with PID 18482 2005-02-14 10:58:33 Task larrdcolumn started with PID 18490 2005-02-14 10:58:33 Task infocolumn started with PID 18491 2005-02-14 10:59:34 Task bbdisplay started with PID 18505 2005-02-14 10:59:34 Task bbretest started with PID 18506 2005-02-14 11:00:34 Task bbdisplay started with PID 18515 2005-02-14 11:00:34 Task bbretest started with PID 18516 2005-02-14 11:01:36 Task bbdisplay started with PID 18523 2005-02-14 11:01:36 Task bbretest started with PID 18524 2005-02-14 11:02:36 Task bbdisplay started with PID 18531 2005-02-14 11:02:36 Task bbretest started with PID 18532 2005-02-14 11:03:31 Task hobbitd terminated by signal 6 2005-02-14 11:03:31 Task hobbitd started with PID 18534 2005-02-14 11:03:31 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:03:31 Cannot bind to listen socket (Address already in use) 2005-02-14 11:03:31 Task hobbitd terminated, status 1 2005-02-14 11:03:31 Task hobbitd started with PID 18535 2005-02-14 11:03:31 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:03:31 Cannot bind to listen socket (Address already in use) 2005-02-14 11:03:31 Task hobbitd terminated, status 1 2005-02-14 11:03:31 Task hobbitd started with PID 18536 2005-02-14 11:03:31 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:03:31 Cannot bind to listen socket (Address already in use) 2005-02-14 11:03:31 Task hobbitd terminated, status 1 2005-02-14 11:03:31 Task hobbitd started with PID 18537 2005-02-14 11:03:31 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:03:31 Cannot bind to listen socket (Address already in use) 2005-02-14 11:03:31 Task hobbitd terminated, status 1 2005-02-14 11:03:31 Task hobbitd started with PID 18538 2005-02-14 11:03:31 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:03:31 Cannot bind to listen socket (Address already in use) 2005-02-14 11:03:31 Task hobbitd terminated, status 1 2005-02-14 11:13:32 Task hobbitd started with PID 18589 2005-02-14 11:13:32 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:13:32 Setting up signal handlers 2005-02-14 11:13:32 Setting up hobbitd channels 2005-02-14 11:13:32 Setting up logfiles 2005-02-14 11:13:32 Setup complete 2005-02-14 11:13:37 Task bbhistory started with PID 18590 2005-02-14 11:13:37 Task bbenadis started with PID 18591 2005-02-14 11:13:37 Task bbpage started with PID 18592 2005-02-14 11:13:37 Task larrdstatus started with PID 18596 2005-02-14 11:13:37 Task larrddata started with PID 18597 2005-02-14 11:13:37 Task bbdisplay started with PID 18598 2005-02-14 11:13:37 Task bbnet started with PID 18601 2005-02-14 11:13:37 Task bbretest started with PID 18602 2005-02-14 11:13:37 Task larrdcolumn started with PID 18611 2005-02-14 11:13:37 Task infocolumn started with PID 18612 2005-02-14 11:14:38 Task bbdisplay started with PID 18615 2005-02-14 11:14:38 Task bbretest started with PID 18616 2005-02-14 11:15:38 Task bbdisplay started with PID 18618 2005-02-14 11:15:38 Task bbretest started with PID 18619 2005-02-14 11:16:38 Task bbdisplay started with PID 18626 2005-02-14 11:16:38 Task bbretest started with PID 18627 2005-02-14 11:17:38 Task bbdisplay started with PID 18629 2005-02-14 11:17:38 Task bbretest started with PID 18630 2005-02-14 11:18:34 Task hobbitd terminated by signal 6 2005-02-14 11:18:34 Task hobbitd started with PID 18633 2005-02-14 11:18:34 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:18:34 Cannot bind to listen socket (Address already in use) 2005-02-14 11:18:34 Task hobbitd terminated, status 1 2005-02-14 11:18:34 Task hobbitd started with PID 18634 2005-02-14 11:18:34 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:18:34 Cannot bind to listen socket (Address already in use) 2005-02-14 11:18:34 Task hobbitd terminated, status 1 2005-02-14 11:18:34 Task hobbitd started with PID 18635 2005-02-14 11:18:34 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:18:34 Cannot bind to listen socket (Address already in use) 2005-02-14 11:18:34 Task hobbitd terminated, status 1 2005-02-14 11:18:34 Task hobbitd started with PID 18636 2005-02-14 11:18:34 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:18:34 Cannot bind to listen socket (Address already in use) 2005-02-14 11:18:34 Task hobbitd terminated, status 1 2005-02-14 11:18:34 Task hobbitd started with PID 18637 2005-02-14 11:18:34 Setting up network listener on 0.0.0.0:1984 2005-02-14 11:18:34 Cannot bind to listen socket (Address already in use) 2005-02-14 11:18:34 Task hobbitd terminated, status 1
On Fri, 2005-02-11 at 23:56, Henrik Stoerner wrote:
On Fri, Feb 11, 2005 at 02:10:12PM -0800, Anonymous wrote:
Hey guys, please forgive the newbie...
Installed hobbit yesterday, and very happy... been fighting with big brother issues for too long :)
I keep ending up getting 'Status not available' messages when I click on any of the icons to view the current state of a service...
This indicates that either you're asking for a status that does not exist, or the Hobbit daemon (hobbitd) is not running.
2005-02-11 14:02:19 Setting up network listener on 10.2.0.9:1984 2005-02-11 14:02:19 Cannot bind to listen socket (Address already in use)
Sounds like something else (Big Brother ?) is now running and has taken over port 1984.
I also notice that hobbitd and it's accosiated services have stopped.
Any known issues?
This sounds mostly like a local setup problem, with Hobbit and Big Brother struggling over the same ressources. If hobbitd cannot start, then all of the other Hobbit tasks will not run either.
Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Mon, Feb 14, 2005 at 11:35:51AM -0800, Anonymous wrote:
Morning, and happy monday...
I would agree with this, save for the fact that bigbrother has been completely removed from the system, and hobbit starts and runs wonderfully for 5 minutes exactly. After the 5 minutes is up, hobbitd terminates with a sig 6 (I assume intentionally from hobbitlaunch)
Signal 6 is never intentional! That means the program aborted due to a fatal error, and usually this is accompanied by a core dump.
Could you send me your hobbitlaunch.cfg and hobbitserver.cfg files, the hobbitd binary, and if you find a core file in the hobbit-users home-directory or the server/tmp/ directory that one as well.
Thanks, Henrik
participants (2)
-
anonymous@example.com
-
henrik@hswn.dk