Project

General

Profile

force-reload / stop is not actually stopping lighttpd, bug or prob with config?

Added by issyd over 15 years ago

Hi,

I am currently configuring a lighttpd server.

Operating System: Ubuntu - 9.04 with the current debian package for lighty,

I am using firefox to access the webpages.

Since i am currently configuring my setup there are changes being made and in the process i am constantly 'reloading' the config. However lighttpd does not seem to be stopping the service correctly, or even using the new settings. The only way to get it to use any updated or edited settings is to manually kill the processes.

For example:

issy@linx:/var/www$ sudo /etc/init.d/lighttpd status 
 * lighttpd is not running
issy@li68-223:/var/www$ sudo /etc/init.d/lighttpd start 
Syntax OK
 * Starting web server lighttpd
2009-08-12 01:32:04: (network.c.300) can't bind to port: 74.207.226.223 80 Address already in use 
   ...fail!
issy@linx:/var/www$ 
issy@linx:/var/www$ lsof -i :80
issy@linx:/var/www$ 

Please note, i do not have any other webserver installed nor is anything other then lighty binding to port 80. Looking at the process list lighttpd it looks like it's not actually stopping when i run the 'stop' command or 'force-reload' or 'reload'.

After stopping the service, i am still able to access the url, without errors indicating the service is still running. However when checking the status it reports as stopped.

My config file(Top portion), after the bit below i just have MIME types and index file configurations.

server.document-root = "/var/www" 

server.port = 80
server.groupname = "www-data" 
server.bind                = "74.123.123.123" 
server.tag ="lighttpd" 

server.errorlog            = "/var/log/lighttpd/error.log" 
accesslog.filename         = "/var/log/lighttpd/access.log" 

server.modules              = (
            "mod_access",
            "mod_accesslog",
            "mod_fastcgi" 
)


Replies (1)

RE: force-reload / stop is not actually stopping lighttpd, bug or prob with config? - Added by nitrox over 15 years ago

Thats a problem with your / your distro´s init-script. As we don´t ship any init-scripts please report this as bug on ubuntu´s bugtracker.

Though this might e.g. be caused by pid-location differences from init-script and lighty.

    (1-1/1)