Httpd dead but subsys locked

I recently encountered an issue with one of the production server running RHEL 4. All the httpd processes were alive and their was no issues with the web server, however when we ran the:

service httpd status

command, it says, "httpd dead but subsys locked."

Their were no files inside the /var/lock/subsys directory for httpd and also I deleted the /var/run/httpd.pid file. However, the issue still persists. Even, I rebooted the server in the hope that this will clear any lock files.

However, nothing happened.

A careful examination of httpd.conf file at /etc/httpd/conf/httpd.conf file referred the pid file directory to /var/www/run, however the corresponding entry in the /etc/init.d/httpd file referred to /var/run directory for pid file.

Changing the lockfile directory and the pid file directory to /var/www/lock/subsys and /var/www/run directory solved the issue.

Now, service httpd status/start/restart/stop does not complain about the subsys issue.

Comments

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Clariion storage processor IP address change

We recently spinned off to a new company from the parent one. As a result a major infrastructure change had to be performed on all our equipments. We had a few Clariions for which the storage processors IP address had to change, as were assigned a new block of IP address. Their are a few things that had to be taken care before undergoing an IP address change of he storage processor IP address. 1. If the Clariion is master node of the global domain, then someone else had to be promoted to be domain master before changing the IP address. That is it has to be demoted as a master domain node. 2. Then the clarrion has to be removed from the domain. That is the domain security has to be reset 3. The storage processor has to be rebooted Briefly, the steps are as follows: 1. Promote some other Clariion to be the master node of the domain. (This can be achieved through the Navisphere web based console). 2. Remove the Clariion from the domain. (This can be done through the Navisphere web conso...
Read more

Move LVM from multiple local and iscsi disk to SAN

We are setting up our DR site. For replication we are using EMC Recoverpoint appliance. The license what we have works for only SAN volumes on EMC arrays namely VNX in our case. The database and file shares which are on SAN have no problem however, the critical file shares that are on local storage or Dell iscsi storage have an issue. It sounds easy to move them to SAN and start replication but not so. Consider below: 1. The LVM housing the file shares on a Dell server contains PV from local disk partition (yes not complete disk but like /dev/sda10 on extended partition) and other full disk from iscsi storage /dev/sdq and /dev/sdi 2. Total size is ~400 GB with 100 GB from local disk partition (total local disk size is 300 GB) and 300 (200 + 100) from iscsi. I know its wrong but it was done long time ago and we were running out of space. 3. The dell server does not have FC connection. 4. The file system structure contains 32000 nested directory structure with approx 1.2 billion fi...
Read more