Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

thin sockets not being written

#108

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)

thin.yaml
--- 
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: []

Reported by Matthew Ford · August 27th, 2009 @ 06:32 AM

State: invalid
Milestone: Future
Assigned to: macournoyer macournoyer

Activity

  1. macournoyer
    macournoyer
    • State changed from new to open

    Hi Matthew,

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

    August 27th, 2009 @ 10:17 AM

  2. Matthew Ford
    Matthew Ford

    start with:

      thin -C thin.yml start
    
    config.ru
    $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
    

    August 27th, 2009 @ 11:49 AM

  3. Matthew Ford
    Matthew Ford

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

    August 28th, 2009 @ 08:18 AM

  4. macournoyer
    macournoyer
    • State changed from open to invalid

    Aaaah cool, thx for the update!

    August 28th, 2009 @ 08:57 AM

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.