Created attachment 551627 [details]
/var/log/aeolus-conductor/*log

Description of problem:

While re-building a vmware-vsphere image, my conductor service suddenly returned "503 - Service Temporarily Unavailable"

I'm unclear whether this is a bug in rubygem-actionpack or in aeolus-conductor

Version-Release number of selected component (if applicable):
 * rubygem-actionpack-3.0.10-1.el6.noarch
 * aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.src.rpm
 * aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.src.rpm
 * aeolus-configure-2.5.0-0.20120104154940git196b80d.el6.src.rpm
 * rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.src.rpm
 * rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.src.rpm


How reproducible:
 * I've only seen this 1 time

Steps to Reproduce:
1. Observed while a vmware image build was finishing
2. While refreshing the conductor web-interface, the conductor service stopped responding
  
Actual results:

  # service aeolus-conductor status
   dead but pid file exists

  # tail /var/log/aeolus-conductor/thin.log

Using gem require instead of bundler
>> Thin web server (v1.2.11 codename Bat-Shit Crazy)
>> Maximum connections set to 1024
>> Listening on 127.0.0.1:3000, CTRL+C to stop
/usr/lib/ruby/gems/1.8/gems/actionpack-3.0.10/lib/action_view/helpers/url_helper.rb:317: [BUG] rb_gc_mark(): unknown data type 0x20(0x3bcb59ced8) non object
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

Expected results:


Additional info:

 * Attaching /var/log/aeolus-conductor/*log as a tarball that contains ...
-rw-r--r-- aeolus/aeolus 414125 2012-01-09 12:50 var/log/aeolus-conductor/dbomatic.log
-rw-r--r-- aeolus/aeolus 5848151 2012-01-09 12:43 var/log/aeolus-conductor/rails.log
-rw-r--r-- aeolus/aeolus     784 2012-01-09 12:43 var/log/aeolus-conductor/thin.log