1. View the process startup time
ps -eo pid,lstart,etime | grep pid
(lstart is the startup time, etime is how long it runs)
2. View the process memory distribution
pmap -x pid
3. The installed so library and version check the
ldconfig -p
version: objdump -V libxxx.so
4. Capture packets with ttl in a certain range
tcpdump -i eth0'ip[8] <= 20'
5. Generate the precompiled file
gcc -E test.c -o test.i
6, scp file transfer
remote to local:
scp [email protected]:/root/1.txt ./ (scp remote machine user name, ip, file path, local path)
Local to remote:
scp /home/space/music/1.mp3 [email protected]:/home/root/others/music/001.mp3 (scp local file, remote host username, ip, file path)
7. Check
ethtool -i eth0 for detailed information such as the driver used by the network card
Some thoughts on troubleshooting:
1) How to troubleshoot the three-layer loop under the condition of heavy traffic and without affecting the customer's business? Does it have or is necessary to implement an active three-layer loop alarm reporting mechanism;
2) How to troubleshoot the problem of large business delays in the production environment?
Increase the time stamp of the entry and exit points of the message (output the number of cpu ticks in each store);