#96 open
Andrew Case

Exit Return Status Value is Wrong

Reported by Andrew Case | March 16th, 2009 @ 05:02 PM | in 1.1

If I already have thin running on a port, and then I try to start it again on that port, thin exits with a successful return value instead of a failure return value.

$ /usr/bin/thin start --only 3000 -C /home/user/rails/config/thin.yml

Starting server on 0.0.0.0:3000 ...
** Ruby version is not up-to-date; loading cgi_multipart_eof_fix /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/daemonizing.rb:154:in remove_stale_pid_file': tmp/pids/thin.3000.pid already exists, seems like it's already running (process ID: 26487). Stop the process or delete tmp/pids/thin.3000.pid. (Thin::PidFileExist) from /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/daemonizing.rb:40:indaemonize' from /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/controllers/controller.rb:55:in start' from /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/runner.rb:173:insend' from /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/runner.rb:173:in run_command' from /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/runner.rb:139:inrun!' from /usr/lib64/ruby/gems/1.8/gems/thin-1.0.0/bin/thin:6 from /usr/bin/thin:19:in `load' from /usr/bin/thin:19 $ echo $? 0

Comments and changes to this ticket

  • macournoyer

    macournoyer March 16th, 2009 @ 08:54 PM

    • Milestone changed from Future to 1.1
    • State changed from “new” to “open”

    This is only on cluster mode, it works when controlling a single server in daemon mode.

    Need to pass the exit code to the parent process.

    thx for reporting Andrew.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

People watching this ticket

Pages