3 ms·
My goto for initial troubleshooting a server is: uptime # uptime and CPU stress w # or better yet:last |head # who is/has been in netstat -tlpn # find server
by lazyant 9y ago
My goto for initial troubleshooting a server is:
uptime # uptime and CPU stress
w # or better yet:last |head # who is/has been in
netstat -tlpn # find server role
df -h # out of disk space?
grep kill /var/log/messages # out of memory?
ps auxf # what's running
htop # stressed? , look out for D (waiting on I/O typically) processes
history # what has changed recently
tail /var/log/application.log # anything interesting logged?
- fapjacks 9y agoI've wasted time not checking for inode availability, so I'd add a check for that to this list: df -hi
- JadeNB 9y ago> w # or better yet:last |head # who is/has been in The post argues that 'last' will not always give the desired information: > Obviously, I could also use 'last' to see who's been on the box recently, but this isn't the whole story. It's totally possible to "ssh root@box /path/to/command" and never start a login shell, which then leaves no trace in the lastlog, but then goes on to break something on the box. The syslog is how you'd find this.