Client not properly initializing in Rails app

[segmentio]

Client not properly initializing in Rails app

[shanemcd]

Update: I've identified that the issue is caused by using unicorn-rails in development.

This code allows for an optional config file to be created at config/unicorn/#{environment}.rb.

I attempted to copy the after_fork code into this file, but does not resolve the issue. The thread is still dead.

[calvinfo]

@shanemcd any chance you can send me what your config/unicorn looks like?

using my super janky rails test project, I was able to see events being sent to segment.io: https://github.com/calvinfo/segmentio-rails-test/blob/master/config/unicorn/development.rb

we aren't really rails guys though, so there could be something obvious which I'm missing. thanks for the detailed report so far! :)

[shanemcd]

I am not quite sure what was going on yesterday, but here is what worked for me:

In an initializer:

Analytics = AnalyticsRuby

This was necessary because assigning the alias in the unicorn config was throwing uninitialized constant WhateverController::Analytics

I'm not sure how you got this to work, but the only thing I can think of is a difference between Rails 3 and Rails 4?

Moving on...

In config/unicorn/development.rb:

worker_processes 3
timeout 30
preload_app true

before_fork do |server, worker|
  if defined?(ActiveRecord::Base)
    ActiveRecord::Base.connection.disconnect!
    ::Rails.logger.info('Unicorn is about to fork workers, so disconnecting from the database in this process')
  end
  sleep 1
end

after_fork do |server, worker|
  if defined?(ActiveRecord::Base)
    ActiveRecord::Base.establish_connection
    ::Rails.logger.info('Unicorn worker process: connecting to the database')
  end

  if defined?(Analytics)
    Analytics.init({
      secret: Settings.segment_io.try(:secret_key),
      on_error: Proc.new { |status, msg| print msg }
    })
    ::Rails.logger.info('Initializing Segment.io Library')
  end
end