mongrel unicorn - Jan 2012 - Default Socket Location

I am collaborating on a Rails app with a very minimal unicorn config
(the socket dir is not specified)

I have booted up the app and created the necessary nginx server config
for it, but it does not seem to be finding the socket file (502 error)

Was just wondering where this file would be by default. Looking at
unicorn''s documentation I had expected it to be living in the /tmp
directory, but no such luck.

For good measure I also checked my app''s tmp/sockets folder but no dice
either

Since this app is a joint effort, specifying the socket location in
the config is not an option

Any idea?

On 01/20/2012 07:35 AM, Steven Garcia wrote:
> I am collaborating on a Rails app with a very minimal unicorn config
> (the socket dir is not specified)
>
> I have booted up the app and created the necessary nginx server config
> for it, but it does not seem to be finding the socket file (502 error)
>
> Was just wondering where this file would be by default. Looking at
> unicorn''s documentation I had expected it to be living in the /tmp
> directory, but no such luck.
>
> For good measure I also checked my app''s tmp/sockets folder but no
dice either
You could use `sudo lsof -p <unicorn-PID>` to see all the open files of 
a running unicorn.  This will show you shared objects, files, pipes, 
sockets, etc.
> Since this app is a joint effort, specifying the socket location in
> the config is not an option
Unicorn defaults to listening on TCP 0.0.0.0:8080 unless you tell it 
something else. It wont listen on a unix domain socket unless you 
configure it to.

You can use --listen with the unicorn startup script 
<http://unicorn.bogomips.org/unicorn_1.html> or the 
listen(address,options) method in your unicorn.conf 
<http://unicorn.bogomips.org/Unicorn/Configurator.html> to change this.

I don''t see how being a collaborator on a joint effort means you
can''t
change config, it just means you need to discuss and agree on the common 
configuration.