syslog shows outdated actions

Discussion in 'General' started by electronico_nc, Jan 1, 2015.

  1. Ubuntu 14.04 x64
    3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
    Multi-server setup, sync of /var/www /var/vmail via unison.

    Here is a sample of what syslog shows :
    Code:
    Jan  1 08:13:01 comeon CRON[9349]: (root) CMD (/usr/bin/unison &> /dev/null)
    Jan  1 08:14:01 comeon CRON[9382]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 > /dev/null | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done)
    Jan  1 08:15:01 comeon CRON[9409]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
    Dec 28 02:34:01 comeon CRON[9407]: (root) CMD (/usr/bin/unison &> /dev/null)
    Jan  1 08:15:01 comeon CRON[9410]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 > /dev/null | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done)
    Jan  1 08:15:01 comeon CRON[9411]: (root) CMD (/usr/bin/unison &> /dev/null)
    Code:
    Jan  1 08:25:01 comeon CRON[11144]: (getmail) CMD (/usr/local/bin/run-getmail.sh > /dev/null 2>> /dev/null)
    Jan  1 08:26:01 comeon CRON[11625]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 > /dev/null | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done)
    Jan  1 01:51:01 comeon CRON[11628]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 > /dev/null | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done)
    Jan  1 08:26:01 comeon CRON[11628]: (root) CMD (/usr/bin/unison &> /dev/null)
    Jan  1 08:27:01 comeon CRON[11854]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 > /dev/null | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done)
    Code:
    Jan  1 09:03:02 comeon CRON[18087]: (root) CMD (/usr/bin/unison &> /dev/null)
    Jan  1 09:04:01 comeon CRON[18123]: (root) CMD (/usr/bin/unison &> /dev/null)
    Dec 28 03:31:01 comeon CRON[18143]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 > /dev/null | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done)
    Jan  1 09:05:01 comeon CRON[18143]: (getmail) CMD (/usr/local/bin/run-getmail.sh > /dev/null 2>> /dev/null)
    Jan  1 09:05:01 comeon CRON[18142]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
    You can see a line dated from the past in the middle, but CRON id is well incremented the right way.
    I don't understand how it is possible ...
    Thanks for any track.
    Nicolas

    PS : One other thing is that cron.daily isn't run anymore (logwatch, logrotate, apt, etc ...) but searches points that date/time problems could lead into this.
    PS2 : date is well sync between the 2 servers:
    Code:
    date && ssh root@server2 'date'
    jeudi 1 janvier 2015, 10:13:25 (UTC+1100)
    jeudi 1 janvier 2015, 10:13:25 (UTC+1100)
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    How long does a unison run takes? Are there multiple unison processes running (check with ps)?
     
  3. Code:
    UNISON 2.40.102 started propagating changes at 07:06:03.58 on 02 Jan 2015
    ...
    UNISON 2.40.102 finished propagating changes at 07:06:03.65 on 02 Jan 2015
    Synchronization complete at 07:06:03  (4 items transferred, 0 skipped, 0 failed)
    There is no unison proccess running, except the one that is setup to run every mlnute via crontab.
    There are 2 files in .unison directory:
    Code:
    ls -lh /root/.unison
    -rw------- 1 root root  27M janv.  2 07:15 ar3d152e74bc622710e0119906bf039f26
    -rw-r--r-- 1 root root 4,3K oct.  23 08:38 default.prf
    -rw------- 1 root root  710 janv.  2 07:15 fp3d152e74bc622710e0119906bf039f26
    -rw------- 1 root root 144M janv.  2 07:15 unison.log
    In the syslog lines posted above, you can see this is not especially unison that writes outdated lines, they are sometimes :
    /usr/local/ispconfig/server/server.sh

    Nicolas
     

Share This Page