We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
DNS Cluster sync
DNS Cluster sync
Hi @ all
As requested form XoXiLhJ0mn I opened an a seperated thread for my dns sync problem.
My infrastructur runs on 2 vmware hosts, there we have 8 VestaCP based VMs with Ubuntu 14.04 LTS (one with 12.04 LTS). 4 of them are running only VestaCP for DNS (so in that way "dns-only" Servers, not used for Webhostings), 4 other Servers are running for normal Webhostings and sync there DNS Records to the 4 "dns-only" server.
so in that way: web0[1-4].domain.tld syncs with integrated remote dns script to the other dns[1-4].domain.tld
After Upgrade to v16, the sync has stopped on my systems. So I've done already some analysis work as below.
Base: I created a new subdomain on my web01 Server, the file "dns-cluster.pipe" will be correctly "loaded" with the "v-add-remote-dns-record". Normaly, the command "v-update-sys-queue dns-cluster" will be executed every 5 minutes - so I've just waited a bit and monitored the syslog output for cron event.
After 15 Minutes (dns-cluster commands runs 3 times) I checked the system again, the "v-add-remote-dns-record" is stil in the "dns-cluster.pipe" file.
So i modified the file "v-update-sys-queue" file to get any error messages in the following line:
So that I see any output of the file and run it manually from the command line with the following error:
If I run the command "bash /usr/local/vesta/data/queue/dns-cluster.pipe" manually from the command line, it works and the command inside of "dns-cluster.pipe" will be executed correctly and the dns entry will be populated on all dns systems.
Is there somewhere else, who have this problem or maybe found already an solution?
Best Regards
Raphael
As requested form XoXiLhJ0mn I opened an a seperated thread for my dns sync problem.
My infrastructur runs on 2 vmware hosts, there we have 8 VestaCP based VMs with Ubuntu 14.04 LTS (one with 12.04 LTS). 4 of them are running only VestaCP for DNS (so in that way "dns-only" Servers, not used for Webhostings), 4 other Servers are running for normal Webhostings and sync there DNS Records to the 4 "dns-only" server.
so in that way: web0[1-4].domain.tld syncs with integrated remote dns script to the other dns[1-4].domain.tld
After Upgrade to v16, the sync has stopped on my systems. So I've done already some analysis work as below.
Base: I created a new subdomain on my web01 Server, the file "dns-cluster.pipe" will be correctly "loaded" with the "v-add-remote-dns-record". Normaly, the command "v-update-sys-queue dns-cluster" will be executed every 5 minutes - so I've just waited a bit and monitored the syslog output for cron event.
Code: Select all
Jul 18 10:50:01 web02 CRON[9911]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue dns-cluster)
So i modified the file "v-update-sys-queue" file to get any error messages in the following line:
Code: Select all
dns-cluster) bash $VESTA/data/queue/$queue.pipe ;;
# dns-cluster) bash $VESTA/data/queue/$queue.pipe > /dev/null 2>&1 ;;
Code: Select all
Error: another sync process already running
Is there somewhere else, who have this problem or maybe found already an solution?
Best Regards
Raphael