Closed (fixed)
Project:
Barracuda
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Mar 2012 at 13:13 UTC
Updated:
30 Mar 2012 at 06:40 UTC
I've tried a drush cc all and it completes fine, but I'm unable to access any urls at my hostmaster site, pre-existing sites are being served fine though, just hostmaster that is inaccesible.
Comments
Comment #1
omega8cc commentedPlease follow bug submission guidelines: http://drupal.org/node/add/project-issue/barracuda
Comment #2
realityloop commented/var/aegir/config/includes/barracuda_log.txt
/var/aegir/install.log
/root/.barracuda.cnf
Comment #3
omega8cc commentedHave you run the upgrade with debug option turned on? This always helps in debugging.
Please check if the hostmaster site platform root matches root in
/var/aegir/.drush/hostmaster.alias.drushrc.phpfile and corresponding vhost file.Comment #4
omega8cc commentedOf course, no:
_DEBUG_MODE=NOComment #5
realityloop commentedRe #3. Both appear to be pointing to the correct directory
Comment #6
realityloop commentedcontents of the host_master dir:
Comment #7
realityloop commentedI'm getting the following if I try and restart nginx manually:
Starting Nginx Server...:nginx: [emerg] bind() to *secondaryIP*:80 failed (99: Cannot assign requested address)
Comment #8
omega8cc commentedHow/when have you added secondary IP in the Aegir interface? I suppose before running the upgrade.
Are you sure you have enabled the *secondaryIP* in your server networking? The error suggests it is not available to bind to.
Comment #9
omega8cc commentedAlso, never use
service nginx restart, alwaysservice nginx reloadto avoid downtime.Comment #10
realityloop commentedRe #8 , yes the secondary IP was added to aegir interface before upgrading to head, I've reverified since adding the secondary IP to /etc/network/interfaces and restarting networking and the secondary has been added to vhost files.
I am getting a warning when restarting networking however:
and I am unable to ping the gateway for the secondary IP.
Comment #11
realityloop commentedThe problem was that linode needed a reboot after adding extra IP
Comment #12
omega8cc commentedJust a note for reference: maybe Linode has specific requirements, but normally it shouldn't be required to reboot the VM to add extra IP, and you should never restart networking, since you don't have a physical access to the machine. Instead, you should activate extra IP on the virtual interface with command like:
ifconfig eth0:1 up ex.t.ra.ip net.m.a.sk