ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    HTTPD Fails To Start On Reboot Fedora

    IT Discussion
    httpd fedora 27
    5
    11
    2.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      NashBrydges
      last edited by

      I'm still pretty new to Fedora and this is an error I've never seen before. After rebooting the server (there was no other action other than a reboot), I get the following error:

         Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
        Drop-In: /usr/lib/systemd/system/httpd.service.d
                 └─php-fpm.conf
         Active: failed (Result: exit-code) since Wed 2018-03-21 16:33:14 EDT; 7s ago
           Docs: man:httpd.service(8)
        Process: 1498 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
       Main PID: 1498 (code=exited, status=1/FAILURE)
         Status: "Reading configuration..."
      
      Mar 21 16:33:14 bookstack-fedora systemd[1]: Starting The Apache HTTP Server...
      Mar 21 16:33:14 bookstack-fedora httpd[1498]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::c644:b17d:61d2:109c. Set the 'ServerName' directive globally to suppress this message
      Mar 21 16:33:14 bookstack-fedora systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
      Mar 21 16:33:14 bookstack-fedora systemd[1]: Failed to start The Apache HTTP Server.
      Mar 21 16:33:14 bookstack-fedora systemd[1]: httpd.service: Unit entered failed state.
      Mar 21 16:33:14 bookstack-fedora systemd[1]: httpd.service: Failed with result 'exit-code'.
      

      I'm guessing the primary error is this:

      Mar 21 16:33:14 bookstack-fedora httpd[1498]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::c644:b17d:61d2:109c. Set the 'ServerName' directive globally to suppress this message
      

      So I know there is a commented out "ServerName" in /etc/httpd/conf/http.conf so I set it to "localhost" but on reboot, Apache won't start. I tried 127.0.0.1, same error.

      Is there somewhere else this global server name needs to be set?

      1 Reply Last reply Reply Quote 0
      • S
        scottalanmiller
        last edited by

        Look in the main logs rather than the systemctl error messages. Generally way better info in there.

        1 Reply Last reply Reply Quote 1
        • J
          JaredBusch
          last edited by JaredBusch

          Ignore that error 100% of the time.

          That is an info message only and is not relevant.

          R 1 Reply Last reply Reply Quote 0
          • R
            Reid Cooper @JaredBusch
            last edited by

            @jaredbusch said in HTTPD Fails To Start On Reboot Fedora:

            Ignore that error 100% of the time.

            That is an info message only and is not relevant.

            I see it all the time on working systems.

            J 1 Reply Last reply Reply Quote 0
            • N
              NashBrydges
              last edited by

              Yep, that was more useful. It was the same issue that Jared had had with a misnamed access.log file instead of access_log file in the conf file. Fixed the correct file name and all is well in the world again.

              1 Reply Last reply Reply Quote 0
              • J
                JaredBusch @Reid Cooper
                last edited by

                @reid-cooper said in HTTPD Fails To Start On Reboot Fedora:

                @jaredbusch said in HTTPD Fails To Start On Reboot Fedora:

                Ignore that error 100% of the time.

                That is an info message only and is not relevant.

                I see it all the time on working systems.

                Correct. it is an information error only. As it says, you can set the variable to make it not show up.

                1 Reply Last reply Reply Quote 0
                • B
                  black3dynamite
                  last edited by

                  Was bookstack working before the reboot?

                  N 1 Reply Last reply Reply Quote 0
                  • N
                    NashBrydges @black3dynamite
                    last edited by

                    @black3dynamite said in HTTPD Fails To Start On Reboot Fedora:

                    Was bookstack working before the reboot?

                    It was working. Only after reboot did it screw up.

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      JaredBusch @NashBrydges
                      last edited by

                      @nashbrydges said in HTTPD Fails To Start On Reboot Fedora:

                      @black3dynamite said in HTTPD Fails To Start On Reboot Fedora:

                      Was bookstack working before the reboot?

                      It was working. Only after reboot did it screw up.

                      @black3dynamite he probably has not rebooted since the first install which he did prior to me fixing the log file error.

                      B N 2 Replies Last reply Reply Quote 1
                      • B
                        black3dynamite @JaredBusch
                        last edited by black3dynamite

                        @jaredbusch said in HTTPD Fails To Start On Reboot Fedora:

                        @nashbrydges said in HTTPD Fails To Start On Reboot Fedora:

                        @black3dynamite said in HTTPD Fails To Start On Reboot Fedora:

                        Was bookstack working before the reboot?

                        It was working. Only after reboot did it screw up.

                        @black3dynamite he probably has not rebooted since the first install which he did prior to me fixing the log file error.

                        That's what I was thinking too.
                        @NashBrydges There is a typo error in the bookstack.conf file
                        https://mangolassi.it/topic/16587/fedora-update-breaks-httpd/12

                        1 Reply Last reply Reply Quote 0
                        • N
                          NashBrydges @JaredBusch
                          last edited by

                          @jaredbusch said in HTTPD Fails To Start On Reboot Fedora:

                          @nashbrydges said in HTTPD Fails To Start On Reboot Fedora:

                          @black3dynamite said in HTTPD Fails To Start On Reboot Fedora:

                          Was bookstack working before the reboot?

                          It was working. Only after reboot did it screw up.

                          @black3dynamite he probably has not rebooted since the first install which he did prior to me fixing the log file error.

                          Yup. You are correct.

                          1 Reply Last reply Reply Quote 0
                          • 1 / 1
                          • First post
                            Last post