weird problems with server suddenly failing to start

[mrbrdo]

Hey,

I've just deployed my app with puma (switched from passenger). I'm using MRI 1.9.3. I'm having really weird issues:

• First I deployed to my staging, which is on the same server as production. This went fine and it worked great, including pumactl.
• Then I deployed to production but pumactl didn't want to work, also I couldn't start puma in daemonized mode
• I could start puma only without daemon mode and that worked fine
• Then I stopped puma, tried to start in daemon mode which failed again
• Now I tried to start puma in non-daemon mode but now it didn't work anymore (error below), even though I used the exact same command as before
• I tried to start the server via bundle exec rails s puma and even bundle exec rails s webrick, but I am getting this error now all the time
• I even restarted the whole server but it didn't help, I had to go back to passenger which works like before
• I cleared the sock files between my attempts

The error I get (I don't think it's as specific, it's probably something more general and pretty sure related to puma somehow):

`method_missing': undefined local variable or method `arel_table' for Doorkeeper::AccessGrant:Class (NameError)

Rails console works (and Doorkeeper::AccessGrant.arel_table works), but rails server does not, I get the above error all the time. Using Rails 4.
Just a wild guess could this be related to ActiveRecord connection pool maybe? Or some postgres settings?

[mrbrdo]

it was caused by newrelic, not related to puma