Opened 4 years ago
Closed 4 years ago
#2305 closed defect (worksforme)
Apache service fails to start
Reported by: | darkblueb | Owned by: | |
---|---|---|---|
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)
Change History (17)
by , 4 years ago
by , 4 years ago
Attachment: | 2021-01-27-210243_1392x863_scrot.png added |
---|
packet capture of beta1 boot
by , 4 years ago
Attachment: | 2021-01-27-214849_1392x863_scrot.png added |
---|
by , 4 years ago
Attachment: | 2021-01-27-214845_1392x863_scrot.png added |
---|
by , 4 years ago
Attachment: | 2021-01-27-214723_1392x863_scrot.png added |
---|
by , 4 years ago
Attachment: | 2021-01-27-214716_1392x863_scrot.png added |
---|
by , 4 years ago
Attachment: | 2021-01-27-214553_1392x863_scrot.png added |
---|
comment:2 by , 4 years ago
apparently a clean boot (no failure):
image https://trac.osgeo.org/osgeolive/attachment/ticket/2305/2021-01-27-210243_1392x863_scrot.png
by , 4 years ago
Attachment: | 2021-01-27-215741_1392x863_scrot.png added |
---|
apache2 failed boot sequence
comment:4 by , 4 years ago
Priority: | blocker → major |
---|
comment:6 by , 4 years ago
one test today and yes, it failed in the same way (Berkeley, Calif residential DSL)
comment:7 by , 4 years ago
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:9 by , 4 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.