On Mon, Mar 15, 1999, [EMAIL PROTECTED] wrote:
> Full_Name: Frank Richter
> Version: 2.2.4
> OS: Linux 2.0.36
> Submission from: stipe.hrz.tu-chemnitz.de (134.109.132.39)
>
> I've build Apache 1.3.4 with mod_ssl/2.2.4 (Linux 2.0.36, RedHat 5.2).
> Starting the httpd isn't working, it brings this in the error_log:
>
> [error] mod_ssl: Child could not open SSLMutex lockfile /var/run/ssl_mutex.12155
> (System error follows)
> [error] System: Permission denied (errno: 13)
>
> I've in httpd.conf:
> SSLMutex file:/var/run/ssl_mutex
>
> ls -l /var/run/ssl_mutex.12155
> -rw------- 1 root root 0 Mar 15 15:45 /var/run/ssl_mutex.12155
>
> Applying a chmod 666 /var/run/ssl_mutex.12155
> helps...
That's interesting. In my ssl_engine_mutex.c source I've programmed:
| /* create the lockfile */
| unlink(mc->szMutexFile);
| if ((mc->nMutexFD = ap_popenf(p, mc->szMutexFile,
| O_WRONLY|O_CREAT, SSL_MUTEX_LOCK_MODE)) < 0) {
| ssl_log(s, SSL_LOG_ERROR|SSL_ADD_ERRNO,
| "Parent process could not create SSLMutex lockfile %s",
| mc->szMutexFile);
| ssl_die();
| }
| /* make sure the childs have access to this file */
| if (geteuid() == 0 /* is superuser */)
| chown(mc->szMutexFile, ap_user_id, -1 /* no gid change */);
So, when you run it as root the mutex file should be correctly owned by the
child user id. Check your ``User'' directive. When it's set to for instance
``User nobody'' then ap_user_id above should chown the mutex to nobody and
this way the childs should be able to use it.
Can you trace down the problem with a debugger for me? The questions are 1.
what is the value of geteuid() in your case (check whether the if-clause is
entered) and what value ap_user_id has.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
