Migrating VESTCP powered droplet in Digital Ocean
Posted: Mon Jul 11, 2016 3:30 pm
Hi,
I really love VESTACP, have been using it for the past couple of years.
All my droplets in digital ocean are powered by VESTCP in the back end. I take regular snapshots of each droplet everyday.
Due blacklisting of one of my droplet, i had to recreate fresh droplet from a snapshot. Everything went good but after restoration, APACHE and NGINX did not start.
When i checked VESTAP admin panel, i see that the IPs were old ones, so i ran a command, "/usr/local/vesta/bin/v-update-sys-ip" after which i am seeing new IPs in admin panel to be assigned to web applications.
However at this point, APACHE and NGINX did not start.
" * Restarting web server apache2
(99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.130.211.187:8080
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed. "
above is the error is see when i start APACHE from ssh.
can someone help me to fix this problem. I would like to know the steps involved to successfully run all VESTACP services after such IP change. Please HELP.
Thank you in advance.
I really love VESTACP, have been using it for the past couple of years.
All my droplets in digital ocean are powered by VESTCP in the back end. I take regular snapshots of each droplet everyday.
Due blacklisting of one of my droplet, i had to recreate fresh droplet from a snapshot. Everything went good but after restoration, APACHE and NGINX did not start.
When i checked VESTAP admin panel, i see that the IPs were old ones, so i ran a command, "/usr/local/vesta/bin/v-update-sys-ip" after which i am seeing new IPs in admin panel to be assigned to web applications.
However at this point, APACHE and NGINX did not start.
" * Restarting web server apache2
(99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.130.211.187:8080
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed. "
above is the error is see when i start APACHE from ssh.
can someone help me to fix this problem. I would like to know the steps involved to successfully run all VESTACP services after such IP change. Please HELP.
Thank you in advance.