Monitor_data issue

Discussion in 'Installation/Configuration' started by itsnedkeren, May 24, 2011.

  1. itsnedkeren

    itsnedkeren New Member

    Hi all,

    Since this morning I'm seeing this in my system log:

    Code:
    2011-05-24 10:25 	node01.domain.tld 	Warning 	DB::query(INSERT INTO monitor_data (server_id, type, created, data, state) VALUES (1, 'sys_log', 1306225509, 'a:1:{s:6:"output";s:0:"";}', 'warning')) -> mysql_query Duplicate entry '1-sys_log-1306225509' for key 'PRIMARY'
    The list continues with about 20+ entries all with the same error message. And for some odd reason the monitor keeps stating that "some system components needs an upgrade", even though I see no upgrades available on my system.

    Furthermore, system log also shows this:

    Code:
    Deprecated: Function ereg() is deprecated in /usr/local/ispconfig/interface/lib/classes/listform.inc.php on line 315
    System info:
    Debian 6.0
    ISPC 3.0.3.3

    Thanks for any replies...
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please check the monitor_data table on your server with phpmyadmin to ensure that it is not corrupted. Then check the date and time on your server and make sure that its correct.


    Thats ok and not realted to your problem.
     
  3. itsnedkeren

    itsnedkeren New Member

    Code:
    node01:~# date
    Tue May 24 12:33:36 CEST 2011


    Seems fine? I have attached a screenshot.

    Thanks Till
     

    Attached Files:

  4. till

    till Super Moderator Staff Member ISPConfig Developer

    That looks fine so far. Is this a multiserver setup?
     
  5. itsnedkeren

    itsnedkeren New Member

    No, has always only been this one server.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Please empty (truncate) the monitor_data table and check 5-10 minutes later in ispconfig is the monitor data is written again.
     
  7. itsnedkeren

    itsnedkeren New Member

    Thanks a lot, that worked :) I had to truncate "sys_log" at the same time or the error kept coming.
     
  8. itsnedkeren

    itsnedkeren New Member

    Same error again, last night :( What to do?


    Code:
    2011-05-24 23:55 	node01.domain.tld 	Warning 	DB::query(INSERT INTO monitor_data (server_id, type, created, data, state) VALUES (1, 'sys_log', 1306274110, 'a:1:{s:6:"output";s:0:"";}', 'warning')) -> mysql_query Duplicate entry '1-sys_log-1306274110' for key 'PRIMARY'
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Have you changed anything in the ispconfig server scripts or did you change the ispconfig cronjob?
     
  10. itsnedkeren

    itsnedkeren New Member


    The only thing I have changes are the master config for creation of new websites. I changed port 80 to 8000 as I'm running Varnish.

    /usr/local/ispconfig/server/conf/vhost.conf.master

    Code:
    <VirtualHost <tmpl_var name='ip_address'>:8000>
    EDIT: These changes I made months ago, but errors just started the other day.
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    This change should not be related to the problem.

    It seems that your system runs the server.sh cronjob from ispconfig twice which causes duplicate entries to be inserted into the monitor_data column or your cluster has more then one server with server_id 1.

    If you run a multiserver setup, please check that every server has a unique server_id in its config.inc.php files and that there are no duplicate lines for the server.sh cronjob in the root crontab on the servers.
     
  12. itsnedkeren

    itsnedkeren New Member

    This is the only lines in crontab, regarding ISPConfig:


    Code:
    * * * * * /usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log
    30 00 * * * /usr/local/ispconfig/server/cron_daily.sh > /dev/null 2>> /var/log/ispconfig/cron.log
    Server is not in a multiserver setup and has never been.

    Thanks Till

    EDIT: I've investigated and this error first occured on the 24th of may. The only thing I have done on the console in that time frame is apt-get upgrade. This is the "history.log" for apt:

    Code:
    Start-Date: 2011-05-24  10:31:20
    Commandline: apt-get upgrade
    Upgrade: postfix:amd64 (2.7.1-1, 2.7.1-1+squeeze1), libapr1:amd64 (1.4.2-6, 1.4.2-6+squeeze2), postfix-mysql:amd64 (2.7.1-1, 2.7.1-1+squeeze1), postfix-doc:amd64 (2.7.1-1, 2.7.1-1+squeeze1)
    End-Date: 2011-05-24  10:31:26
    
    Start-Date: 2011-05-24  11:21:28
    Commandline: apt-get install linux-headers-2.6.32-5-amd64 build-essential gcc
    Install: linux-kbuild-2.6.32:amd64 (2.6.32-1, automatic), linux-headers-2.6.32-5-common:amd64 (2.6.32-31, automatic), linux-headers-2.6.32-5-amd64:amd64 (2.6.32-31)
    End-Date: 2011-05-24  11:21:36
    
    Start-Date: 2011-05-24  23:50:52
    Commandline: apt-get upgrade
    Upgrade: linux-image-2.6.32-5-amd64:amd64 (2.6.32-31, 2.6.32-34squeeze1), firmware-linux-free:amd64 (2.6.32-31, 2.6.32-34squeeze1), linux-headers-2.6.32-5-common:amd64 (2.6.32-31, 2.6.32-34squeeze1), linux-headers-2.6.32-5-amd64:amd64 (2.6.32-31, 2.6.32-34squeeze1), linux-base:amd64 (2.6.32-31, 2.6.32-34squeeze1), linux-libc-dev:amd64 (2.6.32-31, 2.6.32-34squeeze1)
    End-Date: 2011-05-24  23:51:20
    
     
    Last edited: May 26, 2011
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    Have you restarted the server after the update? If not, you should try that, as the update installed also a new kernel.
     
  14. itsnedkeren

    itsnedkeren New Member

    Does not seem so no, I've tried that and will report back tomorrow :)

    Thank Till
     
  15. itsnedkeren

    itsnedkeren New Member


    So far so good, all green in the monitor, for now :)
     

Share This Page