Red Hat Bugzilla – Bug 467704
Httpd hangs when /tmp/rhnccrewrite.lock is removed by tmpwatch
Last modified: 2009-01-22 11:30:04 EST
+++ This bug was initially created as a clone of Bug #282651 +++
Description of problem:
After a week of uptime, httpd responses hang or become incredibly slow. The
httpd error log shows:
[Tue Jul 31 09:12:31 2007] [error] (2)No such file or directory: mod_rewrite:
Child could not open RewriteLock file /tmp/rhnccrewrite.lock
Evidently this file has been removed by tmpwatch.
Happens every week. Recreating the file with the right permissions allows httpd
to proceed normally.
Steps to Reproduce:
1. rm /tmp/rhnccrewrite.lock
Is this really where the lock file should be? Moving it to a dedicated location
under /var/lock seems preferable.
--- Additional comment from email@example.com on 2007-09-07 13:13:41 EDT ---
[root@rlx-1-12 ~]# grep -ir hnccrewrite.lock /etc/httpd/conf/*
[root@rlx-1-12 ~]# ls -l /tmp/rhnccrewrite.lock
-rw-r--r-- 1 apache root 0 Sep 6 15:27 /tmp/rhnccrewrite.lock
--- Additional comment from firstname.lastname@example.org on 2008-07-24 10:56:19 EDT ---
Adding to sat530-triage, since it has the sat-5.3.0 flag set.
--- Additional comment from email@example.com on 2008-10-20 08:25:40 EDT ---
Starting with Satellite 5.1.0, httpd package from RHEL 4 is used. That package is compiled with APR_USE_SYSVSEM_SERIALIZE and APR_USE_PTHREAD_SERIALIZE:
# rpm -q httpd
# httpd -V
Server version: Apache/2.0.52
Server built: May 9 2008 05:54:40
Server's Module Magic Number: 20020903:9
Server compiled with....
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
Therefore SysV locking is used, and no .lock files are created. The httpd package on RHEL 5 has similar compile time settings.
I'm therefore moving this bugzilla ON_QA, with the understanding that no file gets created so no file is deleted, so no slowdown should be observed.
I shall update the lockfile path in Spacewalk but the fix in Spacewalk is not blocking this bugzilla from being tested.
rhn_monitoring.conf changed in bfad4780e58cd79698909a62b68a7c354176cbd8.
I assume it is safe to move this ot MODIFIED.
The fix was included in spacewalk-config-0.3.2-1 and Spacewalk 0.3 contains spacewalk-config-0.3.3-1, so the fix is in. Moving ON_QA.
Can not verified in Spacewalk 0.3 due it require functional monitoring.
Postponing verification to Spacewalk 0.4
The lock is no longer created as per comment #0
The config option points to correct place.
Moving to VERIFIED.