Project

General

Profile

Actions

Defect #4880

closed

ERROR SignalException: SIGTERM

Added by Christian Gagneraud about 15 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-02-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

I wanted to stop redmine with a 'kill <PID>', and I got:
[2010-02-18 21:29:26] ERROR SignalException: SIGTERM
/usr/lib/ruby/1.8/webrick/server.rb:91:in `select'

Stopping it with CTRL-C works fine.

I'm running 0.9-stable freshly checked out.

Actions #1

Updated by Christian Gagneraud about 15 years ago

And actually redmine doesn't QUIT, a kill -INT did the job

Actions #2

Updated by Felix Schäfer about 15 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

I think this is more webrick (the "rails webserver") related than redmine related. In fact, googling for "SIGTERM webrick" lead me to this page http://oldwiki.rubyonrails.org/rails/pages/WEBrick which clearly states that webrick only stops on SIGINT, so this is expected behavior.

On a related note, depending on what you do with your redmine (more or less anything else that testing/developing) and what platform you're on, I'd strongly suggest using mongrel/thin/passenger (the later being imho the best, but you need apache or nginx for it, but I have it running nicely on my MacBook Pro with the OS X provided apache for development for example) to serve your redmine.

Actions

Also available in: Atom PDF