Rebooting my Droplet Crashed Rails

Question

I needed to reboot my droplet to in order to add a new SSH key to access the console via my macbook terminal. It worked but it appears it has crashed rails.

In the nginx error log I see this

to unix:/tmp/unicorn.dropletname.sock failed (2: No such file or directory) while connecting to upstream,

What should I do for this?

Answer 1

bobbyiliev June 19, 2019

I believe that you should not place sockets intended for interprocess communication in /tmp.

Try changing the configuration file and point it to a folder different from the /tmp folder for the socket.

Hope that this helps.

Reply Report

swammy June 19, 2019

Hi bobbyilieve. Thanks for the response.

I actually am new to working on this project. I did nothing to any of the current files on the server. I simply hit the reboot droplet button on the control panel and now it cannot find the original socket.
Reply Report
- bobbyiliev June 19, 2019
  
  Hi Swammy,
  
  Rebooting the server would explain the problem. Every time you reboot the machine the /tmp folder is flushed and all files in there are lost. That’s why you need to change the location of your socket.
  
  Hope that this helps!
  
  Reply Report
  
  swammy June 19, 2019
  
  Thank you for enlightening me about that. We were unaware. Could you point me in the correct direction about what that Rails file was that was lost and how I should recreate it please?
  
  Reply Report
  
  bobbyiliev June 19, 2019
  
  No problem at all.
  
  Here’s a nice guide on how to configure your Redis socket:
  
  https://guides.wp-bullet.com/how-to-configure-redis-to-use-unix-socket-speed-boost/
  
  Hope that this helps!
  
  Reply Report
  
  bobbyiliev June 19, 2019
  
  Just out of interest, did you manage to get this working?
  
  Reply Report

Answer 2

swammy June 19, 2019

Hi bobbyilieve. Thanks for the response.

I actually am new to working on this project. I did nothing to any of the current files on the server. I simply hit the reboot droplet button on the control panel and now it cannot find the original socket.
Reply Report
- bobbyiliev June 19, 2019
  
  Hi Swammy,
  
  Rebooting the server would explain the problem. Every time you reboot the machine the /tmp folder is flushed and all files in there are lost. That’s why you need to change the location of your socket.
  
  Hope that this helps!
  
  Reply Report
  
  swammy June 19, 2019
  
  Thank you for enlightening me about that. We were unaware. Could you point me in the correct direction about what that Rails file was that was lost and how I should recreate it please?
  
  Reply Report
  
  bobbyiliev June 19, 2019
  
  No problem at all.
  
  Here’s a nice guide on how to configure your Redis socket:
  
  https://guides.wp-bullet.com/how-to-configure-redis-to-use-unix-socket-speed-boost/
  
  Hope that this helps!
  
  Reply Report
  
  bobbyiliev June 19, 2019
  
  Just out of interest, did you manage to get this working?
  
  Reply Report

Related

Question

Rebooting my Droplet Crashed Rails

Related

Leave a comment

Looking for something else?

Sign up for our newsletter

Related

Question

Rebooting my Droplet Crashed Rails

Related

Leave a comment

Related

question

Bundle install gets killed

question

Every 2-4 weeks I get (111: Connection refused) while connecting to upstream. Why?

question

Rails one-click app and Unicorn

question

What type of projects is ruby on rails 16.04 (one click install droplet) used for?

Looking for something else?