I didn't make any changes to /etc/system this time, my system file has been that way since I first moved from BB to Hobbit. Any other ideas?

-----Original Message----- From: J Sloan [mailto:joe at tmsusa.com] Sent: Friday, June 30, 2006 2:00 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Problem with the latest release

Wes Neal wrote:

I had 4.1.1 running fine and wanted to move to the latest beta release. The compile seemed to go fine, but the hobbit log shows this now:

2006-06-29 22:16:33 Could not get shm of size 262144: Invalid argument 2006-06-29 22:16:33 Cannot setup status channel 2006-06-29 22:16:33 Task hobbitd terminated, status 1

I have plenty of shared memory I am almost sure and the other channel problem I should not have either. Here is my system file:

set shmsys:shminfo_shmmax=16000000 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=20 set semsys:seminfo_semmns=400 set semsys:seminfo_semmni=140 set semsys:seminfo_semmsl=60

This is Solaris 8 btw. Any ideas?

Did you reboot after editing /etc/system? Unlike Linux, Solaris must be rebooted for the changes to take effect -

J

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

On Thu, Jun 29, 2006 at 11:22:33PM -0400, Wes Neal wrote:

I had 4.1.1 running fine and wanted to move to the latest beta release. The compile seemed to go fine, but the hobbit log shows this now:

2006-06-29 22:16:33 Could not get shm of size 262144: Invalid argument 2006-06-29 22:16:33 Cannot setup status channel

My Solaris 8 man-page says:

 EINVAL
       The size argument  is  less  than  the  system-imposed
       minimum or greater than the system-imposed maximum.

Cannot be this, since your shm settings are for a size between 1 and 16000000 - the Hobbit request of 262144 bytes fits this.

 EINVAL
       A shared memory identifier exists for key but the size
       of  the  segment  associated with it is less than size
       and size is not equal to 0.

Sounds like this is the one. Your old Hobbit may still be running ?

Login as the Hobbit user and do an "ipcs -m". If there are any segments listed, either Hobbit is running or they weren't cleaned up properly upon shutdown. In that case, you can remove them with "ipcrm".

Henrik