Monitoring behavior of slaves in a multiserver setup

Discussion in 'Installation/Configuration' started by cmks, Oct 30, 2023.

Tags:
  1. cmks

    cmks Member HowtoForge Supporter

    Hi team,
    when we update ispconfig from 3.2.9p1 to 3.2.11 and now to 3.2.11p1 I noticed the behavior of the admin monitoring panel:
    Most slaves reports the actual version of ispconfig after a short period of time (a hour or two) and some stays on the old information for days. Finally after some days all slave reports the correct version - but why did it take so long an how can I trigger the update of the monitored information manually?

    Another question: When some slave is down or inaccessible for days or weeks, the admin monitoring panel freezes in the last state and don't give a hint, that a slave may be offline. Is this by design?

    Regards,
    cmks
     
    cmks, Oct 30, 2023
    #1
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    There is no way to manually trigger this. It can take some more time sometimes, I would need to check the code to see why, but I suppose updating it in the database is not triggered by ISPConfig updates but it might be by some other actions happening.
     
    Th0m, Oct 30, 2023
    #2
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    There must have been a connection issue between that slave node and the master or the runtime info for the crown plugins was corrupted and stuck in running state. The version information is updated every 5 minutes. If it takes longer than that, then something is wrong. You can debug this with the cron_debug.php script, the corn plugin is 100-monitor_ispconfig_version.inc.php
     
    till, Oct 30, 2023
    #3
    ahrasis and remkoh like this.

Share This Page