Page 1 of 1

DNS Clusters are broken in V16

Posted: Fri Jul 08, 2016 8:54 pm
by anthonyrossbach
The problems with V16 have caused 2 servers to need to be scraped, 3 others to need massive code changes and me manually updating the backend of VestaCP to make it work again, now here are 2 more servers in need of fixes that are not working at all. I have integrated everything into the CP API and now the problems are driving me crazy, the one for today?

DNS will not sync, and gives no errors that I can see.

I am wondering if anyone has found a reason for the clusters to not sync and if there is a fix, or a forceful way to sync that I can use instead, this causing huge problems and downtime.

Re: DNS Clusters are broken in V16

Posted: Sat Jul 16, 2016 8:52 am
by SS88
anthonyrossbach wrote:The problems with V16 have caused 2 servers to need to be scraped, 3 others to need massive code changes and me manually updating the backend of VestaCP to make it work again, now here are 2 more servers in need of fixes that are not working at all. I have integrated everything into the CP API and now the problems are driving me crazy, the one for today?

DNS will not sync, and gives no errors that I can see.

I am wondering if anyone has found a reason for the clusters to not sync and if there is a fix, or a forceful way to sync that I can use instead, this causing huge problems and downtime.
Mine are working?

This code executed will forcefully update clusters so if you execute it on server 1 - server 1 updates the cluster it's connected to. (this is run every 5 minutes in a Vesta cronjob)

Code: Select all

v-sync-dns-cluster
Anything in here? /var/log/vesta/error.log

Re: DNS Clusters are broken in V16

Posted: Fri Aug 26, 2016 12:25 pm
by skurudo