Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Upgrading Fedora 27 to F39: httpd won't start |
|
| Author |
|
MrVideo
Joined: 08 Jan 2024
Posts: 2
Location: Madison, WI
|
 Posted: Mon 08 Jan '24 20:34 Post subject: Upgrading Fedora 27 to F39: httpd won't start |
 |
|
The currently running version is 2.4.34 and the new one is 2.4.57. I've copied over the /etc/httpd files from the old location to the new. After getting a bunch of missing modules installed, I'm down to what may be the final issue as to why the server won't start:
| Code: |
× httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Mon 2024-01-08 12:27:04 CST; 15s ago
Duration: 9min 8.317s
Docs: man:httpd.service(8)
Process: 26907 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 26907 (code=exited, status=1/FAILURE)
Status: "Reading configuration..."
CPU: 49ms
Jan 08 12:27:04 mrvideo systemd[1]: Starting httpd.service - The Apache HTTP Server...
Jan 08 12:27:04 mrvideo (httpd)[26907]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Jan 08 12:27:04 mrvideo systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Jan 08 12:27:04 mrvideo systemd[1]: httpd.service: Failed with result 'exit-code'.
Jan 08 12:27:04 mrvideo systemd[1]: Failed to start httpd.service - The Apache HTTP Server. |
A friend believes that the OPTIONS variable is a red herring. Any thoughts? Any way to get a lot of debugging info into a file?
UPDATE: I removed the $OPTIONS from the startup service file and it still fails reading my configuration. Yep, going to need some extra logging info to try and narrow this down. |
|
| Back to top |
|
MrVideo
Joined: 08 Jan 2024
Posts: 2
Location: Madison, WI
|
| Posted: Mon 08 Jan '24 22:37 Post subject: |
|
|
Looks like I pretty much have it solved. The log file was a great help. I needed w3c markup stuff installed and then it complained about another missing module. Now it starts.
I can't view my homepage though. SElinux is being a PITA. I HATE SELinux. I'm trying to load the main index.html page and SELinux is bitching about it. So the browser is shown the Apache test page.
The issue is no longer with Apache. |
|
| Back to top |
|
|
|
|
|
|
