Hide Forgot
Created attachment 563994 [details] aeolus-debug Description of problem: factory crashes after aeolus-thin reports /usr/share/aeolus-conductor/app/views/deployments/launch_time_params.html.haml:18: warning: Object#id will be deprecated; use Object#object_id Deployables are no longer visible. see screen shot Unclear what the recreate is at the moment.. I add what I think it *may* after getting the logs in the bug
[root@qeblade30 ~]# aeolus-check-services Checking mongod ... Success: mongod (pid 11877) is running... Checking iwhd ... Success: iwhd (pid 12312) is running... Checking postgresql ... Success: postmaster (pid 7614) is running... Checking httpd ... Success: httpd (pid 11817) is running... Checking qpidd ... Success: qpidd (pid 12209) is running... Checking deltacloud-core ... Success: deltacloud-core (pid 12104) is running... Checking libvirtd ... Success: libvirtd (pid 7036) is running... Checking aeolus-conductor ... Success: thin (pid 11972) is running... Checking conductor-dbomatic ... Success: dbomatic (pid 12051) is running... Checking imagefactory ... FAILURE: imagefactory dead but pid file exists Checking ntpd ... Success: ntpd (pid 4368) is running..
Created attachment 563995 [details] ss of deployables page
I had a look at the machine where this happened. It appears to have been a hard crash of the factory. Under these circumstances it's almost impossible to debug if the factory was launched in the normal way. I've added some additional debug options in this patch: https://github.com/aeolusproject/imagefactory/commit/14bef376aa1f940c2bd79a5c10df99bb34bf9084 If factory crashes we'll at least get stderr and stdout output. If python-faulthandler is installed we will also get tracebacks for all running threads. Wes, Shall we try to get this reproduced with the debug patch in place?
OK... I don't believe this is a blocker for beta, although I'm willing to concede it should block the release. I've set appropriate flags.
The patch mentioned above is now brewed as part of 1.0.0rc6.
Verified to the point of what Ian has added. Unable to reproduce the original report. Wes, have you been able to reproduce?
Will set this to verified until a reproducer is found.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html