Only old data in monitor tab.

Discussion in 'General' started by smurf, Jul 13, 2011.

  1. smurf

    smurf New Member

    Probably after upgrade ISPConfig to 3.0.3.3 from older 3.0.x.x I have this problem.
    In the monitor tab I can see still only old log data from 2011-04-07. (like Overview, RAID State, Mail log, Mail queue, fail2ban log, and other in this tab).
    Restart server, refresh monitor site, without effect.
    All other server and ISPConfig functions o.k. Log files in var/log actualized o.k.
    Any idea pls? :confused:
     
    Last edited: Jul 13, 2011
  2. philippeS

    philippeS New Member

    Same Issue with 3.0.4.6 version, nobody else have this ?

    Best

    Philippe
     
  3. till

    till Super Moderator

  4. philippeS

    philippeS New Member

    ok I have this errors in the ISPConfig3 cron logs :

    FATAL: Could not load /lib/modules/3.2.13-grsec-xxxx-grs-ipv6-64/modules.dep: No such file or directory
    Failed to load mptctl

    Error: (CLI:003) Specified controller does not exist.

    PHP Warning: Invalid argument supplied for foreach() in /usr/local/ispconfig/server/lib/classes/monitor_tools.inc.php on line 1072
    repquota: Cannot stat() mounted device /dev/root: No such file or directory
    repquota: Cannot stat() mounted device /dev/root: No such file or directory
    FATAL: Could not load /lib/modules/3.2.13-grsec-xxxx-grs-ipv6-64/modules.dep: No such file or directory
    Failed to load mptctl

    I believe the absence of the mptctl module does not make the server.sh to fail nore the repquota. Perhaps the PHP error at line 1072 of monitor_tools.php ?

    Best.

    Philippe
     
  5. till

    till Super Moderator

    The log entries are not relevant for this issue like you expected and the php line is just a warning, so it will not make the script fail. Please follow the server debug procedure described at the end of the post I linked above, run the debug at a minute that can be divided by 5, e.g. 5, 10, 15 etc. as the monitor is not triggered every minute.
     
  6. philippeS

    philippeS New Member

    # crontab -e
    comment the line concerned by server.sh cronjob
    # /usr/local/ispconfig/server/lib/classes/monitor_tools.inc.php

    Thanks a lot till !
    It was a parse error at the line 1072 that I believe I tried to solve the warning one day and I did not do that very seriously because I didn't resolve the warning and broke my monitoring :(
    My fault.

    Best.

    Philippe
     

Share This Page