hallo
ich habe ein grösseres problem mit meinem vserver
(debian sarge bei winprofi.de mit syscp)
etwa jede stunden macht der ganze server einfach dicht, er akzeptiert weder ftp noch http, aber "anpingbar" ist er noch.
in der daemon.log steht folgendes:
und immer so weiter
ich dachte mir, das da ein cron verrückt spielt, aber ich kann nichts finden
cron.hourly ist leer und in cron.d steht:
php4 -rwxr-xr-x root
postgresql -rwxr-xr-x root
syscp -rw-r--r-- root
inhalt php4:
inhalt postgresql:
inhalt syscp:
/var/spool/cron ist leer
ich weiss nicht mehr weiter...
ich habe ein grösseres problem mit meinem vserver
(debian sarge bei winprofi.de mit syscp)
etwa jede stunden macht der ganze server einfach dicht, er akzeptiert weder ftp noch http, aber "anpingbar" ist er noch.
in der daemon.log steht folgendes:
Code:
Mar 20 04:37:23 vs-241-72 named[27511]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 04:37:24 vs-241-72 named[27511]: could not listen on UDP socket: permission denied
Mar 20 04:37:24 vs-241-72 named[27511]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 04:37:24 vs-241-72 named[27511]: not listening on any interfaces
Mar 20 04:40:57 vs-241-72 named[1990]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 04:40:57 vs-241-72 named[1990]: could not listen on UDP socket: permission denied
Mar 20 04:40:57 vs-241-72 named[1990]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 04:40:57 vs-241-72 named[1990]: not listening on any interfaces
Mar 20 05:37:24 vs-241-72 named[27512]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 05:37:24 vs-241-72 named[27512]: could not listen on UDP socket: permission denied
Mar 20 05:37:24 vs-241-72 named[27512]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 05:37:24 vs-241-72 named[27512]: not listening on any interfaces
Mar 20 05:40:57 vs-241-72 named[1988]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 05:40:57 vs-241-72 named[1988]: could not listen on UDP socket: permission denied
Mar 20 05:40:57 vs-241-72 named[1988]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 05:40:57 vs-241-72 named[1988]: not listening on any interfaces
Mar 20 06:37:24 vs-241-72 named[27511]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 06:37:24 vs-241-72 named[27511]: could not listen on UDP socket: permission denied
Mar 20 06:37:24 vs-241-72 named[27511]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 06:37:24 vs-241-72 named[27511]: not listening on any interfaces
Mar 20 06:40:57 vs-241-72 named[1990]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 06:40:57 vs-241-72 named[1990]: could not listen on UDP socket: permission denied
Mar 20 06:40:57 vs-241-72 named[1990]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 06:40:57 vs-241-72 named[1990]: not listening on any interfaces
Mar 20 07:37:24 vs-241-72 named[27512]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 07:37:24 vs-241-72 named[27512]: could not listen on UDP socket: permission denied
Mar 20 07:37:24 vs-241-72 named[27512]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 07:37:24 vs-241-72 named[27512]: not listening on any interfaces
Mar 20 07:40:57 vs-241-72 named[1988]: listening on IPv4 interface eth0:vs-241-72, 213.131.241.72#53
Mar 20 07:40:57 vs-241-72 named[1988]: could not listen on UDP socket: permission denied
Mar 20 07:40:57 vs-241-72 named[1988]: creating IPv4 interface eth0:vs-241-72 failed; interface ignored
Mar 20 07:40:57 vs-241-72 named[1988]: not listening on any interfaces
und immer so weiter
ich dachte mir, das da ein cron verrückt spielt, aber ich kann nichts finden
cron.hourly ist leer und in cron.d steht:
php4 -rwxr-xr-x root
postgresql -rwxr-xr-x root
syscp -rw-r--r-- root
inhalt php4:
Code:
# /etc/cron.d/php4: crontab fragment for php4
# This purges session files older than X, where X is defined in seconds
# as the largest value of session.gc_maxlifetime from all your php.ini
# files, or 24 minutes if not defined. See /usr/lib/php4/maxlifetime
# Look for and purge old sessions every 30 minutes
09,39 * * * * root [ -d /var/lib/php4 ] && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm
inhalt postgresql:
Code:
# Regular cron jobs for the postgresql package
#
# To ensure proper access rights, 'ident sameuser' access for localhost is
# required in /etc/postgresql/pg_hba.conf. This is now the default setting for
# the Debian configuration.
#
# If password access for "local" is turned on in /etc/postgresql/pg_hba.conf,
# you must create a file ~postgres/.pgpass containing a line specifying the
# password, as explained in section 1.11 of the PostgreSQL Programmer's Guide
# (package postgresql-doc).
#
# If autovacuum is turned on in /etc/postgresql/postmaster.conf, you need
# to give the -F option to do.maintenance for it to do anything.
# Run VACUUM ANALYSE on all databases every 5 hours
2 0,5,10,15,20 * * 1-6 postgres if [ -z "`ps --no-headers -C pg_autovacuum`" -a -x /usr/lib/postgresql/bin/do.maintenance ]; then /usr/lib/postgresql/bin/do.maintenance -a; fi
# On Sunday run a VACUUM FULL ANALYSE as well
# If you run a 24/7 site, you may want to comment out this line and save VACUUM
# FULL for when you think you really need it
# 10 3 * * sun postgres /usr/bin/test -x /usr/lib/postgresql/bin/do.maintenance && /usr/lib/postgresql/bin/do.maintenance -a -f -F
inhalt syscp:
Code:
#
# Set PATH, otherwise restart-scripts won't find start-stop-daemon
#
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
#
# Regular cron jobs for the syscp package
#
*/5 * * * * root /usr/bin/php4 -q -c /etc/php4/syscpcron /var/www/syscp/scripts/cronscript.php
/var/spool/cron ist leer
ich weiss nicht mehr weiter...