Sorry, this seems to be a problem with the way DC is started.
We use daemontools to start DC and after I checked out the processes on the
server I found 3 'ruby init.rb' PIDs.
So then my question is how to run DC with daemontools correctly?
This is the run file:
export DC_DATA_DIR=/var/damagecontrol
exec ruby /usr/local/damagecontrol/init.rb >> ./LOG 2>&1
Are
,
On Monday 27 February 2006 09:50, Are Vattekar wrote:
> We upgraded from DC 0.3 to revision 118. There are a lot of nifty new
> features, but DC looks less stable. Every now and then DC chrash and needs
> to be restarted. This happens usually twice a day.
> Do you have any ideas?
>
> /usr/local/lib/ruby/1.8/logger.rb:510:in `write': Shifting failed. Bad file
> descriptor - $DC_DATA_DIR/log/scm_poller.log at Fri Feb 24 16:02:11 CET
> 2006 (Logger::ShiftingError)
> from /usr/local/lib/ruby/1.8/monitor.rb:229:in `synchronize'
> from /usr/local/lib/ruby/1.8/logger.rb:505:in `write'
> from /usr/local/lib/ruby/1.8/logger.rb:335:in `add'
> from /usr/local/lib/ruby/1.8/logger.rb:401:in `error'
> from ./lib/damagecontrol/process/base.rb:76:in `forever'
> from ./lib/damagecontrol/process/base.rb:69:in `forever'
> from ./lib/damagecontrol/process/base.rb:59:in `forever'
> from ./lib/damagecontrol/process/scm_poller.rb:10:in `run'
> from ./lib/damagecontrol/process/base.rb:26:in `execute'
> from ./lib/damagecontrol/process/base.rb:24:in `execute'
>
> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in
> `each_with_index'
> from ./lib/damagecontrol/process/base.rb:22:in `execute'
> from
> /usr/local/lib/ruby/gems/1.8/gems/cmdparse-2.0.0/lib/cmdparse.rb:412:in
> `parse'
> from init.rb:33
> ./vendor/rails/activerecord/lib/active_record/base.rb:620: [BUG]
> Segmentation fault
> ruby 1.8.3 (2005-09-21) [x86_64-linux]
>
> Are
