-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | Lighttpd: Incompatible with libssl1.1.1 (Buster version) #2808
Comments
@maartenlangeveld I recognised this with the sury.org repo (used on non-ARMv6) hence blocked the SSL packages there. Good to know this is true with Buster repo as well, so its about the libssl1.1 version (1.1.1), not about the specific package. However since I tested with Lighttpd, this update seems to be not done automatically, right? Do you remember when this got installed? So we need to block this for Buster branch on Stretch as well. I hope there are no follow-up dependency by this. Will post some instructions to downgrade and block the SSL package this evening. Of course you can install the Lighttpd version from Buster as well, but generally I would avoid mixing the branches more than required. Ah or was Lighttpd instead installed from Buster? Please paste:
And if you can the exact "dependency unmet" error output when attempting to reinstall. |
If I remember well (not 100% sure...) Lighttpd got installed when I installed O!MPD. How can I get lighttpd working again, I really need it. Have you a workaround or solution ? Thanks! Another issue: phpmyadmin (4:4.6.6-4) has been removed with the upgrade to v6.24 When reinstalling ( dietpi-software reinstall 90 ) it seems it installs php7.0 back again...
Would have loved to post terminal output but my terminal sessions suddenly died... Is that ok / preferable ? @MichaIng
|
Thanks, Micha ! Get a message that there's an upgrade for mpd but it is not installed:
|
The old conf is preserved (on my zero w, that is). Copy /etc/lighttpd/lighttpd.conf to /etc/lighttpd/lighttpd.conf.old. After that cp lighttpd.conf-dpkg* lighttpd.conf and start the service. (If there is no need for special config.) |
@PeterLacknase |
Hi Micha, is there a workaround ? Or do I have to wait for v6.25 ? Thanks, Maarten |
@maartenlangeveld @PeterLacknase LighttpdReverting the old config file will not work, since the php-fpm socket has been changed to the Okay now I am confused. Both Lighttpd and libssl1.1 has been upgraded to the Buster version, so they should be compatible with each other. Not sure how this can happen with priority 100 but it must be due to some dependency tail. This is why I was not happy to use the Buster repo. Found the dependency tail for the Buster libssl1.1 version: Attempting to forcefully downgrade Lighttpd:
Okay given that Lighttpd needs to be taken from Buster, now the question is why it fails. On my test VM system it works, but might be different on Raspbian. Please paste the following:
|
phpMyAdminWith phpMyAdmin this is indeed an issue, although easy to solve:
To prevent any further issues when PHP meta packages are updated, run:
Btw after collecting and fixing/working around the related APT issues with Raspbian Buster, I will release v6.24.1 as hotfix. We don't need to use a new subversion since there are no heavy patches done during the v6.24 patch loop. |
Sorry if I couldn‘t express it clear enough: On my Zero W rpis during the lighttpd update the old file was preserved. Thatswhy the startup stalled. Using the updated one, that came with the new package, everything worked. |
error.log remains empty
|
PR up to solve phpMyAdmin and hopefully Lighttpd issue as well: #2809 |
@maartenlangeveld
|
Ah, that might be possible. Okay makes sense:
Will check the configs for differences. |
|
Lighttpd default configsRaspbian Stretch
Raspbian Buster
|
Jep that's it! Is there some When you found the one, replace the existing lighttpd.conf with it and do:
|
I get confused... both config files (stretch and buster) have
So what makes the difference ? which config should I take then? Thanks Maarten |
@maartenlangeveld Actually since everything else matches or is optional or replaceable, the only required switch is:
You can also verify that the one file exists, while the other not. Seems it was renamed: |
My apologies, you are completely right. They are different .assign. <--> .conf. I did not notice. |
Have followed your instruction. System extremely slow. Htop shows that system continuously tries to start lighttpd, spawning new processes. Rebooting now. Takes a very very long time that I can start SSH session after reboot. Good news lighttpd service is started but makes system extremely slow... Watching htop, lighttdp starts itself over and over everytime with new PID... Almost there... |
@maartenlangeveld
|
I stopped lighttpd, still >95% cpu. Don't know what's going (wr)on(g). Seems things getting even worse. Cannot restart lighttpd (failed). Have removed the symlink to the non-existing '50-phpmyadmin.conf'. Uninstalled phpmyadmin. But booting still extremely slow.... Takes about 10 mins before system responds to SSH... It's still a long way. Will reinstall phpmyadmin eventually (needed but not high priority), see if it installs the apparently needed '50-phpmyadmin.conf'. But first have to find out what makes my system so terribly slow at the moment. Let you know. Thanks, Maarten
|
@maartenlangeveld Possibly there were still the two php-fpm versions running concurrently. So the above, which includes purging php7.0 packages, perhaps solves the hanging. Then since you just switched back to default Lighttpd Buster config, phpMyAdmin most likely wants to reapply its configuration changes. You should be able to do that via:
If phpmyadmin is currently not installed, you of course need to do that, which includes the config adjustment: |
I did apply the phpMyAdmin fixes. Had also purged the php7.0 packages. Have de-installed phpMyAdmin. Now services stopped (dietpi-services stop), stil very high CPU >95%, it seems '/lib/systemd/systemd-journald' consumes lot of cpu power. update update 2 update 3 Will let you know the results. root@DietPi:~# journalctl -xe
|
Hi Micha, have installed everything again
but moreover the high CPU (95-100%) load remains with same error for dietpi-wifi-monitor:
This is a real issue. Will go back to v6.22 again again again... I'm sorry since I know how committed you are. But with 100% CPU I have no other option. |
@maartenlangeveld
|
@MichaIng Finally, I am there. Everything is working fine now. Many thanks for your support! |
@maartenlangeveld I solved btw the priorities a bid different to assure that only the absolutely required packages are pulled from Buster: #2809 This allows install e.g. build-essentials from Stretch, since some core libraries were not pulled from Buster. But in your case (where the mentioned libraries were already upgraded), this requires downgrading of some of them. When required, I will assist in how to do that. |
You are more than welcome. I have to thank you and Daniel for putting so much effort so that I enjoy my SBCs. I do not need build essentials, I installed it by accident, so no assistance relating to thus issue is needed. |
The right path came with the updated conf file (on my machines, that is). Thanks for all Your patience! |
Okay, v6.24.1 just released with Lighttpd and further PHP on ARMv6 fixes. |
Hi Micha/Daniel,
Have now upgraded my (restored) RPi Zero W (armv6) from v6.22 to v6.24. All went well (thanks!) except that Lighttpd seems broken. Service won't start, and it fails to re-install (dependency unmet libssl1.1).
Is there a solution?
Thanks
The text was updated successfully, but these errors were encountered: