Apache raucht ab, hat dieser Cronjob was damit zu tun?

P

passbreak2001

Grünschnabel
Hallo, ich habe ein kleines nerviges Problemchen, welches ich irgendwie nicht in den Griff bekomme.

Alle paar Tage funktioniert mein Apache nicht mehr. 'ps aux' sagt das die dazugehörigen Applikationen noch laufen. Starte ich Apache neu neu kommt diese Standartfehlermeldung:

# no pid found, apache not running?

Habe das soweit nachverfolgt als das ich rausgefunden habe das nicht Apache beendet wird sondern nur die pid verschwindet

Code:
[Sun Feb 04 05:22:50 2007] [warn] child process 24382 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 24383 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 24384 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 24386 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 24393 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 24394 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 24960 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 6151 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 6152 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:50 2007] [warn] child process 7390 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24382 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24383 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24384 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24386 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24393 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24394 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 24960 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 6151 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 6152 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:52 2007] [warn] child process 7390 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24382 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24383 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24384 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24386 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24393 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24394 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 24960 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 6151 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 6152 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:54 2007] [warn] child process 7390 still did not exit, sending a SIGTERM
[Sun Feb 04 05:22:56 2007] [error] child process 24382 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 24383 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 24384 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 24386 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 24393 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 24394 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 24960 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 6151 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 6152 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:56 2007] [error] child process 7390 still did not exit, sending a SIGKILL
[Sun Feb 04 05:22:58 2007] [notice] caught SIGTERM, shutting down

Das merkwürdige, immer alle paar Tage um 5.20 rum. folgender Cronjob wird zeitgleich, so vermute ich, gestartet:

Code:
#!/bin/sh
#
# man-db cron weekly

set -e

if ! [ -d /var/cache/man ]; then
    # Recover from deletion, per FHS.
    mkdir -p /var/cache/man
    chown man:root /var/cache/man
    chmod 2755 /var/cache/man
fi

# regenerate man database
if [ -x /usr/bin/mandb ]; then
    # --pidfile /dev/null so it always starts; mandb isn't really a daemon,
    # but we want to start it like one.
    start-stop-daemon --start --pidfile /dev/null \
		      --startas /usr/bin/mandb --oknodo --chuid man \
		      -- --quiet
fi

exit 0


Ich kenne mich leider nicht so gut aus das ich die Ausmaße kenne von diesem beim Vserver (Debian Sarge/Confixx professional) vorinstallierten Cronjob. Das Script betrifft zwar nur anscheinend die mandb aber könnte es sein das es weitere Auswirkungen auf die Apache pid hat?

Bin für alle Antworten und auch andere Theorien dankbar. Möchte endlich sichergehen das ich den Apache nicht alle paar Tage manuell starten muss...
 

Ähnliche Themen

Problem mit Apache2 + MySQL Server

OpenSuse 12.3 / Tiefschlaf funktioniert nicht

Akonadi startet nicht mehr

Apache /var/www zu /home/ich/www wechseln

NagiosGrapher 1.7.1 funktioniert nicht

Zurück
Oben