Not as likely but still possible. I think the default limit is 25% of physmem, so it depends. If you have leftover segments or a small amount of physical memory then this may be the cause:
The error message that you got in the log definitely points to this:
"2006-08-07 16:23:54 Could not get shm of size 1048576: Invalid argument"
"Invalid argument" means:
" EINVAL The size argument is less than the system- imposed minimum or greater than the system- imposed maximum. See NOTES.
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."
"Everett, Vernon" <Vernon.Everett at dpi.wa.gov.au> 07/08/2006 10:47 Please respond to hobbit at hswn.dk
To <hobbit at hswn.dk> cc
Subject RE: [hobbit] Message to long
On Solaris 10?
From: Colin Spargo [mailto:cspargo2 at csc.com] Sent: Monday, 7 August 2006 4:48 PM To: hobbit at hswn.dk Subject: RE: [hobbit] Message to long
MAXMSG_CLIENT seems to need to allocate a shared memory segment of equal size. If your kernel shared memory settings are set too low (eg. if you are running defaults on solaris) then you may not be able to allocate the segment. If that happens, things like you just described seem to happen...
you could possibly have dangling segments left over that were not cleaned up when you restarted hobbit, or possibly another app.
Try checking what is allocated with "ipcs -a", and increasing the parameter "shmmax".