0

I'm using Lighttpd web server. I was trying to experiment with a new simple module whose purpose is to write the http request details in a text file. But after creating that module and compiling it, every time I start the web server it becomes dead within a few minutes. Then when I check the status it says that the web server is dead but pid file exists. In terminal the following shows up.

[root@konsult2_vm ~]# service lighttpd status lighttpd dead but pid file exists

More over when I try to locate the lighttpd.pid file it locates it like this

[root@konsult2_vm ~]# locate lighttpd.pid

/var/run/lighttpd.pid

But then when I go to folder and look for it I can't find it. I'm totally confused. How can I stop lighttpd from getting dead, what could be the solution?

Thanks

the_naive
  • 2,936
  • 6
  • 39
  • 68
  • 2. Look in your configuration file and find out if/where it logs errors. See the errors that are logged. If required turn on debugging (this is all configured from your configuration file). Then post the errors here. – ArjunShankar Apr 05 '12 at 11:33
  • 3. `locate` does not give 'current' results. It has a database that it looks up. So sometimes, it can return a file that has since been removed, and sometimes it may not return a file that really exists. – ArjunShankar Apr 05 '12 at 11:36
  • How to "accept" the correct answers, I don't have any idea about it. Could you say me how to do so? – the_naive Apr 05 '12 at 11:37
  • Then what should I use instead of Locate? – the_naive Apr 05 '12 at 11:38
  • The location returned by `locate` seems to be right. Don't bother about the fact that the file vanishes. First check that lighthttpd is actually dead, and then check the error log. Read my comment numbered #2. – ArjunShankar Apr 05 '12 at 11:41

0 Answers0