Pzz
Verified User
Hi,
I was updating to httpd-2.4.48 and after the "Done!"message I took a look at the log:
I've no idea what a #Hunk is, or does, but httpd.service definitly doesn't want to start the job. The details weren't (for me) very helpfull in solving my problem, but I guess the problem already started with the core.c.
Shouldn't the install just stop after an error like this?
I put a backup back in place, but I'm affraid the same error will happen when I do a retry.
Is there a way for me to solve this?
Thanks...
I was updating to httpd-2.4.48 and after the "Done!"message I took a look at the log:
Code:
...
Patching apache for hardened symlinks patch...
patching file include/http_core.h
patching file server/core.c
Hunk #1 succeeded at 153 (offset 14 lines).
Hunk #2 FAILED at 1548.
Hunk #3 FAILED at 1726.
2 out of 3 hunks FAILED -- saving rejects to file server/core.c.rej
...
..
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
..
...
Restarting apache.
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Done!
I've no idea what a #Hunk is, or does, but httpd.service definitly doesn't want to start the job. The details weren't (for me) very helpfull in solving my problem, but I guess the problem already started with the core.c.
Shouldn't the install just stop after an error like this?
I put a backup back in place, but I'm affraid the same error will happen when I do a retry.
Is there a way for me to solve this?
Thanks...