[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#914606: marked as done (apache2 setup-instance (apache-multi) logrotation)



Your message dated Tue, 31 Mar 2020 06:33:45 +0000
with message-id <E1jJAT3-000Bxq-AB@fasolo.debian.org>
and subject line Bug#914606: fixed in apache2 2.4.43-1
has caused the Debian Bug report #914606,
regarding apache2 setup-instance (apache-multi) logrotation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
914606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914606
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Version: 2.4.25-3+deb9u6
Severity: normal

Dear Maintainer,

there is a problem with the setup-instance script for apache-multi
installation. The logrotation for the copyied instance is not working.
It looks like it is in debian stretch and buster/sid, in a kind of the
same way. In my fokus it's comming up with an installation from Ubuntu 18.04

What i did (stretch; buster/sid; ubuntu 18.04)

:~# apt-get install apache2
[...]

:~# sh /usr/share/doc/apache2/examples/setup-instance multi-xxx
Setting up /etc/apache2-multi-xxx ...
systemd is in use, no init script installed
use the 'apache2@multi-xxx.service' service to control your new instance
sample commands:
systemctl start apache2@multi-xxx.service
systemctl enable apache2@multi-xxx.service
Setting up symlinks: a2enmod-multi-xxx a2dismod-multi-xxx
a2ensite-multi-xxx a2dissite-multi-xxx a2enconf-multi-xxx
a2disconf-multi-xxx apache2ctl-multi-xxx


HINT "no init script installed"


:~# ls -la /etc/init.d/apache*
-rwxr-xr-x 1 root root 8181 Nov  3 12:34 /etc/init.d/apache2
-rwxr-xr-x 1 root root 2489 Nov  3 12:34 /etc/init.d/apache-htcacheclean

-> No init.d for the new multi-xxx apache


With in Debian 9.6 stretch

:~# cat /etc/logrotate.d/apache2-multi-xxx
/var/log/apache2-multi-xxx/*.log {
        daily
        missingok
        rotate 14
        compress
        delaycompress
        notifempty
        create 640 root adm
        sharedscripts
        postrotate
                if /etc/init.d/apache2-multi-xxx status > /dev/null ; then \
                    /etc/init.d/apache2-multi-xxx reload > /dev/null; \
                fi;
        endscript
        prerotate
                if [ -d /etc/logrotate.d/httpd-prerotate ]; then \
                        run-parts /etc/logrotate.d/httpd-prerotate; \
                fi; \
        endscript
}

:~# /etc/init.d/apache2-multi-xxx status
-su: /etc/init.d/apache2-multi-xxx: Datei oder Verzeichnis nicht gefunden

:~# /etc/init.d/apache2-multi-xxx reload
-su: /etc/init.d/apache2-multi-xxx: Datei oder Verzeichnis nicht gefunden



With in Debian buster/sid

:~$ cat /etc/logrotate.d/apache2-multi-xxx
/var/log/apache2-multi-xxx/*.log {
        daily
        missingok
        rotate 14
        compress
        delaycompress
        notifempty
        create 640 root adm
        sharedscripts
        postrotate
                if invoke-rc.d apache2-multi-xxx status > /dev/null
2>&1; then \
                    invoke-rc.d apache2-multi-xxx reload > /dev/null 2>&1; \
                fi;
        endscript
        prerotate
                if [ -d /etc/logrotate.d/httpd-prerotate ]; then \
                        run-parts /etc/logrotate.d/httpd-prerotate; \
                fi; \
        endscript
}


:~# invoke-rc.d apache2-multi-xxx status
Unit apache2-multi-xxx.service could not be found.
invoke-rc.d: initscript apache2-multi-xxx, action "status" failed.

:~# invoke-rc.d apache2-multi-xxx reload
/usr/sbin/invoke-rc.d: 527: /usr/sbin/invoke-rc.d:
/etc/init.d/apache2-multi-xxx: not found
invoke-rc.d: initscript apache2-multi-xxx, action "reload" failed.



In both cases the logrotation will fail because the reload is not
working. Also in the both cases the logrotate.d script for the multi-xxx
apache is a copy from the original logrotate.d apache2 script.

:~$ cat /usr/share/doc/apache2/examples/setup-instance
[...]
echo Setting up /etc/logrotate.d/apache2-$SUFFIX and
/var/log/apache2-$SUFFIX ...
cp -a /etc/logrotate.d/apache2 /etc/logrotate.d/apache2-$SUFFIX
perl -p -i -e s,apache2,apache2-$SUFFIX,g /etc/logrotate.d/apache2-$SUFFIX
[...]

As shown above the original apache has a init.d script installed and the
logrotation is working.


In that Ubuntu 18.04 installation i changed the
/etc/logrotate.d/apache2-multi-xxx in that way that i changed the reload
to systemd

from

[...]
                if invoke-rc.d apache2-multi-xxx status > /dev/null
2>&1; then \
                    invoke-rc.d apache2-multi-xxx reload > /dev/null 2>&1; \
[...]


in to

[...]

                if systemctl status apache2@multi-xxx.service >
/dev/null 2>&1; then \
                    systemctl reload apache2@multi-xxx.service >
/dev/null 2>&1; \
[...]

Looks like some day's after the logrotation is now workings as expected
for the multi-instance.

And in that case i think the upstream package for ubuntu 18.04 is
comming from Debian buster/sid.

Kind regards

 Horst

--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.43-1
Done: Xavier Guimard <yadd@debian.org>

We believe that the bug you reported is fixed in the latest version of
apache2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 914606@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard <yadd@debian.org> (supplier of updated apache2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 31 Mar 2020 08:02:12 +0200
Source: apache2
Architecture: source
Version: 2.4.43-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers <debian-apache@lists.debian.org>
Changed-By: Xavier Guimard <yadd@debian.org>
Closes: 914606 955348
Changes:
 apache2 (2.4.43-1) unstable; urgency=medium
 .
   [ Timo Aaltonen ]
   * mod_ssl: Add patches to fix TLS 1.3 client cert authentication for POST
     requests (Closes: #955348)
 .
   [ Moritz Schlarb ]
   * Fix logrotate script for multi-instance (Closes: #914606)
 .
   [ Xavier Guimard ]
   * New upstream version 2.4.43
   * Refresh patches
Checksums-Sha1: 
 e6720767a66e0a0f7a84c10b62b18b047a057a96 3498 apache2_2.4.43-1.dsc
 15d8605b094dfe5e283cd9e90770368dd14e26f2 9348230 apache2_2.4.43.orig.tar.gz
 e217995394ad01e4b1572ba8ecb7c25008cafd90 488 apache2_2.4.43.orig.tar.gz.asc
 0475b38fee9b3ea1bfc7fc91462ff453a5038a02 1015576 apache2_2.4.43-1.debian.tar.xz
Checksums-Sha256: 
 1f79e6ac3669395bb344ac42cce8e9b01db6567545dd80d57a673b6a4c439db6 3498 apache2_2.4.43-1.dsc
 2624e92d89b20483caeffe514a7c7ba93ab13b650295ae330f01c35d5b50d87f 9348230 apache2_2.4.43.orig.tar.gz
 b5fcb9366beebd0873ffa8f84b1415ed34e350f2cbbe9013f710b6ba1cb3291e 488 apache2_2.4.43.orig.tar.gz.asc
 159434868a2332bb2d0f22c4ca12913c7c60ad0dd550b9035ba9a13c0bcaa5c0 1015576 apache2_2.4.43-1.debian.tar.xz
Files: 
 9245410e9b58277132c77f2d6b99387d 3498 httpd optional apache2_2.4.43-1.dsc
 1e0298e7bf0afdb57e6a071c53a322e1 9348230 httpd optional apache2_2.4.43.orig.tar.gz
 b5aa2b5a61bd85fdfe11ae1452a2e59b 488 httpd optional apache2_2.4.43.orig.tar.gz.asc
 10125daef5e97a2932eeaa7aa7921994 1015576 httpd optional apache2_2.4.43-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl6C3zkACgkQ9tdMp8mZ
7uk1VQ/7BYkEuXsb5ZbyB+Wiz/M/JdFhZTLEwSpivB3IF3fNsv9e2/kJaLYyILqh
33OfebSMDTrEaifaO/73Pz2zGloj6KA21YkZsIb7BF9HCO0UsEu2gQf+ONVQHXCf
JSA1U8iLwCHAq9oi3MX0Bj3/w2wdUikMhpJJxjDbhzQDzElM8xG8Ksu/qpiJe+cx
wQvKqLqZWb1iGJfQzGgcXRX/egECOq01GdwHANA+OLww+CrzeqqS+v9q7l7lulQM
/5vel0ZjUk8it0OJmzsr/DHgDsXChXB8NMHEi376IFl6rnOYEMp9a6e//vSB64Qe
j3L/yIbdw0E3q08IWMjNioq7c8Vs+P3i7NQ4Qr54IHOoUMq7vc9YElIPQh8/UhUz
0S5AL7JkURumezpBow9bUS5A/TuyWFISgjgkLNDpzSYUsgJtt4VGOCgOs2GoAeRO
A45zGbg6DNOUREpOQIiblpTjJk41l5+ryx6/0UbtOQB5c/dp/9osX1K/n7PKEeet
b1jB3q9g9cNgfzerj0JYNX1O7QUpSELdgLSgKG8zzG6u6//BP/LyZipC5z8vP/Bs
B2VOE7sGgaposXO1IFz2z48Tw2FIYlQA6CHNShxKZKJlUjdi2790bKGeLB/3dwYU
S70yVSExF//rL8JyaVADM9lyr3LXlaaXc8KjBE2ZmW+gxmFRALw=
=+CIl
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: