Hallo today I updated the multiserver environment from buster to bullsey and also I updated to ispconfig 3.2.11 after them I became a lot of troubles. Most of them I could I solve by myself. One problem still exists 3 nameserver, ns01 is master and ns02, ns03 are mirror of master After upgrade the server all bind server refused any querry so about 1000 domains are not reachable I did a resync of the domains. Step by step domains became responsible. But still I´m not sure if the server I did a change at one domain but the change will not reflect to ns03 The counter for not populated changes stuck at the 2 open changes Jobque also displays the two open changes disabled crontab activeted debug level running /usr/local/ispconfig/server/server.sh no output happens. the script will not finish after pressing ^C and restarting server.sh WARNING - There is already a lockfile set, but no process running with this pid Checked that the php 7.4 is the default php version Rebooting server didn´t help Creating a new dns zone: this zone will not reflected to ns03 ns02 and ns01 are working Any ideas?
Have you followed this guide for the updates? https://www.howtoforge.com/update-the-ispconfig-perfect-server-from-debian-11-to-debian-12/
Thanks for replay I updated to Debian 11, not Debian 12 Because it´s a dedicated nameserver there is only limited software installed but basicaly I did this steps All servers can commuicate to each other
Double-check that you really enabled the debug log level for the affected nodes on master and that you ran server.sh on an affected node. It looks to me as if you set the email reporting level to debug but not the debug log level, as you would have gotten a different output if debug log level is enabled. You can find detailed instructions here: https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/ Enable debug log level, run server.sh on an affected node and post the full output you get from server.sh command.
Sorry for my long delay! 1st: you are right, a activated the eMail debug logging 2nd: it took a long time but step by step after starting the resync domains became available 3rd: one reason because of the long delay was a high utilization of the underlying virtualization host After about 4 hours sync was finished and everything works now. Thank you for your great support!!!
