Xymon Mailing List Archive search

Task hobbitd terminated, status 1

4 messages in this thread

list Matthew Daubenspeck · Tue, 18 Oct 2005 08:33:37 -0400 ·
For some strange reason, hobbit just stopped working a few days ago.
Client data was no longer being reported and all alerts went purple. I
decided to try a recompile/reinstall just for the heck of it, now I
can't even get hobbitd to start :)

Here is the error from hobbitlaunch.log:

2005-10-18 08:24:10 hobbitlaunch starting
2005-10-18 08:24:10 Loading tasklist configuration from
/home/hobbit/server/etc/hobbitlaunch.cfg
2005-10-18 08:24:10 Loading hostnames
2005-10-18 08:24:10 Loading saved state
2005-10-18 08:24:10 Setting up network listener on 0.0.0.0:1984
2005-10-18 08:24:10 Setting up signal handlers
2005-10-18 08:24:10 Setting up hobbitd channels
2005-10-18 08:24:10 Could not get shm of size 262144: Invalid argument
2005-10-18 08:24:10 Cannot setup status channel
2005-10-18 08:24:10 Task hobbitd terminated, status 1

That's about it, over and over. I searched through the archives and only
came up with a few results, but there didn't really seem to be anything
that solved the problem. Any suggestions?
-- 
  Matthew Daubenspeck
  http://www.oddprocess.org

Gentoo Linux 2.6.12-gentoo-r6 x86_64 AMD Athlon(tm) 64 Processor 2800+
08:25:45 up 86 days, 18:53, 1 user, load average: 0.50, 0.31, 0.21
list Henrik Størner · Tue, 18 Oct 2005 15:17:28 +0200 ·
quoted from Matthew Daubenspeck
On Tue, Oct 18, 2005 at 08:33:37AM -0400, Matthew Daubenspeck wrote:
2005-10-18 08:24:10 Setting up hobbitd channels
2005-10-18 08:24:10 Could not get shm of size 262144: Invalid argument
2005-10-18 08:24:10 Cannot setup status channel
It complains that it cannot setup the shared memory (shm) segments
needed for communicating with the hobbitd_* modules.

First, login as the hobbit user and run "ipcs -m" to see if any 
shared-memory segments exist for this user. When hobbitd is 
stopped there should not be any. If you see something like this:

hobbit at osiris:~$ ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x020289c7 32769      hobbit    600        262144     2
0x030289c7 65538      hobbit    600        262144     2
0x040289c7 98307      hobbit    600        262144     2
0x050289c7 131076     hobbit    600        262144     1
0x060289c7 163845     hobbit    600        32768      1
0x070289c7 196614     hobbit    600        524288     2

and there is no hobbitd running, then the normal cleanup 
didn't happen when hobbitd last stopped. You can use "ipcrm -m <shmid>"
to remove them manually.


If that is not the problem (ie. there are no shared memory segments),
then the problem appears to be a ressource limit so hobbit isn't 
allowed to create a shared memory segment of size 256 KB. You'll have
to check your OS documentation on where to configure these limits.
Look for "IPC tuning" or "SYSV IPC parameters".


Regards,
Henrik
list Matthew Daubenspeck · Tue, 18 Oct 2005 10:52:40 -0400 ·
quoted from Henrik Størner
On Tue, Oct 18, 2005 at 03:17:28PM +0200, Henrik Stoerner wrote:
It complains that it cannot setup the shared memory (shm) segments
needed for communicating with the hobbitd_* modules.

First, login as the hobbit user and run "ipcs -m" to see if any 
shared-memory segments exist for this user. When hobbitd is 
stopped there should not be any. If you see something like this:

hobbit at osiris:~$ ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x020289c7 32769      hobbit    600        262144     2
0x030289c7 65538      hobbit    600        262144     2
0x040289c7 98307      hobbit    600        262144     2
0x050289c7 131076     hobbit    600        262144     1
0x060289c7 163845     hobbit    600        32768      1
0x070289c7 196614     hobbit    600        524288     2

and there is no hobbitd running, then the normal cleanup 
didn't happen when hobbitd last stopped. You can use "ipcrm -m <shmid>"
to remove them manually.
That did the trick. Thank you very much. Now I just need to figure out
how to get rid of the purple hobbitd_client alert :)
quoted from Matthew Daubenspeck

-- 
  Matthew Daubenspeck
  http://www.oddprocess.org

Gentoo Linux 2.6.12-gentoo-r6 x86_64 AMD Athlon(tm) 64 Processor 2800+

10:51:54 up 86 days, 21:19, 1 user, load average: 0.47, 0.56, 0.48
list Henrik Størner · Tue, 18 Oct 2005 17:14:07 +0200 ·
quoted from Matthew Daubenspeck
On Tue, Oct 18, 2005 at 10:52:40AM -0400, Matthew Daubenspeck wrote:
didn't happen when hobbitd last stopped. You can use "ipcrm -m <shmid>"
to remove them manually.
That did the trick. Thank you very much. Now I just need to figure out
how to get rid of the purple hobbitd_client alert :)
bb 127.0.0.1 "drop your.hobbit.servername hobbitd_client"


Regards,
Henrik