Backup tries to also run -and fails- on secondary DNS server, without having Webservice enabled here.
What is happening and what is wrong with that?
I have a multi-server environment with 2 servers (one of them is the master) and a secondary DNS server that has only DB and DNS services installed and enabled on. The secondary DNS server is mirroring the "master" webserver where the primary DNS service runs. Since the 3.2 update the backup of the websites is reporting error on the secondary DNS server as well, despite the fact these websites are not residing on it but on the master webserver only. The errors stating that the backup was not possible to run for the sites. (since the path is not valid on the secondary DNS but only on the master web server.)
The backup on the server, holding the site takes place properly.
What should happen instead?
The backup shall only run on the webserver where the sites do reside and not on any mirrored server, especially if the service is not enabled on it at all.
Server OS: debian 9
Server OS version: stretch
ISPConfig version: 3.2
you can use
grep 'ISPC_APP_VERSION' /usr/local/ispconfig/server/lib/config.inc.php to get it from the command line
If it might be related to the problem
insert the output of `nginx -v` or `apachectl -v` here root@castor:~# apachectl -v Server version: Apache/2.4.25 (Debian) Server built: 2019-10-13T15:43:54 insert the output of `php -v` here root@castor:~# php -v PHP 7.0.33-34+0~20201018.42+debian9~1.gbp80c9be (cli) (built: Oct 18 2020 21:35:49) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.0.33-34+0~20201018.42+debian9~1.gbp80c9be, Copyright (c) 1999-2017, by Zend Technologies with Xdebug v2.8.1, Copyright (c) 2002-2019, by Derick Rethans ## proposed fix optional, of course. if you want to post code snippets, please use
or attach a code file. Best is to create a merge request of course. ## references if you know of related bugs or feature requests, please reference them by using `#<bugnumber>`, e. g. #123 if you have done a merge request already, please reference it by using `!<mergenumber>`, e. g. !12 if you know of a forum post on howtoforge.com that deals with this topic, just add the link to the forum topic here ## screenshots optional, of course. Add screenshots of the problem by clicking "Attach a file" on the bottom right. ## log entries
apache / nginx error.log lines (if related)