I have a multi-server configuration (ISPConfig 3.2.7p1) with one particular node (not the master server) running a web server. I need to change the IP address for that node (and only the IP address) and I'm wondering if there are any instructions for doing that? Can I just change the IP address on the server and re-run the ISPConfig install/upgrade script? I should note I'm not using the System -> Server Config settings to set the IP address etc.
Change the IP-address in the operating system the usual way. Then examine files in /etc, for example grep -r 11.22.33.44 /etc to find the ones with the IP. Examine other hosts in the cluster for IP in /etc tree. It is probably in /etc/hosts at least. Use the ISPConfig multiserver installation guide or ISPCOnfig manual to see where in database the host with IP is defined, and change those. I think running ispconfig install or update script wont be needed in this.
If I remember correctly you mysql access via ip also need to be updated i.e. remove the old one and add the new one.
I've made all these changes (ip addresses in /etc, the database etc), but I'm still having an issue. When I look in ISPConfig on the master server, the syslog for the server with the changed IP is being updated, but none of the others and changes queued up to go down to the server aren't being picked up. Any ideas?
Interestingly, things seem to be getting to the server with the changed IP address, just not getting updating the master server...
So an update. I was wrong about the logs, apparently I got about an hour more of syslog than any other then it stopped too. However I seem to have fixed the outstanding command thing, it seems if the child server and master server get out of sync, things get stuck. I updated server.updated and now I can send commands, they get applied and get removed from the outstanding count properly. I could still do with some help figuring out why the log files/stats/etc arn't getting back to the master server though.
This should help finding out why stuff does not happen as it should: https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/ Then there is this: https://forum.howtoforge.com/threads/please-read-before-posting.58408/
I've increased the debug level on both the master server and the web server but I'm not seeing any issues in the logs. When I manually run the server.sh on the web server all I get is the following: Code: 04.09.2022-14:34 - DEBUG [plugins.inc:155] - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 04.09.2022-14:34 - DEBUG [server:217] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock finished server.php. For the record, the master server is: Code: Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PHP 7.4.30 (cli) (built: Jul 7 2022 15:51:43) ( NTS ) Copyright (c) The PHP Group Zend Engine v3.4.0, Copyright (c) Zend Technologies with Zend OPcache v7.4.30, Copyright (c), by Zend Technologies And the Web Server: Code: Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PHP 7.4.25 (cli) (built: Oct 23 2021 21:53:50) ( NTS ) Copyright (c) The PHP Group Zend Engine v3.4.0, Copyright (c) Zend Technologies with Zend OPcache v7.4.25, Copyright (c), by Zend Technologies And I've attached the output of the test script to this message.
I've changed the IP address on the web server host, created appropriate mysql accounts on the master server and updated the settings in ispconfig. I can now send commands to the web server (create a website, delete one etc) and have them aknowledged and actioned, however none of the monitoring information (CPU use, memory use, disk use, packages to be updated, ispconfig logs, syslogs etc) are getting sent back to the master server. Edited to add: I've turned on the higher debug level by setting log_priority in config.inc.php to zero and I can see the main cron script running each of the 100-monitor scripts, but nothing is getting back to the master server and there doesn't seem to be any errors logged. Other web servers and dns servers are updating their monitor information normally, it's just the one that's had the IP changed that's having problems.
Please choose only one LE client which is basically the one come with your original setup in master server. This is not to resolve your main problem though.
One was installed before the other (can't remember which way round) and was disabled when the oither was installed, it's just still there and I guess that's what the script is picking up. Only one is actually in use.
I've no idea why, but monitor data is now arriving at the master server again. I've made no changes since the last time I looked at it and it wasn't working back then, so I've no idea why it's started working again.
