Bug 1221775

I got during http-server installation via YasT2: 


Error: Cannot adjust 'apache2' service.

After installation of apache2 I checked apache2.service:

--


localhost:~ # systemctl status apache2
× apache2.service - The Apache Webserver
     Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Wed 2024-03-20 20:31:57 CET; 1min 25s ago
    Process: 3099 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE)
   Main PID: 3099 (code=exited, status=1/FAILURE)
        CPU: 136ms

Mar 20 20:31:57 localhost systemd[1]: Starting The Apache Webserver...
Mar 20 20:31:57 localhost start_apache2[3099]: [Wed Mar 20 20:31:57.453480 2024] [php7:crit] [pid 3099:tid 28147303>
Mar 20 20:31:57 localhost start_apache2[3099]: AH00013: Pre-configuration failed
Mar 20 20:31:57 localhost systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
Mar 20 20:31:57 localhost systemd[1]: apache2.service: Failed with result 'exit-code'.
Mar 20 20:31:57 localhost systemd[1]: Failed to start The Apache Webserver.
localhost:~ # systemctl restart apache2
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details.
localhost:~ # journalctl -xeu apache2
~
~
~
~
~
~
~
Mar 20 20:31:57 localhost systemd[1]: Starting The Apache Webserver...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit apache2.service has begun execution.
░░ 
░░ The job identifier is 4056.
Mar 20 20:31:57 localhost start_apache2[3099]: [Wed Mar 20 20:31:57.453480 2024] [php7:crit] [pid 3099:tid 28147303>
Mar 20 20:31:57 localhost start_apache2[3099]: AH00013: Pre-configuration failed
Mar 20 20:31:57 localhost systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 20 20:31:57 localhost systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Mar 20 20:31:57 localhost systemd[1]: Failed to start The Apache Webserver.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit apache2.service has finished with a failure.
░░ 
░░ The job identifier is 4056 and the job result is failed.
Mar 20 20:33:35 localhost systemd[1]: Starting The Apache Webserver...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit apache2.service has begun execution.
░░ 
░░ The job identifier is 4166.
Mar 20 20:33:35 localhost start_apache2[3356]: [Wed Mar 20 20:33:35.117142 2024] [php7:crit] [pid 3356:tid 28147321>
Mar 20 20:33:35 localhost start_apache2[3356]: AH00013: Pre-configuration failed
Mar 20 20:33:35 localhost systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 20 20:33:35 localhost systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Mar 20 20:33:35 localhost systemd[1]: Failed to start The Apache Webserver.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit apache2.service has finished with a failure.
░░ 
░░ The job identifier is 4166 and the job result is failed.


--

I think "Pre-configuration failed" is the error.

Created attachment 873669 [details]
yast logs

I compared with build 64.2 which doesn't have issue with apache2, but /usr/share/doc/packages/apache2 is not available neither.

with latest build71.1 I am not able to reproduce this issue.
But the problem with /usr/share/doc/packages is still remaining.

It means apache2 packages got installed without doc files.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18953 can help in this case. apache2 test is passed so far.

But the issue with doc needs your attention, thanks!

Hi Zaoliang and developer,

I would like to add my findings as well.

Now we have the below apache2 packages on sle15sp6 build 71.1:

# rpm -qa |grep apache2
apache2-2.4.58-150600.1.1.x86_64
apache2-prefork-2.4.58-150600.1.1.x86_64
apache2-utils-2.4.58-150600.1.1.x86_64

# rpm -q apache2-2.4.58-150600.1.1.x86_64 --changelog |more
* Mon Mar 18 2024 eugenio.paolantonio@suse.com
- SLE-only: forward-port gensslcert change to generate dhparams certificate
  using a valid FIPS method (bsc#1198913)

* Tue Feb 20 2024 dimstar@opensuse.org
- Use %autosetup macro. Allows to eliminate the usage of deprecated
  %patchN.

* Mon Jan 29 2024 dmueller@suse.com
- use grep -E for egrep

---------------------------------------------------------------

And I can find that some changes are happening now:

1. the file /usr/share/doc/packages/apache2/httpd.conf.default is gone, and below 2 files can be seen and some contents are changed as well:

# rpm -ql apache2-2.4.58-150600.1.1.x86_64 |grep httpd-default.conf
/usr/share/doc/packages/apache2/conf/extra/httpd-default.conf
/usr/share/doc/packages/apache2/conf/original/extra/httpd-default.conf

2. 'httpd2-prefork' binary file is gone, and now it is '/usr/sbin/httpd-prefork'
# rpm -ql apache2-prefork-2.4.58-150600.1.1.x86_64 |grep sbin
/usr/sbin/httpd
/usr/sbin/httpd-prefork

-----------------------------------------------------------------

The test can pass with my code changes below:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18953/files

https://openqa.suse.de/tests/13872532#details

----------------------------------------------------------------

So Can I ask for developer's kindly confirmation?

1. Are these changes are expected or regression issues?
2. If the changes are expected, do they only happen on sle15sp6?  [how about TW/leap and other sle releases]

Please let me know if you need access my test setup to debug.

Hi,

I'm CCing David as he's the apache2 maintainer.

On build 73.1, apache2 reintroduces the compatibility symlinks (including for example http2-prefork), so I hope that most of the issues are solved there (bsc#1221880).


For the configuration file, @David, please confirm if the example configuration being moved to /usr/share/doc/packages/apache2/conf/httpd.conf is okay (to my untrained eye, since it's the example one, I suppose it's fine).

I prepared one fix for the testsuite to move to the new configuration file here [0], I will submit it as a Pull Request soon.

Thanks!


[0] https://github.com/g7/os-autoinst-distri-opensuse/commit/cfe74e2e22bfa23da159a1b8200b2e0b4947b6ac

> For the configuration file, @David, please confirm if the example
> configuration being moved to 
> /usr/share/doc/packages/apache2/conf/httpd.conf is okay (to my 
> untrained eye, since it's the example one, I suppose it's fine).

Yes, it's fine to put it there but please explicitly mention we are adding it to /usr/share/dpc it on the changelog.

Thank you again!

Please indicate the current expectation for fixing the bug using the Target Milestone field. What do we believe is possible? 

In the cases where we do not plan to deliver or cannot guess (!?) please do not enter anything, but you can comment if you wish to provide more details.