During the recent update of lighttpd, it didn't restart automatically. It turns out that the main package (lighttpd) was updated before the packages containing the additional modules (in my case lighttpd-mod_auth), causing a mismatch in the library when lighttpd tried to restart: Sep 9 09:52:36 mail systemd[1]: Stopping Lightning Fast Webserver With Light System Requirements... Sep 9 09:52:36 mail lighttpd-angel[27604]: lighttpd-angel.c.139: child (pid=27608) exited normally with exitcode: 0 Sep 9 09:52:36 mail systemd[1]: Starting Lightning Fast Webserver With Light System Requirements... Sep 9 09:52:37 mail lighttpd[22303]: Syntax OK Sep 9 09:52:37 mail systemd[1]: Started Lightning Fast Webserver With Light System Requirements. Sep 9 09:52:37 mail perl: [RPM] lib64xml2_2-2.9.1-2.3.mga4.x86_64 installed Sep 9 09:52:37 mail lighttpd-angel[22306]: 2015-09-09 09:52:37: (plugin.c.223) dlopen() failed for: /usr/lib64/lighttpd/mod_auth.so /usr/lib64/lighttpd/mod_auth.so: undefined symbol: LI_ltostr Sep 9 09:52:37 mail lighttpd-angel[22306]: 2015-09-09 09:52:37: (server.c.679) loading plugins finally failed Sep 9 09:52:37 mail lighttpd-angel[22306]: lighttpd-angel.c.139: child (pid=22307) exited normally with exitcode: 255 Sep 9 09:52:37 mail perl: [RPM] lib64pcre16_0-8.37-1.mga4.x86_64 installed Sep 9 09:52:37 mail perl: [RPM] lib64pcre32_0-8.37-1.mga4.x86_64 installed Sep 9 09:52:37 mail perl: [RPM] lib64pcre-devel-8.37-1.mga4.x86_64 installed Sep 9 09:52:38 mail perl: [RPM] lib64xml2-devel-2.9.1-2.3.mga4.x86_64 installed Sep 9 09:52:38 mail perl: [RPM] bind-utils-9.9.7.P3-1.mga4.x86_64 installed Sep 9 09:52:38 mail perl: [RPM] lighttpd-mod_auth-1.4.37-1.mga4.x86_64 installed Sep 9 09:52:38 mail perl: [RPM] lighttpd-mod_magnet-1.4.37-1.mga4.x86_64 installed Sep 9 09:52:38 mail perl: [RPM] lib64pcre-devel-8.33-2.1.mga4.x86_64 removed Sep 9 09:52:38 mail perl: [RPM] lighttpd-mod_magnet-1.4.33-4.1.mga4.x86_64 removed Sep 9 09:52:38 mail perl: [RPM] bind-utils-9.9.7.P2-1.mga4.x86_64 removed Sep 9 09:52:38 mail perl: [RPM] lib64xml2-devel-2.9.1-2.2.mga4.x86_64 removed Sep 9 09:52:38 mail perl: [RPM] lighttpd-mod_auth-1.4.33-4.1.mga4.x86_64 removed Sep 9 09:52:38 mail perl: [RPM] lighttpd-1.4.33-4.1.mga4.x86_64 removed I suppose that is also applies to mga5, but on another server that's running lighttpd on mga5 I didn't have this problem because there I'm not using additional modules. I think that lighttpd and its extra modules should be upgraded in the same transaction (or maybe the extra modules updated before lighttpd). Reproducible: Steps to Reproduce:
(In reply to Luca Olivetti from comment #0) > I think that lighttpd and its extra modules should be upgraded in the same > transaction (or maybe the extra modules updated before lighttpd). Neither of those is possible. Likely the only solution is the same as apache; to use a filetrigger to reload or restart the service when modules are installed. If the restart for the main package in %post is going to die if the modules aren't updated, then a reload at the end of the transaction probably won't work because of the failed service, so the main package's restart may need to be moved to %posttrans.
CC: (none) => luigiwalser
Can't we just require the specific lighttpd version in the mod_* packages?
CC: (none) => mageia
(In reply to Olivier Blin from comment #2) > Can't we just require the specific lighttpd version in the mod_* packages? The modules already require the main package, so the main package gets installed first. Adding a version to that requires won't change anything.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Version: 4 => CauldronWhiteboard: (none) => MGA5TOO
(In reply to David Walser from comment #3) > (In reply to Olivier Blin from comment #2) > > Can't we just require the specific lighttpd version in the mod_* packages? > > The modules already require the main package, so the main package gets > installed first. Adding a version to that requires won't change anything. So can't fix.... close as wontfix?? @ Shlomi Since you're the registered lighttpd maintainer: wdyt?
CC: (none) => marja11Assignee: bugsquad => shlomif
(In reply to Marja van Waes from comment #5) > (In reply to David Walser from comment #3) > > (In reply to Olivier Blin from comment #2) > > > Can't we just require the specific lighttpd version in the mod_* packages? > > > > The modules already require the main package, so the main package gets > > installed first. Adding a version to that requires won't change anything. > > So can't fix.... close as wontfix?? > > @ Shlomi > > Since you're the registered lighttpd maintainer: wdyt? I think also close as WONTFIX.
(In reply to Shlomi Fish from comment #6) > > I think also close as WONTFIX. Thanks.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX