unable to start lightttpd code 255
Added by lightrr about 4 years ago
i upgraded raspbian stretch to buster
running into error below appretiate help
[....] Starting lighttpd (via systemctl): lighttpd.serviceJob for lighttpd.service failed because the control process exited with error code.
See "systemctl status lighttpd.service" and "journalctl -xe" for details.
failed!
pi@vorman:~ $ systemctl status lighttpd.service
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-03-30 00:18:43 EDT; 3s ago
Process: 4410 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
Mar 30 00:18:43 vorman systemd1: Failed to start Lighttpd Daemon.
Mar 30 00:18:43 vorman systemd1: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 30 00:18:43 vorman systemd1: lighttpd.service: Scheduled restart job, restart counter is at 5.
Mar 30 00:18:43 vorman systemd1: Stopped Lighttpd Daemon.
Mar 30 00:18:43 vorman systemd1: lighttpd.service: Start request repeated too quickly.
Mar 30 00:18:43 vorman systemd1: lighttpd.service: Failed with result 'exit-code'.
Mar 30 00:18:43 vorman systemd1: Failed to start Lighttpd Daemon.
Replies (7)
RE: unable to start lightttpd code 255 - Added by gstrauss about 4 years ago
Run the ExecStartPre command on the command line as root and look at the error message:/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf
Or look at the logging in:journalctl -u lighttpd.service
RE: unable to start lightttpd code 255 - Added by lightrr about 4 years ago
here is error
pi@vorman:~ $ /usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf
/bin/bash: /usr/share/lighttpd/create-mime.assign.pl: No such file or directory
2020-03-30 07:34:12: (configfile.c.1461) command "/usr/share/lighttpd/create-mime.assign.pl" exited non-zero: 127
2020-03-30 07:34:12: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 30 pos: 14 parser failed somehow near here: (EOL
RE: unable to start lightttpd code 255 - Added by gstrauss about 4 years ago
/bin/bash: /usr/share/lighttpd/create-mime.assign.pl: No such file or directory
RE: unable to start lightttpd code 255 - Added by lightrr about 4 years ago
i solved the create-mime file missing
now have following issue
pi@vorman:/var/www/html/owncloud $ /usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf
2020-03-30 18:14:14: (configfile.c.1599) server.upload-dirs doesn't exist: /var/cache/lighttpd/uploads
2020-03-30 18:14:14: (mod_openssl.c.445) SSL: BIO_read_filename('/etc/letsencrypt/live/vorman.mooo.com/combined.pem') failed
2020-03-30 18:14:14: (server.c.1183) Initialization of plugins failed. Going down
RE: unable to start lightttpd code 255 - Added by lightrr about 4 years ago
i have 7.3 installed why is lighty looking for 7.0
2020-04-01 13:22:23: (gw_backend.c.240) establishing connection failed: No such file or directory socket: unix:/var/run/php/php7.0-fpm.sock
2020-04-01 13:22:23: (gw_backend.c.956) all handlers for /status.php? on .php are down.
2020-04-01 13:22:25: (gw_backend.c.319) gw-server re-enabled: unix:/var/run/php/php7.0-fpm.sock 0 /var/run/php/php7.0-fpm.soc
RE: unable to start lightttpd code 255 - Added by gstrauss about 4 years ago
PHP FPM may be incompatible between versions.
PHP FPM only recently added feature to allow non-versioned paths.
Most distro ship webservers with config files that hard-code a specific PHP FPM version. All of this has nothing to do with the canonical lighttpd source code on this site -- it's your distro vendor config files that your distro provides for lighttpd. If you want lighttpd to use a different PHP FPM version, e.g. 7.3, then you'll have to update the config files for lighttpd provided by your distro that have hard-coded PHP FPM 7.0.