Vesta Control Panel - Forum

# v-add-remote-dns-host xx.xx.xx.xx admin XXXXXXXX
Error: another sync process already running
Error: xx.xx.xx.xx sync failed

problem is in latest update... I formated 2 machines ... install clean vestacp ... and not working =(

Same problem here. DNS Cluster was working perfectly before the update. Now you need to run dns-cluster.pipe in order for it to sync. v16 update has screwed all the hard work of the developers for the last few years.

I agree in many parts with you. However, why is it so difficult to release a v16.1 giving us all the bugfixes of the last month?

mestresan wrote:# v-add-remote-dns-host xx.xx.xx.xx admin XXXXXXXX
Error: another sync process already running
Error: xx.xx.xx.xx sync failed

problem is in latest update... I formated 2 machines ... install clean vestacp ... and not working =(

You are not alone - same problem

PS FREE DNS - "Free cheese is only in mousetrap" )))

just one question

for the vestacp dns cluster on say vps1 to be used as dns1

do i need to install webserver, ftp, mail, etc

may i skip all and just install the bind?

mestresan wrote:# v-add-remote-dns-host xx.xx.xx.xx admin XXXXXXXX
Error: another sync process already running
Error: xx.xx.xx.xx sync failed
problem is in latest update... I formated 2 machines ... install clean vestacp ... and not working =(

Bugs on tracker
https://bugs.vestacp.com/issues/339
https://bugs.vestacp.com/issues/323

It looks like the fix is coming out in version 0.9.8-17 which is not released yet. I can see the code changes in GitHub. The issue is present in a bunch of scripts such as those dealing with remote-dns. Here is a quick fix that worked for me in the current latest release 0.9.8-16.

Edit $VESTA/func/main.sh (which is sourced from other scripts) to add the following line at the top, in the "Internal Variables" section

bravo wrote: Edit $VESTA/func/main.sh (which is sourced from other scripts) to add the following line at the top, in the "Internal Variables" section

Code: Select all

SCRIPT=`basename "$0"`

Seems to be not correct. As far as I see, the problem was fixed in https://github.com/serghey-rodin/vesta/ ... f0db1c1e05

I would suggest to wait for the release of the new VestaCP Version.

Thanks for sharing the solutions. I was facing the same problem.

Regards,
Kate