I have a server hosting my website. It runs fine usually for about a week or so before it becomes unresponsive. When I try to view my website in a browser it does not load. When I try to ssh into it, it does not respond with anything just hangs (have to ctrl+c from ssh command). When I restart the server it starts working again just fine. I created a system utilization logging script and this is what it has (server restarted today 5/19/20 and became unresponsive 5/18/20):
Any particular reason why PopOS is the chosen server? You’d think Ubuntu Server Minimal or Debian Server Minimal would be best if you want ubuntu/debian based.
May 18 01:01:01 pop-os CRON[2570]: pam_unix(cron:session): session opened for user root by (uid=0)
May 18 01:01:01 pop-os CRON[2572]: (root) CMD (/home/<UserName>/Web/SysUtilLogger/runLogger.sh)
May 18 01:01:01 pop-os CRON[2570]: pam_unix(cron:session): session closed for user root
-- Reboot --
May 19 15:56:20 pop-os kernel: Linux version 5.3.0-7648-generic (buildd@lcy01-amd64-012)
Not sure how to check for kernel dumps. “pty”? I can’t leave a monitor connected. I was planning on connecting a monitor while it was unresponsive, but i forgot and i will have to wait a week before i will have a chance again. “Are you patching the system?” I ssh in and run apt every once in a while, if that is what you mean.
Not really, I just prefer pop. And at this point i’m not going to change it (would be too much of a pita). It is also not likely to be a pop specific issue.
Pop isn’t meant to be a server OS. I can’t speak to the stability of it’s customizations for server workloads. That said, it shouldn’t be happening, regardless.
Pseudo terminal. the thing you get from ctrl+alt+F3, etc…
Ah, that’s frustrating. Maybe leave an ssh session open watching dmesg?
just realized that i might actually be able to have it hooked up to a monitor. just need to find my dvi cable. my two monitors are currently connected to my desktop, but the dvi on my second monitor is open.
I’ve had systems with your symptoms and it was because of a root drive failure. It could be running along just fine for the most part until it hit a series of bad blocks. Then the drive would become so unresponsive that the entire system would fail. And of course it couldn’t log anything because the drive wasn’t talking.
Check the SMART data on all of your drives. See if you can get a remote network log going so logging doesn’t depend on the hard drive working.