ERR_CONNECTION_REFUSED after reboot

30 views
Skip to first unread message

Brian Burton

unread,
Feb 13, 2016, 1:05:10 PM2/13/16
to Coronium IO
Chris,
I rebooted my server (it was acting up; sometimes not sending password refreshes) and I'm now getting an ERR_CONNECTION_REFUSED
I've tried refreshing my browser, connecting through a different ip, and used different devices, all with the same result.

I was able to use putty to connect with ssh so I started coronium with "sudo service coronium start" on the server. that worked (process 2150).
If i do "sudo service coronium reload" I get a "reload: Unknown Instance:"

Obviously, the server is up since I can ssh in, but coronium doesn't seem to be responding after the reboot.

my ip is 54.88.76.212

I have also reset the cache on my local system and applied the 500 error fix.
Any suggestions or ideas?

Thank you,
Brian

develephant

unread,
Feb 13, 2016, 4:10:53 PM2/13/16
to Coronium IO
Hi Brian,

Can you log in and run:

cat /home/coronium/logs/error.log

I'm hoping there should be some clues towards the end of that file. Let me know.

Cheers.

Brian Burton

unread,
Feb 13, 2016, 7:57:52 PM2/13/16
to Coronium IO
Sadly, the error.log is empty.

Brian Burton

unread,
Feb 14, 2016, 11:55:00 AM2/14/16
to Coronium IO
Quick update:
I wasn't able to get the coronium on the AWS instance up and running again.  
However, I was able to create a new instance and copy my mongo and script files over fairly quickly (less than an hour, and it was the first time I had done such a procedure).  
I will do a write-up of the entire transfer process for reference.

Suggested change to Coronium: For situations like this, it would be nice to be able to copy the Coronium-API key to the new instance.  It would save from having to republish the app.  
Thank you Chris! 
I appreciate your hard work on Coronium!
Brian

develephant

unread,
Feb 14, 2016, 6:57:35 PM2/14/16
to Coronium IO
Hi Brian,

First, my apologies for the issues. Without getting into the box itself, it's very hard to determine what could be causing the boot problem.

I'm glad you were able to transfer over info to a new instance, I would be very interested in seeing a short write up on that, in your copious amount of free time. :)

If you still know the existing API key, I might be able to help you transfer it, if you are interested in such a thing at this point.

Coronium 2 (in progress as we speak) will handle all of these situations better.

Cheers.
Reply all
Reply to author
Forward
0 new messages