Workling/daemons receiving SIGTERM?

108 views
Skip to first unread message

Brendon J. Wilson

unread,
Jan 18, 2010, 1:59:26 AM1/18/10
to ec2-on-rails-discuss
Jonathan Spooner related a problem in August on this list, and I
haven't seen a response that indicates the possible source of the
problem. I've encountered the same issue with workling - the workling
client receives a SIGTERM when it starts. The output in workling.log
is :

---
Mon Jan 18 06:07:11 +0000 2010
SIGTERM
["/usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/monitor.rb:
57:in `sleep'", "/usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/
daemons/monitor.rb:57:in `watch'", "/usr/lib/ruby/gems/1.8/gems/
daemons-1.0.10/lib/daemons/monitor.rb:44:in `loop'", "/usr/lib/ruby/
gems/1.8/gems/daemons-1.0.10/lib/daemons/monitor.rb:44:in `watch'", "/
usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/monitor.rb:84:in
`start_with_pidfile'", "/usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/
daemons/monitor.rb:64:in `fork'", "/usr/lib/ruby/gems/1.8/gems/
daemons-1.0.10/lib/daemons/monitor.rb:64:in `start_with_pidfile'", "/
usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/monitor.rb:
111:in `start'", "/usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/
daemons/application_group.rb:113:in `create_monitor'", "/usr/lib/ruby/
gems/1.8/gems/daemons-1.0.10/lib/daemons/application.rb:244:in
`start'", "/usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/
controller.rb:69:in `run'", "/usr/lib/ruby/gems/1.8/gems/
daemons-1.0.10/lib/daemons.rb:139:in `run'", "/usr/lib/ruby/gems/1.8/
gems/daemons-1.0.10/lib/daemons/cmdline.rb:105:in `call'", "/usr/lib/
ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/cmdline.rb:105:in
`catch_exceptions'", "/usr/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/
daemons.rb:138:in `run'", "/mnt/app/current/script/workling_client:
17"]
---

I'm assuming that this is a legitimate SIGTERM sent to the
workling_client, but where it's coming from is unclear.

Is this perhaps something being caused by the EC2 on Rails
configuration? Something monitoring processes and killing things off?
I've been looking at this for a day, and can't figure it out for the
life of me - not sure where to even begin debugging.

Reply all
Reply to author
Forward
0 new messages