New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
@Infinity580 - We need more details. Please advise?
I never have used Lighttpd but 1 thing I instantly noticed is the errors on startup. You might wanna fix those first.
I have a problem: no description
I have a problem: no logs?
Uninstall and reinstall to try and correct the permissions and missing files
@wcypierre here you go that should be helpfull:
2014-03-15 23:22:28: (log.c.166) server started
2014-03-15 23:23:18: (server.c.1442) [note] graceful shutdown started
2014-03-15 23:23:18: (log.c.166) server started
2014-03-15 23:23:18: (server.c.1558) server stopped by UID = 0 PID = 8640
2014-03-15 23:40:13: (server.c.1558) server stopped by UID = 0 PID = 15969
2014-03-15 23:40:13: (log.c.166) server started
2014-03-16 12:25:00: (server.c.1442) [note] graceful shutdown started
2014-03-16 12:25:00: (server.c.1558) server stopped by UID = 0 PID = 32
@Mark_R The errors are not the issue, i fix them later it worked before.
I just have the error thats it, i just restart lighttpd and it cant start up again.
@rajprakash already did that, dosent help....
Does it start again if you change the listening web port? the last error looks like the cause.
@Mark_R yes it works on port 81 but not 80:)
I suspect that another application is using port 80 and prevents Lighttpd from broadcasting on that same port, you can check this by entering this command
Perhaps apache is installed by default on your system, try this command:
or
Try to run this :
Also, do you have another aplication running on port 80? Such Apache/Nginx/SSH?
Nothing is running on port 80.
Considering it is OpenVZ, something in kernel iptables module might not be right?
in that case I wouldn't know what's wrong, it must be the configuration.
Maybe this thread helps you out http://nginxcp.com/forums/thread-541.html they are talking about it being related to vhosts.
It would be good to see the configuration files /etc/lighttpd
Make sure that:
if you're doing name based virtual hosts with lighttpd then you should use:
$HTTP["host"] =~ "(^|.)nixcraft.com$" {
...
}
*Oh and run: netstat -antp as a root; share the output with us
Another trick you can use to debug this issue is, move one of the other services, let's say proftpd to port 80 and see if you can start it.
Also are you tailing the most recent logs in /var/log when this error occurs. Check /var/log/syslog /var/log/messages and all logs under /var/log/lighthttpd/
so after one unsuccessful start attempt run (as root) ls -latr /var/log and check for the files that come at the bottom of the list
then run: tail -f /var/log/lighttpd/* /var/log/syslog {{and also other files that changed since you tried to start the server}} in one console window while you attempt to start lighttpd in the other; see what turns up