permission denied?
list Daniel J McDonald
It ran fine with beta 6. Upgrading to RC1 gives the following in hobbitlaunch.log 2005-02-03 15:54:36 Setting up network listener on 0.0.0.0:1984 2005-02-03 15:54:36 Setting up signal handlers 2005-02-03 15:54:36 Setting up hobbitd channels 2005-02-03 15:54:36 Could not get shm of size 102400: Permission denied 2005-02-03 15:54:36 Cannot setup status channel 2005-02-03 15:54:36 Task hobbitd terminated, status 1 Where should I look? -- Daniel J McDonald, CCIE # 2495, CNX Austin Energy user-290ce4e24e19@xymon.invalid
list Henrik Størner
▸
In <user-178641afd78e@xymon.invalid> Daniel J McDonald <user-290ce4e24e19@xymon.invalid> writes:
It ran fine with beta 6. Upgrading to RC1 gives the following in hobbitlaunch.log
2005-02-03 15:54:36 Setting up network listener on 0.0.0.0:1984 2005-02-03 15:54:36 Setting up signal handlers 2005-02-03 15:54:36 Setting up hobbitd channels 2005-02-03 15:54:36 Could not get shm of size 102400: Permission denied 2005-02-03 15:54:36 Cannot setup status channel 2005-02-03 15:54:36 Task hobbitd terminated, status 1
Where should I look?
First check that no hobbitd and hobbitd_channel processes are running. You can also run the "ipcs" command and see if there are any shared- memory segments owned by the hobbit user - there should not be any when Hobbit is not running. If that doesn't give anything, add "--debug" to the hobbitd commandline in ~/server/etc/hobbitlaunch.cfg, and let's see what that tells us. Henrik
list Daniel J McDonald
▸
On Thu, 2005-02-03 at 22:12 +0000, Henrik Storner wrote:
In <user-178641afd78e@xymon.invalid> Daniel J McDonald <user-290ce4e24e19@xymon.invalid> writes:
First check that no hobbitd and hobbitd_channel processes are running. You can also run the "ipcs" command and see if there are any shared- memory segments owned by the hobbit user - there should not be any when Hobbit is not running.
there were some shared memory segments owned by the UID hobbit had when I was running beta-4. I changed the UID and GID when I upgraded to beta-5 (and fixed my ldap pam module). I'm rebooting now to see if that clears it all up.... Yes.
▸
If that doesn't give anything, add "--debug" to the hobbitd commandline in ~/server/etc/hobbitlaunch.cfg, and let's see what that tells us.
2005-02-03 16:22:36 calling ftok('/var/hobbit/server',1)
2005-02-03 16:22:36 ftok() returns: 0x1070A37
and that is referenced by
[root at ldap2 hobbit]# ipcs
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00070a37 0 1008 600 102400 0
0x01070a37 32769 1008 600 102400 0
0x02070a37 65538 1008 600 102400 0
0x03070a37 98307 1008 600 102400 0
0x04070a37 131076 1008 600 102400 0
0x05070a37 163845 1008 600 102400 0
------ Semaphore Arrays --------
key semid owner perms nsems
0x00070a37 0 1008 600 3
0x01070a37 32769 1008 600 3
0x02070a37 65538 1008 600 3
0x03070a37 98307 1008 600 3
0x04070a37 131076 1008 600 3
0x05070a37 163845 1008 600 3
So I'm guessing it just never cleaned up after I changed the username to
UID 506.Henrik
list Henrik Størner
▸
On Thu, Feb 03, 2005 at 04:33:14PM -0600, Daniel J McDonald wrote:
there were some shared memory segments owned by the UID hobbit had when I was running beta-4. I changed the UID and GID when I upgraded to beta-5 (and fixed my ldap pam module).
[snip]
So I'm guessing it just never cleaned up after I changed the username to UID 506.
That does make sense, because there was a bug in the cleanup code that wasn't fixed until beta-6.
I'm rebooting now to see if that clears it all up.... Yes.
"ipcrm" would suffice (I had to learn this tool when I started developing Hobbit), but a reboot certainly will wipe out any left-overs. Henrik