Linux: find thin server running on port 80 and kill it

rubythinubuntu-12.04

On my Linux server I ran:

sudo thin start -p 80 -d

Now I'd like to restart the sever. The trouble is, I can't seem to get the old process to kill it. I tried:

netstat -anp

But what I see on port 80 is this:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      -

So, it didn't give me a PID to kill…

I tried pgrep -l thin but that gave me nothing. Meanwhile pgrep -l ruby gives me like 6 processes running. I don't really understand why multiple ruby threads would be running, or which one I need to kill…

How do I kill / restart the thin daemon?

Best Answer

thin is a Ruby gem, so it only makes sense that the Ruby interpreter would be running it.

A typical invocation of thin would be:

bundle exec rails server thin -p $PORT -e $RACK_ENV

In the process list, from the ps command, this appears something like:

 6870 pts/3    Rl+    0:01 /usr/bin/ruby script/rails server thin -p 80 -e production

When using pgrep, by default it only matches against the command name (i.e. ruby). This won't match when the pattern you're searching for appears in the arguments. For this, you need to use the -f option as well:

pgrep -l -f thin

The return then appears like this:

6870 /usr/bin/ruby script/rails server thin -p 80 -e production

And voila, there is the process you're looking for.

Related Solutions

Running Thin behind Apache2

You'll be configuring Apache as a "reverse proxy" - that search term will point you to a wealth of information regarding the configuration, but here's an example that should get you most of the way to the deployment you're looking for.

If you'll be using a different hostname and different <VirtualHost>, then you can do something like this:

<VirtualHost *:80>
    ServerName sinatra.example.com
    # Any normal settings you use go here; access logs, ServerAdmin, etc

    # Replace the 9999 below with the port that thin is using, note that it can't
    # be the same as Apache's port.
    # This can also be a service running on adifferent computer if you
    # use another IP address instead of 127.0.0.1
    ProxyPass / http://127.0.0.1:9999/
    ProxyPassReverse / http://127.0.0.1:9999/
</VirtualHost>

An alternative configuration that may be of use to you would be to just make it a subdirectory of an existing <VirualHost>; you'd add a <Location> block to your existing config:

<Location /sinatra/>
    ProxyPass http://127.0.0.1:9999/
    ProxyPassReverse http://127.0.0.1:9999/
</Location>

Ubuntu – Setting up Thin, Bundler and Ubuntu

You could create binstubs. using these the init-script should be like any other. thin just needs --damonize as parameter if you do not specify it in your thin.yaml. With thin install thin generates an init-script for you

BUNDLE INSTALL --BINSTUBS

If you use the --binstubs flag in bundle install(1), Bundler will automatically create a directory (which defaults to app_root/bin) containing all of the executables available from gems in the bundle.

After using --binstubs, bin/rspec spec/my_spec.rb is identical to bundle exec rspec spec/my_spec.rb.

http://gembundler.com/man/bundle-exec.1.html

Based on these features this works for me:

bundle install --binstubs
./bin/thin install
/etc/init.d/thin start

Best Answer

Related Solutions

Running Thin behind Apache2

Ubuntu – Setting up Thin, Bundler and Ubuntu

Related Topic