Opened 4 months ago

Last modified 7 weeks ago

#2305 new defect

Apache service fails to start

Reported by: darkblueb Owned by: osgeolive@…
Priority: major Milestone: OSGeoLive14.0
Component: OSGeoLive Keywords: apache
Cc:

Description

user@osgeolive:~$ sudo service apache2 status
● apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Thu 2021-01-28 00:10:43 UTC; 11min ago
       Docs: https://httpd.apache.org/docs/2.4/
    Process: 1570 ExecStart=/usr/sbin/apachectl start (code=killed, signal=TERM)

Jan 28 00:09:13 osgeolive systemd[1]: Starting The Apache HTTP Server...
Jan 28 00:10:43 osgeolive systemd[1]: apache2.service: start operation timed out. Terminating.
Jan 28 00:10:43 osgeolive systemd[1]: apache2.service: Failed with result 'timeout'.
Jan 28 00:10:43 osgeolive systemd[1]: Failed to start The Apache HTTP Server.

Attachments (8)

t2.png (292.9 KB) - added by darkblueb 4 months ago.
2021-01-27-210243_1392x863_scrot.png (237.9 KB) - added by darkblueb 4 months ago.
packet capture of beta1 boot
2021-01-27-214849_1392x863_scrot.png (174.2 KB) - added by darkblueb 4 months ago.
2021-01-27-214845_1392x863_scrot.png (180.3 KB) - added by darkblueb 4 months ago.
2021-01-27-214723_1392x863_scrot.png (176.0 KB) - added by darkblueb 4 months ago.
2021-01-27-214716_1392x863_scrot.png (190.8 KB) - added by darkblueb 4 months ago.
2021-01-27-214553_1392x863_scrot.png (186.3 KB) - added by darkblueb 4 months ago.
2021-01-27-215741_1392x863_scrot.png (245.3 KB) - added by darkblueb 4 months ago.
apache2 failed boot sequence

Download all attachments as: .zip

Change history (16)

Changed 4 months ago by darkblueb

Attachment: t2.png added

comment:1 Changed 4 months ago by darkblueb

user@osgeolive:/var/log$ sudo service apache2 restart
user@osgeolive:/var/log$ sudo service apache2 status
● apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2021-01-28 01:04:42 UTC; 1s ago
       Docs: https://httpd.apache.org/docs/2.4/
    Process: 5719 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
   Main PID: 5747 (apache2)
      Tasks: 40 (limit: 9423)
     Memory: 107.0M
     CGroup: /system.slice/apache2.service
             ├─5747 /usr/sbin/apache2 -k start
             ├─5748 /usr/sbin/apache2 -k start
             ├─5752 /usr/sbin/apache2 -k start
             ├─5753 /usr/sbin/apache2 -k start
             ├─5754 /usr/sbin/apache2 -k start
             ├─5755 /usr/sbin/apache2 -k start
             ├─5756 /usr/sbin/apache2 -k start
             ├─5757 /usr/sbin/apache2 -k start
             ├─5758 /usr/sbin/apache2 -k start
             ├─5759 /usr/sbin/apache2 -k start
             ├─5760 /usr/sbin/apache2 -k start
             ├─5761 /usr/sbin/apache2 -k start
             └─5762 /usr/sbin/apache2 -k start

Jan 28 01:04:26 osgeolive systemd[1]: Starting The Apache HTTP Server...
Jan 28 01:04:35 osgeolive apachectl[5733]: [Thu Jan 28 01:04:35.348887 2021] [core:warn] [pid 5733] AH001>
Jan 28 01:04:35 osgeolive apachectl[5733]: AH00558: apache2: Could not reliably determine the server's fu>
Jan 28 01:04:42 osgeolive systemd[1]: Started The Apache HTTP Server.

Changed 4 months ago by darkblueb

packet capture of beta1 boot

Changed 4 months ago by darkblueb

Changed 4 months ago by darkblueb

Changed 4 months ago by darkblueb

Changed 4 months ago by darkblueb

Changed 4 months ago by darkblueb

Changed 4 months ago by darkblueb

apache2 failed boot sequence

comment:3 Changed 4 months ago by kalxas

Works for me

comment:4 Changed 4 months ago by darkblueb

Priority: blockermajor

comment:5 Changed 3 months ago by kalxas

Is this still happening?

comment:6 Changed 3 months ago by darkblueb

one test today and yes, it failed in the same way (Berkeley, Calif residential DSL)

comment:7 Changed 2 months ago by darkblueb

failed on rc1 in the same way. Some research on the nature of the failure shows that this is a local device protocol query, not a query to a well-known external address. Users may or may not experience this in their own local network environment; the effect in a VM is unknown

comment:8 Changed 7 weeks ago by astrid_emde

I have no problems on my installation with rc2

Note: See TracTickets for help on using tickets.