Multiserver - Monitoring doesn't work after Masterserver change

Discussion in 'Installation/Configuration' started by crazyiven, Dec 2, 2019.

  1. crazyiven

    crazyiven New Member

    Good Morning :)

    I've a Multiserver Setup with 4 Slave Servers and it worked perfect until yesterday. I had to switch the Masterserver so I installed the new Server with the HowTo and ISPConfig worked fine. I've stopped all daemons on the old server, transfered the dbispconfig DB and the User with Rights vom mysql DB to the new server and changed the ip of the hostname in DNS.

    The Setup is working ... i can add/edit/delete Details on Slave Servers and it works great ... the Job queue works as it should. But one little problem is the Monitoring page. This page is "stuck" with the Details of the timeframe with the old Masterserver and doesnt change. I've updated all Servers from 3.1.15 to 3.1.15p2 ... but only the Masterserver shows this version ... all Slaves still show 3.1.15.

    Reading other threads i tried the "Reconfigure Permissions in master database" from one Slave, but this Slave still shows 3.1.15 and other old data (E-mail Queue, Server uptime, Logfiles ....) and I even set the logging to debug and can see all is working on the Slave side:
    Code:
    Mon 02 Dec 2019 10:03:02 AM CET 02.12.2019-10:03 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'.
    Mon 02 Dec 2019 10:03:02 AM CET 02.12.2019-10:03 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    Mon 02 Dec 2019 10:03:02 AM CET finished.
    Mon 02 Dec 2019 10:04:01 AM CET
    Mon 02 Dec 2019 10:04:01 AM CET
    Mon 02 Dec 2019 10:04:01 AM CET 02.12.2019-10:04 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'.
    Mon 02 Dec 2019 10:04:01 AM CET 02.12.2019-10:04 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    Mon 02 Dec 2019 10:04:01 AM CET finished.
    Mon 02 Dec 2019 10:05:01 AM CET
    Mon 02 Dec 2019 10:05:01 AM CET
    Mon 02 Dec 2019 10:05:01 AM CET 02.12.2019-10:05 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'.
    Mon 02 Dec 2019 10:05:01 AM CET 02.12.2019-10:05 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    Mon 02 Dec 2019 10:05:01 AM CET finished.
    
    So what can I do next? I can do everthing with this setup/servers, but the monitoring page isn't working as it should. What can i do to investigate more?

    Kind regards
    Marcus
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Have you changed also /etc/hosts file on master and all slaves?
     
  3. crazyiven

    crazyiven New Member

    Yes all /etc/hosts Files on master & slave have the new ip, that was the first thing i did, sorry for not telling in the first post :)
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Check the root crontab on the slave to ensure it contains lines for server.sh and cron.sh cronjob.
     
  5. crazyiven

    crazyiven New Member

    Already did ... all slaves are working fine ... can add/edit/delete Domains and the server does his job ... so this connection is working ... all is working exept Monitoring Details :/
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    That's why I asked about the second cronjob, server.sh is responsible for the things that work and cron.sh is responsible for things like the monitoring which does not work :)

    What you can try is to empty the whole monitor_data table on the master. monitor_data is empty when you install a new system and get's filled by the monitoring scripts step by step when they run, so it's ok to remove any data from that database table. And run atable repair on that table with phpmyadmin to ensure it's not damaged.
     
  7. crazyiven

    crazyiven New Member

    Hey Till :)
    Thanks for this information ... but the "/usr/local/ispconfig/server/cron.sh" works without an error ... it justs shows nothing ... Loglevel is Debug. So "nothing" seems for me to be right? On the Masterserver "/usr/local/ispconfig/server/cron.sh" shows nothing as well.

    I've saved the monitor_data Table, checked it (repair) and then truncted it ... lets wait and see :)
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, that's ok. the cron part (sadly) does not has debugging yet.
     
  9. crazyiven

    crazyiven New Member

    The table was truncted and the masterserver filled his details it up right after ... from the other servers i just got 10 entries (3 x log_messages, 4 x system_update & 3 x sys_log). The entries with log_messages are filled with syslog details and all other entries in this table just have the entrie "a:1:{s:6:"output";s:0:"";}" in data.

    What can I do/check next? The 3 log_messages details are "ok" and filled with the latests details from syslog, but there is a missing a lot of other entries ;)
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Maybe you disabled functions in the cli php.ini file on the slaves which are required, something like exec and so on?
     
  11. crazyiven

    crazyiven New Member

    No changes we're made to any php config ... just the masterserver got new Hardware/IP and the php.ini is unchanged since installation of server or update to debian 10

    Is there a way for me to "force" the details to get maybe an error message?
     
  12. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    you can check, that no cronjob on the slave is marked es running in mysql
    Code:
    select name from sys_cron where running=1;
    maybe the monitor-job is still marked as running.
     
  13. crazyiven

    crazyiven New Member

    Hey Florian :)

    Thanks for your response ... this query has no results, so no job is marked running. Any other idea?
     
  14. crazyiven

    crazyiven New Member

    Hello :)

    I "fixed" the problem and the details are working now ... i get monitoring details now ... but the "solution" was "tricky".

    I stopped the cronjob for cron.sh & server.sh on the slaves and edited the following file:
    Code:
    /usr/local/ispconfig/server/lib/classes/cronjob.inc.php
    In Line 86 i changed
    Code:
    if($run_it == true || $debug_mode === true) {
    to
    Code:
    if($run_it == true || $debug_mode === true || 1) {
    and started the cron.sh file by hand.

    And with this the details "fly" into the monitor_data table and all details seems to be there. I need to wait to confirm, but this seems to fix my problem after all. Of course after the run by hand i changed the file back and reactivated the cronjob ... this was a few minutes ago. I'll message tomorrow with the info if all details are fully back :)

    Kind regards and thanks for your help ... the cron.sh information was realy good :)
    Marcus
     
  15. crazyiven

    crazyiven New Member

    Hello :)

    Sorry got delayed ... but the monitoring is working as it should now ... can't say what was wrong, but this "hard reset" fixed it :). All details are back and up2date ... just like "the old days" with the old mainserver :)

    Kind regards
    Marcus
     

Share This Page