>Number: 1727 >Category: os-irix >Synopsis: I get 'accept_mutex_on: Permission denied' in the error_log >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Jan 23 15:30:00 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3b3 >Environment: IRIX 5.3 11091812 IP22 mips Challenger S server, apache 1.3b3 compiled with the IRIX cc. The server runs in a chrooted environment. >Description: I tried to upgrade one of our web-servers from 1.2.5 to 1.3b3. The server runs in a chrooted environment. But when I started the 1.3b3 server it gave me these messages in the error_log:
accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied [Fri Jan 23 22:40:00 1998] [notice] Apache/1.3b3 configured -- resuming normal o perations accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_onaccept_mutex_onaccept_mutex_onaccept_mutex_on: : : : Permission d eniedPermission deniedPermission deniedPermission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied accept_mutex_on: Permission denied And so on forever... I suspected this had something to do with the various ways to do accept serialization code, so I recompiled with -DUSE_FCNTL_SERIALIZED_ACCEPT (which is used with the 1.2.5 version), and the new version has worked fine (so far). But isn't this a suboptimal solution? My server don't have multiple processors, so USE_USLOCK_SERIALIZED_ACCEPT is probably not a good idea. But will USE_SYSVSEM_SERIALIZED_ACCEPT be faster than USE_FCNTL_SERIALIZED_ACCEPT? I suspect that my problem with USE_SYSVSEM_SERIALIZED_ACCEPT is due to the absence of some important system files in my chrootet environment, but so far I have not found any helpful hints in any of the logs, or in any of the man-pages I've been through (semop, semctl, semget, intro). Could you possibly give me some hints on where to look? If you need to know more about my chroot-setup I'll be happy to provide all the details. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
