SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
|
Notes |
|
|
|
|
|
|
|
Got the same issue. Thomas already gave me the hint with the blackholedns script but it doesn't seem to work. We are pretty sure it is related to the blackholedns because this process is allays stuck:
Here is pstree sometime the next morning after backup failed:
init???clamd
??collectd
??dnsmasq
??6*[efw-console]
??efw-console???bash
??emi
??fcron???fcron???bash???run-parts???blackholedns
??2*[getblackholedns]
??havp???20*[havp???havp]
??httpd???6*[httpd]
??keepalived???2*[keepalived]
??lcd-daemon
??logsurfer
??monit
??ntpd
??2*[python]
??snmpd
??snort
??squid???squid???20*[ncsa_auth]
? ??unlinkd
??sshd???sshd???bash
? ??sshd???bash???pstree
??stslog???openvpn
??syslog-ng
??udevd
??ulogd
??uplinksdaemon
Here a ps aux sometime the next morning after backup failed:
ps aux | grep cron
root 6408 0.0 0.0 1876 552 ? S Sep03 0:00 /usr/sbin/fcron -c /etc/fcron.conf
root 6409 0.0 0.1 3248 1064 ? S Sep03 0:00 /bin/bash -c [ -x /bin/run-parts ] && run-parts --report /etc/cron.daily
root 6410 0.0 0.0 1496 604 ? S Sep03 0:00 run-parts --report /etc/cron.daily
root 8241 0.0 0.0 2896 676 pts/1 R+ 10:34 0:00 grep cron
root 12575 0.0 0.0 1876 596 ? Ss Aug28 0:02 /usr/sbin/fcron -c /etc/fcron.conf
As soon as i kill the hanging cron.daily processes it will run the next day fine. This all happens randomly on my EFW's. I have a 2 Cluster and 3 nonclusteresd ones. And sometimes it works fine on one for a couple of days but on another one it fails then it changes and fails on a different one. So absolutly not reproducable. Any clue? |
|
|
|
|
|
Seems to work now again. No idea why. Will keep you up to date. |
|
|
|
|
changed the cronscript that it runs the download completely detached
here's the patch:
Index: src/lib/blackholedns.cron
===================================================================
--- src/lib/blackholedns.cron (revision 23770)
+++ src/lib/blackholedns.cron (working copy)
@@ -33,7 +33,7 @@
# Author: Peter Warasin <peter@endian.it>
# Description: calls blackholedns list retriever
-PATH=/sbin:/bin:/usr/sbin:/usr/bin
-/usr/local/bin/getblackholedns.py &>/dev/null &
+PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
+run-detached getblackholedns.py &>/dev/null
exit 0 |
|
|
|
|
|
i will completely detach the process, so it can't happen anymore. so we are on the secure side. |
|
|
|
|
|
detaching does not block run-parts anymore, so this is resolved |
|
backup.jpeg (69,595) 2010-06-14 08:41