Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2.
Debian Apache Maintainers, DSL> Which init system are you using? The answer was in TG's original bug report: Init: sysvinit (via /sbin/init) I believe that this regression only occurs for non-systemd init systems (i.e. sysvinit). Popcon says sysvinit-core is installed on 0.88% of reporting systems: https://qa.debian.org/popcon.php?package=sysvinit Some of those may be pre-Jessie, so the percentage could be even lower. On Tue, 6 Jul 2021 13:56:21 +0200, Adam Borowski wrote: > + if pgrep -f ^/usr/sbin/apache2 > /dev/null; then > +invoke-rc.d apache2 reload > + fi > ... > Changing querying status to pgrep is also bogus: it will detect any apache2 > process rather than just ours. ... How could there be a /usr/sbin/apache2 process that is not ours? Any suggestions for improving this (after bullseye release, of course)? Thank you, Dan Urbana, Illinois
Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2.
Thorsten, et al, On Fri, 02 Jul 2021 14:08:00 +, Thorsten Glaser wrote: > Having just upgraded machines from 2.4.46-4 to 2.4.48-3 > I now get daily cron mails: > | /etc/cron.daily/logrotate: > | Reloading Apache httpd web server: apache2. Under the default systemd, the following commands generate no output: * sudo invoke-rc.d apache2 reload * sudo systemctl restart apache2.service Which init system are you using? Daniel Lewart Urbana, Illinois
Bug#990580: debdiff for NMU apache2 (= 2.4.48-3.1) (was Re: Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2., caused by #979813)
On Sun, 11 Jul 2021, Adam Borowski wrote: > I for one believe the old behaviour was superior for the common case of > "success" -- no news is good news No disagreement from here. We could do things like… output=$(command 2>&1; echo $? >tempfile) case $(cat tempfile 2>&1) in (0) ;; (*) printf >&2 '%s\n' "$output" ;; esac … but… > • three weeks before the release is no time for such meddling … precisely this. > • it should be coded in sysv-rc/runit/etc instead of every daemon Nope. This is out of the scope of init systems. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg * Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter *
Bug#990580: debdiff for NMU apache2 (= 2.4.48-3.1) (was Re: Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2., caused by #979813)
On Sat, Jul 10, 2021 at 11:37:33PM +0200, Thorsten Glaser wrote: > OK, thanks for the maintainer approval. Accordingly, I have > just uploaded the attached debdiff. I chose to direct the > output to syslog instead of the bitbucket so it is not lost > if someone indeed needs it so it isn’t a regression. > - invoke-rc.d apache2 reload > + invoke-rc.d apache2 reload 2>&1 | logger -t apache2.logrotate I for one believe the old behaviour was superior for the common case of "success" -- no news is good news, no need to bother anyone just because logrotate does its job, especially that the restart is already logged elsewhere. On the other hand, logging failures is a damn good idea. But then: • three weeks before the release is no time for such meddling • it should be coded in sysv-rc/runit/etc instead of every daemon (the author of the patch that regressed this was probably used to a certain inferior rc system that fails to notify an interactive user whether a reload succeeded or was a no-op due to in-chroot policy/etc, which is a major no-no) Thus, thank you TG for the for-Bullseye fix! Meow. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ If you ponder doing what Jesus did, remember than flipping tables ⢿⡄⠘⠷⠚⠋⠀ and chasing people with a whip is a prime choice. ⠈⠳⣄
Bug#990580: debdiff for NMU apache2 (= 2.4.48-3.1) (was Re: Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2., caused by #979813)
On Fri, 9 Jul 2021, Yadd wrote: > Apache2 is RFH for years, feel free to contribute OK, thanks for the maintainer approval. Accordingly, I have just uploaded the attached debdiff. I chose to direct the output to syslog instead of the bitbucket so it is not lost if someone indeed needs it so it isn’t a regression. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg * Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter *diff -Nru apache2-2.4.48/debian/apache2.logrotate apache2-2.4.48/debian/apache2.logrotate --- apache2-2.4.48/debian/apache2.logrotate 2021-06-20 13:55:24.0 +0200 +++ apache2-2.4.48/debian/apache2.logrotate 2021-07-10 23:31:24.0 +0200 @@ -14,7 +14,7 @@ endscript postrotate if pgrep -f ^/usr/sbin/apache2 > /dev/null; then - invoke-rc.d apache2 reload + invoke-rc.d apache2 reload 2>&1 | logger -t apache2.logrotate fi endscript } diff -Nru apache2-2.4.48/debian/changelog apache2-2.4.48/debian/changelog --- apache2-2.4.48/debian/changelog 2021-06-20 16:39:33.0 +0200 +++ apache2-2.4.48/debian/changelog 2021-07-10 23:31:28.0 +0200 @@ -1,3 +1,11 @@ +apache2 (2.4.48-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Direct init script reload output from logrotate to syslog, to +avoid mail-spamming the local admin (Closes: #990580) + + -- Thorsten Glaser Sat, 10 Jul 2021 23:31:28 +0200 + apache2 (2.4.48-3) unstable; urgency=medium * Fix debian/changelog
Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2., caused by #979813
Le 09/07/2021 à 05:04, Thorsten Glaser a écrit : > Thanks Adam for the analysis! > >> To stop the mails from logrotate, could you please change back: >> - invoke-rc.d apache2 reload >> + invoke-rc.d apache2 reload > /dev/null 2>&1 >> >> otherwise, people running Bullseye will be mightily unhappy. >> >> I also wonder why such a cleanup was done late during hard freeze. > > Indeed. ping‽ (I intend to NMU if no activity happens.) > > bye, > //mirabilos Hi, Apache2 is RFH for years, feel free to contribute
Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2., caused by #979813
Thanks Adam for the analysis! > To stop the mails from logrotate, could you please change back: > - invoke-rc.d apache2 reload > + invoke-rc.d apache2 reload > /dev/null 2>&1 > > otherwise, people running Bullseye will be mightily unhappy. > > I also wonder why such a cleanup was done late during hard freeze. Indeed. ping‽ (I intend to NMU if no activity happens.) bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg * Mit unserem Consulting bieten wir Unternehmen maßgeschneiderte Angebote in Form von Beratung, Trainings sowie Workshops in den Bereichen Softwaretechnologie, IT Strategie und Architektur, Innovation und Umsetzung sowie Agile Organisation. Besuchen Sie uns auf https://www.tarent.de/consulting . Wir freuen uns auf Ihren Kontakt. *
Bug#990580: apache2: [regression] daily cron mails from logrotate: Reloading Apache httpd web server: apache2.
Package: apache2 Version: 2.4.48-3 Severity: important X-Debbugs-Cc: t...@mirbsd.de, debian-rele...@lists.debian.org Having just upgraded machines from 2.4.46-4 to 2.4.48-3 I now get daily¹ cron mails: | From: Anacron | Message-ID: <20210702075325.946f340...@ci-busyapps.lan.tarent.de> | To: r...@ci-busyapps.lan.tarent.de | Date: Fri, 2 Jul 2021 07:53:25 + (UTC) | Subject: Anacron job 'cron.daily' on ci-busyapps.lan.tarent.de | | /etc/cron.daily/logrotate: | Reloading Apache httpd web server: apache2. This is a regression that’s going to severely annoy admins and ought to be fixed, including for bullseye. ① I know they are daily because I have been getting them on another system for some time already but didn’t know if it was that system or something in the package; as multiple other systems are now affected identically, I know it’s a bug in the package. -- Package-specific info: -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages apache2 depends on: ii apache2-bin 2.4.48-3 ii apache2-data 2.4.48-3 ii apache2-utils2.4.48-3 ii dpkg 1.20.9 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii mime-support 3.66 ii perl 5.32.1-4 ii procps 2:3.3.17-5 Versions of packages apache2 recommends: ii ssl-cert 1.1.0+nmu1 Versions of packages apache2 suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom ii lynx [www-browser] 2.9.0dev.6-2 Versions of packages apache2-bin depends on: ii libapr11.7.0-6 ii libaprutil11.6.1-5 ii libaprutil1-dbd-pgsql 1.6.1-5 ii libaprutil1-ldap 1.6.1-5 ii libbrotli1 1.0.9-2+b2 ii libc6 2.31-12 ii libcrypt1 1:4.4.18-4 ii libcurl4 7.74.0-1.3 ii libjansson42.13.1-1.1 ii libldap-2.4-2 2.4.57+dfsg-3 ii liblua5.3-05.3.3-1.1+b1 ii libnghttp2-14 1.43.0-1 ii libpcre3 2:8.39-13 ii libssl1.1 1.1.1k-1 ii libxml22.9.10+dfsg-6.7 ii perl 5.32.1-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages apache2-bin suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom ii lynx [www-browser] 2.9.0dev.6-2 Versions of packages apache2 is related to: ii apache2 2.4.48-3 ii apache2-bin 2.4.48-3 -- Configuration Files: /etc/apache2/mods-available/ssl.conf changed [not included] /etc/apache2/sites-available/000-default.conf changed [not included] /etc/apache2/sites-available/default-ssl.conf changed [not included] -- no debconf information
