Sometimes apache2 hang after boot

Bug #1821293 reported by Claudio Fior
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

If i restart apache2 everything works fine. No adivice in access and system log.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: apache2 2.4.34-1ubuntu2 [modified: lib/systemd/system/apache2.service]
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
Apache2ConfdDirListing: False
Apache2Modules:
 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
 httpd (pid 2247) already running
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 22 09:08:50 2019
SourcePackage: apache2
UpgradeStatus: Upgraded to cosmic on 2018-10-16 (156 days ago)
error.log:
 [Fri Mar 22 08:38:50.991565 2019] [:notice] [pid 2247] mod_ruid2/0.9.8 enabled
 [Fri Mar 22 08:38:50.994977 2019] [mpm_prefork:notice] [pid 2247] AH00163: Apache/2.4.34 (Ubuntu) OpenSSL/1.1.1 configured -- resuming normal operations
 [Fri Mar 22 08:38:50.995002 2019] [core:notice] [pid 2247] AH00094: Command line: '/usr/sbin/apache2'
modified.conffile..etc.apache2.mods-available.userdir.conf: [modified]
modified.conffile..etc.apache2.sites-available.000-default.conf: [modified]
mtime.conffile..etc.apache2.mods-available.userdir.conf: 2017-09-15T14:41:18.959666
mtime.conffile..etc.apache2.sites-available.000-default.conf: 2017-10-17T09:11:21.482173

Revision history for this message
Claudio Fior (caiofior) wrote :
Revision history for this message
Paride Legovini (paride) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

There isn't really enough information here for a developer to confirm this issue is a bug, or to begin working on it, so I am marking this bug Incomplete for now.

If you can provide exact steps so that a developer can reproduce the original problem, then please add them to this bug and change the status back to New.

Changed in apache2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Claudio Fior (caiofior) wrote :
Download full text (4.4 KiB)

Today the same problem, no data added to /var/log/apache2/access.log, but in /var/log/apache2/error.log I found:

[Fri Mar 29 09:25:39.351071 2019] [core:notice] [pid 2292] AH00051: child pid 11272 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:39.351073 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11272
[Fri Mar 29 09:25:41.353823 2019] [core:notice] [pid 2292] AH00051: child pid 11301 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:41.353869 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11301
[Fri Mar 29 09:25:42.357223 2019] [core:notice] [pid 2292] AH00051: child pid 11303 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:42.357255 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11303
[Fri Mar 29 09:25:42.357285 2019] [core:notice] [pid 2292] AH00051: child pid 11304 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:42.357291 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11304
[Fri Mar 29 09:25:43.364074 2019] [core:notice] [pid 2292] AH00051: child pid 11308 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:43.364104 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11308
[Fri Mar 29 09:25:43.364131 2019] [core:notice] [pid 2292] AH00051: child pid 11309 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:43.364134 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11309
[Fri Mar 29 09:25:43.364146 2019] [core:notice] [pid 2292] AH00051: child pid 11312 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:43.364149 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11312
[Fri Mar 29 09:25:43.364161 2019] [core:notice] [pid 2292] AH00051: child pid 11313 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:43.364164 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11313
[Fri Mar 29 09:25:44.365277 2019] [core:notice] [pid 2292] AH00051: child pid 11316 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:44.365311 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11316
[Fri Mar 29 09:25:44.365332 2019] [core:notice] [pid 2292] AH00051: child pid 11318 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:44.365338 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11318
[Fri Mar 29 09:25:44.365357 2019] [core:notice] [pid 2292] AH00051: child pid 11319 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri Mar 29 09:25:44.365363 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11319
[Fri Mar 29 09:25:44.365382 2019] [core:notice] [pid 2292] AH00051: child pid 11321 exit signal Segmentat...

Read more...

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

IIRC apache by default does not store dumps (to avoid exploiting remotely to fill disks or anything like it).
But it can be enabled [1][2]

[1]: https://askubuntu.com/questions/612532/how-to-get-an-apache-core-dump
[2]: https://ashout.com/enable-coredump-apache2-ubuntu/

Revision history for this message
Paride Legovini (paride) wrote :

Hello Claudio,

Is your system otherwise stable, or did you notice anything else crashing in a similar way? You could try to search your system logs for segmentation faults or other unexpected crashes. This is useful information to understand if the problem is actually with apache2 or with some other component of your system (e.g. a library) which makes Apache crash as a consequence.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Have you checked /var/crash for apache crash files?

Revision history for this message
Claudio Fior (caiofior) wrote :
Download full text (7.9 KiB)

Nothing found in /var/crash, enabled code dump but nothing happens:

[Fri Apr 05 14:25:24.740627 2019] [core:error] [pid 2264] AH00546: no record of generation 0 of exiting child 27311
[Fri Apr 05 14:25:24.740630 2019] [core:notice] [pid 2264] AH00052: child pid 27312 exit signal Segmentation fault (11)
[Fri Apr 05 14:25:24.740633 2019] [core:error] [pid 2264] AH00546: no record of generation 0 of exiting child 27312
[Fri Apr 05 14:25:24.740636 2019] [core:notice] [pid 2264] AH00052: child pid 27313 exit signal Segmentation fault (11)
[Fri Apr 05 14:25:24.740679 2019] [core:error] [pid 2264] AH00546: no record of generation 0 of exiting child 27313
[Fri Apr 05 14:25:24.740683 2019] [core:notice] [pid 2264] AH00052: child pid 27314 exit signal Segmentation fault (11)
[Fri Apr 05 14:25:24.740685 2019] [core:error] [pid 2264] AH00546: no record of generation 0 of exiting child 27314
[Fri Apr 05 14:25:24.740689 2019] [core:notice] [pid 2264] AH00052: child pid 27315 exit signal Segmentation fault (11)
[Fri Apr 05 14:25:24.740691 2019] [core:error] [pid 2264] AH00546: no record of generation 0 of exiting child 27315
[Fri Apr 05 14:25:24.740695 2019] [core:notice] [pid 2264] AH00052: child pid 27316 exit signal Segmentation fault (11)
[Fri Apr 05 14:25:24.740699 2019] [core:error] [pid 2264] AH00546: no record of generation 0 of exiting child 27316

No core dump has been created.

Apache hangs usually during lunch break when the pc is idle. This is the syslog produced in this time:

Apr 5 12:50:26 pc-claudio automount[2635]: message repeated 2 times: [ key ".hidden" not found in map source(s).]
Apr 5 12:56:13 pc-claudio systemd-timesyncd[1092]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Apr 5 12:56:23 pc-claudio systemd-timesyncd[1092]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 5 12:56:33 pc-claudio systemd-timesyncd[1092]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 5 12:56:43 pc-claudio systemd-timesyncd[1092]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 5 13:00:02 pc-claudio CRON[17540]: (caiofior) CMD (rsync -r /home/caiofior/Dropbox/ABBREVIA_DOC/ /media/Documenti/Documenti/sviluppo/Documenti)
Apr 5 13:00:02 pc-claudio cron[1278]: sendmail: fatal: open /etc/postfix/main.cf: No such file or directory
Apr 5 13:00:02 pc-claudio postfix/sendmail[17553]: fatal: open /etc/postfix/main.cf: No such file or directory
Apr 5 13:00:03 pc-claudio CRON[17539]: (caiofior) MAIL (mailed 208 bytes of output but got status 0x004b from MTA#012)
Apr 5 13:01:45 pc-claudio systemd[1]: Started Run anacron jobs.
Apr 5 13:01:45 pc-claudio anacron[18211]: Anacron 2.3 started on 2019-04-05
Apr 5 13:01:45 pc-claudio anacron[18211]: Normal exit (0 jobs run)
Apr 5 13:09:02 pc-claudio systemd[1]: Starting Clean php session files...
Apr 5 13:09:02 pc-claudio CRON[21032]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Apr 5 13:09:11 pc-claudio systemd[1]: Started Clean php session files.
Apr 5 13:17:02 pc-claudio CRON[24148]: (root) CMD ( cd / && run-parts --report /etc/cron.ho...

Read more...

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

The log holds nothing obvious that I'd see, if anything I wonder if something is overheating. 115 °C is really high for most components.
Hhave you tried to enable apache core dumps as I asked in comment #4

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]

Changed in apache2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.