Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Knowledge Partner
Knowledge Partner
2045 views

novell-httpstkd is dead but pid exists?

I was in NRM and saw that the health monitor was yellow. It said it was "high processes"

I made the mistake of clicking on it, it showed me some processes and then NRM went dead.

I did a:

rcnovell-httpstkd status
and get:
novell-httpstkd (3524) is dead, but /var/run/httpstkd.pid exists
Labels (2)
0 Likes
2 Replies
Knowledge Partner
Knowledge Partner

Re: novell-httpstkd is dead but pid exists?

So it was explained to me that I should use ps to find if the process is "really" dead or not. It was still "there", so I had to kill -9 it

I was also informed that sometimes if the process is NOT there, you still have to delete the .pid file.

I was able to then start httpstkd
0 Likes
Knowledge Partner
Knowledge Partner

Re: novell-httpstkd is dead but pid exists?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, a PID file will persist if you kill a process abruptly. The stop
scripts typically deal with the cleanup of the file. Often, though, a
startup script will check for a bad PID file and create it; other times
the script will tell you the file exists and have you clean it yourself.

Good luck.





kjhurni wrote:
> So it was explained to me that I should use ps to find if the process is
> "really" dead or not. It was still "there", so I had to kill -9 it
>
> I was also informed that sometimes if the process is NOT there, you
> still have to delete the .pid file.
>
> I was able to then start httpstkd
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLMmYFAAoJEF+XTK08PnB5Jd8P/jugY5L9OJC6NxPHScjMh52m
uy04MF+SVd117Ul9ul4mGTjWGBWriXiz/PgfITXSjVzEhsTAJp54eJyMlWkaPhX5
/zUR6q/nrqcuLZ+U6t04bJLB3xAxxNLoOfvUWCPHFkUBaOuBbWQXKGsGjhAKstZt
4vBn6ZBGvDIBSm2X4SQWicZSakhs/DaeqA/wHcot8mSWas9Bgda8YXvAKFAGsVzW
+dhx2lqByDhTwDVMsdwjt7vDshRfYRPkzLYw19568Ii4NeM4I+QNRtO2iWb6Cx1T
Xgz+k3GkF94a/JhpEEaiAXkmT8SZ8/GV0AMikGAWIl2LHG6oGcxbatO3VZlr4iGn
M3yzZK34wZXelQstXVwREYTHqTvFBE/5t3CIdFfLo3I5ODxtdcYYWPBfOnjeMOsL
6ghgrz0mvurJeZ/4WMxk0UNJBduMzNdg5JyiHw9Q3CbPQZorQkz2AaQuVYyU7P+F
IRi7QtidHhVYxR2NQFvUPd7mJNSeB0zkN6jYlYidgLsNWzwtH+sGih83BMdtnuCY
diNCawPMQAaBdyrtNaUY7plSTOrbz52+U1Hr7N7izHPCWM+kMCHs79U7oitjZUpx
OkRfRFg9oMlAxHPHIHKWUin8GKF8QaJ0JCqre5N4F+djM4uiTvfj5bIma75KMBug
RZh3oL3AAb+VAwHheFtg
=74BN
-----END PGP SIGNATURE-----
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.