Hi all,
I was wondering how I can debug lighttpd when it stops working. I
have had lighty working great for over a month, but recently I must
have change something causing lighty to fail during start up. Here
is the stack trace:
2005-07-04 21:44:22: (config.c.625) line: 1 pos: 30 invalid value
field
2005-07-04 21:44:22: (config.c.707) configfile parser failed
From what I can tell, config/lighttpd.conf gets translated into /tmp/
appname_lighttpd.conf. When I look at this file, line 1 says:
server.port = 80
Which looks fine (I start lighty as root, so there should be no
permission issues).
Any help debugging this would be greatly appreciated.
Thanks!
* David Teare [2005-07-04 21:52]:> 2005-07-04 21:44:22: (config.c.625) line: 1 pos: 30 invalid value > field > 2005-07-04 21:44:22: (config.c.707) configfile parser failed > > From what I can tell, config/lighttpd.conf gets translated into /tmp/ > appname_lighttpd.conf. When I look at this file, line 1 says: > > server.port = 80 >Hmm, maybe funky control character in there? Did you edit and upload the file or edit in a shell using a text editor? Also try the helpful folk (esp Jan, the author) on the lighttpd list: http://lighttpd.net/documentation/ -- ________________________________ toddgrimason*todd[ at ]slack.net