Bug in apachectl script

[HawkinsDan]

Describe the bug
Multi-instance Apache installs will not start any site other than the primary after the 2.4.48 package.

There is a script located in /usr/sbin/ called apachectl. In the 2.4.48 version, line 78 looks like this:

HTTPD=${APACHE_HTTPD:-usr/sbin/apache2}

In the 2.4.49 and later versions, this line looks like this:

HTTPD=${APACHE_HTTPD:-usr/sbin/apache2$SUFFIX}

Where $SUFFIX is the name of the other Apache instances. This variable sets the location for the Apache binary, so appending on the suffix makes it look in a directory that doesn’t exist.

To Reproduce
Steps to reproduce the behavior:

1. Update Apache on a multi-instance system via your repository to any version after 2.4.48
2. Attempt to start any apache2 - works.
3. Attempt to start any of the other instances (e.g. apache2@suffix1 or apache2@suffix2). Attempt fails with the following output:
   Oct 06 22:11:17 SERVER systemd[1]: Starting The Apache HTTP Server...
   Oct 06 22:11:17 SERVER apachectl[848]: /usr/sbin/apachectl: 174: /usr/sbin/apache2-suffix1: not found
   Oct 06 22:11:17 SERVER apachectl[816]: Action 'start' failed.

Expected behavior
I expected the apache2@suffixX sites to start as they had in 2.4.48 and earlier.

Distribution (please complete the following information):

• OS: Ubuntu
• Architecture: amd64
• Repository: ppa:ondrej/apache2

Package(s) (please complete the following information):

Additional context

[oerdnj]

Yadd (Debian co-maintainer) was so kind that he fixed the issue while doing the security update to 2.4.51, so this is fixed in the current version (2.4.51-1...)

[HawkinsDan]

Thanks so much. Dan From: Ondřej Surý ***@***.***> Sent: Thursday, October 07, 2021 3:32 PM To: oerdnj/deb.sury.org ***@***.***> Cc: Dan Latvala ***@***.***>; Author ***@***.***> Subject: Re: [oerdnj/deb.sury.org] Bug in apachectl script (#1659) ***EXTERNAL SOURCE ALERT***. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Yadd (Debian co-maintainer) was so kind that he fixed the issue while doing the security update to 2.4.51, so this is fixed in the current version (2.4.51-1...) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1659 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIHMAFDAMCNIPIS473VG75TUFX7VPANCNFSM5FRWSFQQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.