#108 ✓invalid
Matthew Ford

thin sockets not being written

Reported by Matthew Ford | August 27th, 2009 @ 06:32 AM | in Future

When I start a thin (1.2.2 & 1.2.3) cluster with sockets, only /tmp/thin.0.sock is written the others are not. Not sure where to start to track this down, as thin.0.sock is there, just not 1-4.
using eventmachine (0.12.8)

pid: tmp/pids/thin.pid
rackup: config.ru
socket: /tmp/thin.sock
log: log/thin.log
timeout: 30
max_conns: 1024
chdir: /home/bot/tw
max_persistent_conns: 512
environment: production
servers: 5 
daemonize: true
require: []

Comments and changes to this ticket

  • macournoyer

    macournoyer August 27th, 2009 @ 10:17 AM

    • State changed from “new” to “open”

    Hi Matthew,

    How do you start thin? And what's the content of your config.ru file?

  • Matthew Ford

    Matthew Ford August 27th, 2009 @ 11:49 AM

    start with:

      thin -C thin.yml start
    $LOAD_PATH.unshift File.dirname(__FILE__) + '/sinatra/lib'
    require 'rubygems'
    require 'rack'
    require 'sinatra'
    require 'haml'
    require 'rufus/tokyo'
    require 'grackle'
    require 'twitter_oauth'
    require 'rack_hoptoad'
    require 'tw'
    use Rack::HoptoadNotifier, '0f5dfc30dd1693988e0db2224ab49123'
    run Tw
  • Matthew Ford

    Matthew Ford August 28th, 2009 @ 08:18 AM

    I think I tracked down the problem, in my sinatra app I had left the connection open to the tokyocabinet db.

  • macournoyer

    macournoyer August 28th, 2009 @ 08:57 AM

    • State changed from “open” to “invalid”

    Aaaah cool, thx for the update!

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