Lighttpd is not starting after update

Troubleshooting
1

Good day!

Last week I have updated my RasPi B+ to bullseye from buster. Everything went ok apparently.

This week I upgraded several packages, and today my webserver stop working. I went to dietpi-services and MariaDB and other services were missing, so I reinstalled MariaDb.

 sudo apt --reinstall install mariadb-server-10.3

Then all services missing reappeared but lighttpd failed.

I reinstalled Lighttpd with:

sudo dietpi-software reinstall 84

After a reboot lighttpd still failing.

I don’t know what information I should send here but I would thank any guide to help me resolve this issue

Thanks!

2

Hi

Bullseye is still a BETA version of Debian and not finally released. There could be some issues still. Let’s check how your system is doing. Can you post following

journalctl -u lighttpd.servic
cat /var/log/lighttpd/error.log
/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf
3

Hello again and thank you for your reply!

This was the result:

2021-02-25 20:43:13: configfile.c.316) Warning: please add "mod_authn_file" t
o server.modules list in lighttpd.conf.  A future release of lighttpd 1.4.x w
ill not automatically load mod_authn_file and lighttpd will fail to start up
since your lighttpd.conf uses auth.backend = "htpasswd".
2021-02-25 20:43:13: configfile.c.461) Warning: "mod_compress" is DEPRECATED
and has been replaced with "mod_deflate".  A future release of lighttpd 1.4.x
 will not contain mod_compress and lighttpd may fail to start up
2021-02-25 20:43:13: plugin.c.195) dlopen() failed for: /usr/lib/lighttpd/mod
_openssl.so /usr/lib/lighttpd/mod_openssl.so: cannot open shared object file:
 No such file or directory
2021-02-25 20:43:13: server.c.1233) loading plugins finally failed

I am not sure what does it means, but I could not find the file mod_openssl.so in /usr/lib/lighttpd/

4

I guess you are trying to activate SSL, correct?

Usually this mod is part on the normal lighttpd apt package on Dedian Buster. Seems is not the case on Bullseye and that’s what the system is complaining about :wink:

/usr/lib/lighttpd/mod_openssl.so: cannot open shared object file: No such file or directory

I’m not sure if this is an issue on the Bullseye package or simply not yet developed by package owner. Keep in mind, Bullseye is not officially released yet and in a BETA status. Same applies for Bullseye software packages.

However there is own lighttpd-mod-openssl package available and can be installed as follow

apt install lighttpd-mod-openssl
systemctl restart lighttpd.service

[hr]
MichaIng
There is a message on Bullseye about TLS settings being deprecated

Feb 26 08:41:11 DietPiVM1 lighttpd[2747]: 2021-02-26 08:41:10: mod_openssl.c.2447) SSL: ssl.use-sslv2 is deprecated and will soon be removed.  It is disabled by default.  Many modern TLS libraries no longer support SSLv2.
Feb 26 08:41:11 DietPiVM1 lighttpd[2747]: 2021-02-26 08:41:10: mod_openssl.c.2454) SSL: ssl.use-sslv3 is deprecated and will soon be removed.  It is disabled by default.  Many modern TLS libraries no longer support SSLv3.

Probably we would need to remove following 2 lines on dietpi-letsencrypt sooner or later

	ssl.use-sslv2 = "disable"
	ssl.use-sslv3 = "disable"
5

Hello again @Joullinar and thanks for your answer!

I installed lighttpd-mod-openssl but the error remained… then I follow your instructions in your first message:

journalctl -u lighttpd.service
cat /var/log/lighttpd/error.log
/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf

and I found another package was missing: lighttpd-mod-deflate … So I Installed that package and then restarted lighty service…

Finally everything works as usual! I have my weberver running now with no errors apparently…

Thanks for your help!

6

Yes,

actually using /usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf is quite a good way to troubleshoot/ verify configuration without starting the lighttpd service. Basically same is done by the service itself.

7

Thanks! I have learned a lot… :smiley:

Now I feel someone less newbie instead a totally newbie :rofl:

8

keep in mind you are not on a beta path using Bullseye now. Might some more thinks not working as expected.