"Ralf S. Engelschall" wrote:
> On Thu, Dec 09, 1999, Scott R. Every wrote:
>
> > we are trying to switch one of our new servers to mod_ssl from stronghold
> > on solaris 2.6. using a similar setup to what works on our linux machine,
> > get the following error at runtime:
> > /usr/local/apache/bin/apachectl startssl
> > Ouch! ap_mm_create(1048576, "/usr/local/apache/logs/httpd.mm.6553") failed
> > Error: MM: mm:core: failed to acquire shared memory segment (Invalid
> > argument):
> > OS: No such file or directory
> > /usr/local/apache/bin/apachectl startssl: httpd could not be started
> >
> > everything appears to compile fine, but i'm at a loss as to what to try
> > next.
>
> The value 1048576 is 1024*1024 = 1MB. AFAIK Solaris doesn't allow such large
> shared memory segments when using IPC shm.
solairs kernel is quite tunable, and most of it`s default values are quite low
unless you rise'em:
> Name Default Max Brief Description
> ----- ------- -------------- -------------------------------------
>
> msgmap 100 2147483647 Number of entries in the message map
> msgmax 2048 2147483647* Maximum message size
> msgmnb 4096 2147483647* Maximum bytes on queue
> msgmni 50 2147483647 Number of message queue identifiers
> msgssz 8 2147483647* Segment size of a message
> msgtql 40 2147483647 Number of system message headers
> msgseg 1024 32767* Number of message segments (MUST BE < 32768)
>
> Use "SSLSessioCache
> shm:/path(1000000)", i.e. a little bit less than 1MB, because Solaris's value
> is a little bit less than 1MB.
you might try to find out or set acutall sizes:
> Setting Message Queue Parameters
> --------------------------------
>
> Message queue parameters are changed by editing the
>/etc/system file and
> adding lines of the form:
>
> set msgsys:msginfo_variable = value
>
> where 'variable' is one of the entries from the name
>column, above. For
> example, the entry:
>
> set msgsys:msginfo_msgmap = 150
>
> would increase the size of the message queue resource
>map to 150.
>
> After modifying the /etc/system file, the system must
>be rebooted in order to
> implement the new values.
>
>
> Checking Message Queue Parameters
> ---------------------------------
>
> InterProcess Communication (IPC) parameters can be
>checked via the sysdef
> command:
>
> $ sysdef -i
>
> Toward the bottom of the output, there will a section
>which should look
> something like the following:
>
> *
> * IPC Messages
> *
> 100 entries in msg map (MSGMAP)
> 2048 max message size (MSGMAX)
> 4096 max bytes on queue (MSGMNB)
> 50 message queue identifiers (MSGMNI)
> 8 message segment size (MSGSSZ)
> 40 system message headers (MSGTQL)
> 1024 message segments (MSGSEG)
>
>
> The values at the left will reflect either the default
>value, or the value
> specified in the /etc/system file, if that parameter
>has been modified.
>
> If the values displayed are all zero, load the message
>queue module:
>
> # modload -p sys/msgsys
>
> and run sysdef -i again.
>
> If you really need such a large size, compile
> MM differently, i.e. let MM use mmap(2) instead shmget(2). See MM's configure
> --help output for hints.
or do this....
gerhard
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
