Hi,
I recently upgraded BOA installation from 2.0.3 to 2.0.8 on my VPS.
At first I had some problems with the whole upgrade-> MySQL access denied. After a search or two I found one case where they suggested that password had been manually changed. So I went and took password from .my.conf. and updated db tables.
Now the upgrade went trough and during the installation there was no errors or such.
However, after upgrading barracuda and octopus I got 404 on aegir front-end and 500 on site(octopus).
I reviewed nginx access log and it said 13: permission denied (when accessing aegir frontend).
Therefore I made some changes to file permission on var/aegir/host_master with reference to old installation(still in the folder).
*And now I can access Aegir frontend though update doesn't work.
What would be the correct file permissions in different data sources? Same as Drupal? Is there any script available that could take care of fixing file permissions?
I can also receive emails about available updates concerning my current installation.
Should I just try to install it one more time with the debug mode set to true?
*Edits and updates
- Browsing to VPS IP returns Chive login and so does chive.o1.dot.com
- All other subdomains except for aegir o1/front-end =404 do return nginx default under construction page.
- I reviewed MySQL database permissions and found out that there were only a few db permissions. Therefore I had to create couple new db permissions and the dot.com started to work. But still, hostmaster/aegir front-end doesn't open (404).
Comment | File | Size | Author |
---|---|---|---|
#8 | octopus-up-o1-130419-2212.txt | 131.48 KB | ETENTION |
#6 | octopus-up-o1-130417-2248.txt | 5.02 KB | ETENTION |
#4 | octopus-up-o1-130419-1453.txt | 1.96 KB | ETENTION |
#2 | LATEST barracuda-install-log.txt | 125.67 KB | ETENTION |
Comments
Comment #1
ETENTION CreditAttribution: ETENTION commentedFYI
I just tried to upgrade it again with debug mode set to yes and
barracuda up-stable log
command.And the result was
And I'm back to square one: hostmaster(aegir) -> 404 and site ->500.
Comment #2
ETENTION CreditAttribution: ETENTION commentedI found the latest barracuda log(attachment).
Comment #2.0
ETENTION CreditAttribution: ETENTION commentededits and updates
Comment #2.1
ETENTION CreditAttribution: ETENTION commentededits and updates
Comment #2.2
ETENTION CreditAttribution: ETENTION commentededits and updates
Comment #3
omega8cc CreditAttribution: omega8cc commentedThe system and Master Instance upgrade looks fine, no errors there.
Could you also enable Drush debugging in the Octopus config file
/root/.USER.octopus.cnf
and post the full debug output on another upgrade attempt withoctopus up-stable all log
- it will be written to/var/backups/reports/up/octopus/DATE/octopus-up-*
file.Comment #3.0
ETENTION CreditAttribution: ETENTION commentededits and updates
Comment #3.1
ETENTION CreditAttribution: ETENTION commentededits and updates, clean up
Comment #4
ETENTION CreditAttribution: ETENTION commentedLet's take one step backwards and review the log file related to first upgrade attempt on octopus.
Don't know how I didn't see this earlier.
Ok, thanks for reviewing.
I've now tried to upgrade octopus according to your guidance. Here's what happened:
What concerns me is that
instance control panel is available at o1.MY_HOSTNAME since it should be in o1.dot.com(which is a alias)?
AFAIK the installation loads the octopus conf that seems to include "wrong" domain and therefore maybe I could change it manually and try running the upgrade once more?
Comment #5
omega8cc CreditAttribution: omega8cc commentedAs I have requested already, please change
_DEBUG_MODE=NO
to_DEBUG_MODE=YES
and then run the upgrade and *attach* (don't post inline!) the full output.Also, please don't *edit* the issue or comments, because you are introducing a total chaos and confusion. All updates should be posted as *new* comments *only*.
Comment #6
ETENTION CreditAttribution: ETENTION commentedOk, sorry :)
I did try the debug mode and posted the "results" in the previous comment.
In short:
Upgrade got hanging and nothing happened.
Just a notice "waiting 5 sec" and hang(waited for 30min).
Went to see logfile which ended in: Do you want to proceed? (which is the first step in upgrade)
If I now try the upgrade again it will say that it is already up to date.
However, main point is the most recent "inline" log that you can find from attachments below :) It declares that there was errors in the first place.
Comment #7
omega8cc CreditAttribution: omega8cc commentedOK, could you please try the same with
_DEBUG_MODE=YES
? But there is something else, which looks much worse:/var/backups/OCTOPUS.sh.o1: line 589: read: read error: 0: Input/output error
I have never seen anything like that before. Something seems to be seriously broken or untypical on this system if such a simple and basic thing doesn't work.
What is the parent system there and what are its default locales? I mean the result of
locale
command.Comment #8
ETENTION CreditAttribution: ETENTION commentedOK, I tried following:
1. _DEBUG_MODE=YES
2. wget...
3. bash...
4.octopus up-stable all both log
5.OCTOPUS upgrade completed Bye
6. log file as attachment
Locale is fi_FI.utf-8.
Comment #9
omega8cc CreditAttribution: omega8cc commentedThis log shows successful auto-recovery from previous failed upgrade:
This time it worked just fine:
Comment #10
ETENTION CreditAttribution: ETENTION commentedThat's what it seems like.
At the moment
front end -> 404
site-> 500
Nginx error log declares "permission denied" when trying to access front end:
"/var/aegir/host_master/003/" (13: permission denied)
"/var/aegir/host_master/003/index.php" (13: permission denied)
"/var/aegir/host_master/003/sites/.../files/..." (13: permission denied)
...
If I try to change the permissions into e.g. rwx for aegir user and group in var/aegir/host_master/003/... it won't no longer give errors related to sites/.../files/.
For the index.php/front end part it turns into a error 500 but nginx doesn't show any erros in the log.
Obviously permission denied was solved and now something else gets in the way.
Comment #11
omega8cc CreditAttribution: omega8cc commentedCould you please run another
barracuda up-stable
upgrade after enabling drush debugging in /root/.barracuda.cnf and attach the output? I guess that it needs to fix the master instance as it fixed the satellite instance.Comment #12
omega8cc CreditAttribution: omega8cc commentedClosing due to a lack of response for a long time.
Comment #12.0
omega8cc CreditAttribution: omega8cc commentededits and updates