Closed (cannot reproduce)
Project:
Barracuda
Component:
Aegir Master Instance
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 Apr 2013 at 07:23 UTC
Updated:
7 Jun 2013 at 16:08 UTC
Jump to comment: Most recent file
Comments
Comment #1
omega8cc commentedPlease follow guidelines.
Comment #2
realityloop commentedComment #3
omega8cc commentedI can't reproduce that. Please enable debugging as explained in the guidelines and attach full console output on upgrade - or use the silent/logged mode, like
barracuda up-stable logand attach the log written in the/var/backups/reports/up/barracuda/DATE/directory.Comment #4
realityloop commentedre-running boa up-stable appears to have resolved the issue
Comment #5
realityloop commentedComment #6
omega8cc commentedBy the way, always check if there is no pid file left for some weird reason and remove it, if it exists once the upgrade is complete:
ls -la /var/run/boa_wait.pidls -ls /var/run/boa_run.pidComment #7
realityloop commentedThis has happened again after updating to BOA 2.0.8 on the same server
contents of /var/run:
I tried using the log directive but it didn't seem to work.
I can trigger the queue manually by using:
Comment #8
omega8cc commentedPlease read and follow #3 before re-opening this ticket again. Thanks.
Comment #9
realityloop commentedSo it seems I've found a problem with the silent log mode, none of the prompts get displayed to the user.
I assume there are flags so that the prompts get filled in automatically, could you please point them out?
Anyway after running the update this time it's working again, which is weird as I'd tried re-running it 3 times already.
Comment #10
realityloop commentedattached log due to it containing <code> tags
Comment #11
obrienmd commentedI'm running into something similar - quick Q: Should the aegir user (barracuda) have a crontab running hosting-dispatch? Mine is empty as well.
Comment #12
omega8cc commentedThanks.
No, the non-interactive mode doesn't cause any problems here, because we are running
hostmaster-migratewith flag-y, so it answers YES for you:It should of course and it does have the standard aegir cron set up in all servers we manage, mostly Debian Squeeze but also some Ubuntu with at least three versions and it never happened to us to have this cron entry missing:
Something must be non-standard on your server(s), if this happened to you, because normally Aegir will replace the crontab on upgrade, also in the non-interactive mode, as shown in your log.
Note that BOA never touched this cron entry in any way, it is Aegir what manages it, and there were no changes in the way it is managed.
I'm sorry, but I have to close this as 'cannot reproduce', because it always just 'works for me' (tm) :/
If you will find anything related to your systems which could cause such a weird issue, feel free to re-open, but there is nothing BOA specific here, since BOA simply uses Aegir own
hostmaster-migratetask to proceed with upgrades and never modifies the cron entry for the master instance.Comment #13
obrienmd commentedNo problem, thanks for the context :)
Comment #14
jimsmith commentedI'm having the same problem. I updated and now cannot run any tasks. Some tasks ran, but verification of Hostmaster did not, nor did anything after that.
I notice that Hostmaster shows it is locked. Could this be the reason why tasks in the queue after it are not running?
My log files: https://gist.github.com/startinggravity/5728904/96e192166258338084506b01...
Comment #15
jimsmith commentedA follow up question: can I safely delete the tasks that have not run and then run an unlock task on Hostmaster?
Comment #16
jimsmith commentedA follow up question: can I safely delete the tasks that have not run and then run an unlock task on Hostmaster?
Comment #17
omega8cc commentedThere can be some "running" task which blocks your queue, so you should find it and delete. Or enable drush debugging, run upgrade and provide all details in a separate issue for review.
This has nothing to do with locked by design hostmaster platforms. See #1306430: Platforms show a warning but seem to work?
That said, please open a separate ticket with all required details and provide more information if you still experience issues.