huginn: Unicorn Error

Hi there,

I have followed the installation instructions here to install on a Ubuntu based server over at DigitalOcean. I am new to nginx (familiar with apache) so a little lost.

I am getting the following error:

2016/04/19 23:15:19 [crit] 979#0: *1 connect() to unix:/home/huginn/huginn/tmp/sockets/unicorn.socket failed (2: No such file or directory) while connecting to upstream, client: 81.149.45.127, server: IPCOMMENTEDOUT, request: "GET / HTTP/1.1", upstream: "http://unix:/home/huginn/hug$

As noted in the installation instructions, I have CONFIRMED that my Procfile file is correct and that the unicorn config exists. I do not want to use Huginn on a domain, just the root server IP. Is this what is causing the issue?

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 15

Most upvoted comments

Hopefully it is, try removing the leading spaces in front of web and jobs.

dsander on Apr 20, 2016

You’re right!!! I ignore this step.Thanks for your help.Now I can do some interesting things.

zytomorrow on Dec 2, 2017

Hi @OliverGee,

the issue you are noticing can have multiple causes. First check that the unicorn process is running ps aux|grep unicorn. If it isn’t run sudo bundle exec rake production:export Next ensure the unicorn socket file exists sudo ls -al /home/huginn/huginn/tmp/sockets/unicorn.socket. If it doesn’t the unicorn configuration is not set up correctly. Now we need to check if the socket is accessible by the www-data user nginx is using sudo -u www-data ls -al /home/huginn/huginn/tmp/sockets/unicorn.socket. If that does not work the permissions for the huginn home directory are set too tightly.

When everything looks good please post the output of the other log files listed in the troubleshooting section

dsander on Apr 19, 2016