Conversation

Notices

1. Embed this notice
   Jerry Lerman (jerry@hear-me.social)'s status on Thursday, 16-May-2024 23:21:07 JST Jerry Lerman

   • BeAware :fediverse:

   @BeAware Ugh. Supposed to be "sudo journalctl -xe -u sharkey", not -ue. Sorry.

   • Embed this notice
     Anders Rytter Hansen (anders@sharkey.world)'s status on Thursday, 16-May-2024 22:01:50 JST Anders Rytter Hansen

     • BeAware :fediverse:

     @BeAware@social.beaware.live well no need to do the disable and enable commands. just stop and start or just poweroff without stopping and starting. it shouldn't break it though. have you checked the log if it shows any error?

   • Embed this notice
     Mr Snrub (snrub@diablocanyon1.com)'s status on Thursday, 16-May-2024 22:04:15 JST Mr Snrub

     in reply to

     • BeAware :fediverse:

     @BeAware@social.beaware.live my immediate guess might be that your database didn't start back after the restart.

   • Embed this notice
     Mr Snrub (snrub@diablocanyon1.com)'s status on Thursday, 16-May-2024 22:04:16 JST Mr Snrub

     • BeAware :fediverse:

     @BeAware@social.beaware.live Check your logs to see if sharkey is giving you any startup errors:
     
     
     https://www.howtogeek.com/499623/how-to-use-journalctl-to-read-linux-system-logs/

   • Embed this notice
     Anders Rytter Hansen (anders@sharkey.world)'s status on Thursday, 16-May-2024 22:04:41 JST Anders Rytter Hansen

     • BeAware :fediverse:

     @BeAware@social.beaware.live Alright. Good luck. Hope it helps 🤞

   • Embed this notice
     Mr Snrub (snrub@diablocanyon1.com)'s status on Thursday, 16-May-2024 22:11:45 JST Mr Snrub

     in reply to

     • BeAware :fediverse:

     @BeAware@social.beaware.live run the systemctl start in the second terminal

   • Embed this notice
     Mr Snrub (snrub@diablocanyon1.com)'s status on Thursday, 16-May-2024 22:11:46 JST Mr Snrub

     • BeAware :fediverse:

     @BeAware@social.beaware.live all good. The short easy commands:
     
     If you can open two terminals run this command in one of them to keep the logs running:
     
     sudo journalctl -f
     
     Then run your systemctl command to start sharkey. That should give you a hint as to what's going on

   • Embed this notice
     Mr Snrub (snrub@diablocanyon1.com)'s status on Thursday, 16-May-2024 22:12:16 JST Mr Snrub

     • BeAware :fediverse:

     @BeAware@social.beaware.live Sure. Just ping me if you have questions. Happy to help

   • Embed this notice
     Jerry Lerman (jerry@hear-me.social)'s status on Thursday, 16-May-2024 22:43:47 JST Jerry Lerman

     • BeAware :fediverse:

     @BeAware Oh no. You mean, "Did you turn if off, and then back on" is not the universal fix, after all?

     Did you do "systemctl status sharkey" to see if the service is running? If so, then it's probably a different issue. Also do a "journalctl -u sharkey" to check the service logs?

     I'm not a Linux expert, but these are two things I'd do to start off with.

   • Embed this notice
     Jerry Lerman (jerry@hear-me.social)'s status on Thursday, 16-May-2024 22:50:15 JST Jerry Lerman

     • BeAware :fediverse:

     @BeAware If you mean for journalctl, you can do a date range: journalctl --since "2024-05-15" --until "2024-05-16 09:00" or just jump to the end jouralctl -ue -u sharkey

     I believe

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Thursday, 16-May-2024 23:21:06 JST BeAware :fediverse:

     in reply to

     @Jerry Yeah, it's strange. There doesn't seem to be much wrong in the logs. I got a small error when trying to shut it down, but I don't think that caused it🤷♂️

     I'm at a complete loss for ideas at this point. Status on both NGINX and Sharkey seems "okay". I DID have some "warns" with Sharkey starting up which I'll also paste here, but I had 2 of those errors when I started it up originally and it was working fine and it's just the same errors doubled, and they say "ignored".

     First pic is the end of the Sharkey logs, where I "restarted" the instance and the second pic is the Sharkey status when I use the command.

   • Embed this notice
     Jerry Lerman (jerry@hear-me.social)'s status on Thursday, 16-May-2024 23:41:18 JST Jerry Lerman

     in reply to

     • BeAware :fediverse:

     @BeAware
     When I go to the website I get a 502, bad gateway. This means your webserver (nginx) is fine. But the application server (sharkey) is not.

     I'm guessing Sharkey didn't come up properly, or at all.

     Sharkey is a fork of Firefish? When I had Firefish, to start it after a reboot, I had to do this command:

     pm2 start "NODE_ENV=production pnpm run start" --name Firefish

     So, maybe the same for you, but the name might be Sharkey?

     Then I ran, one time, after it came up, to make this automatic when rebooting:

     pm2 save
     pm2 startup

     I have no idea if this is relevant. Just tossing it out.