troubleshooting /var/log syslog.con dmesg rout lpq kill

By -
Troubleshooting Problems in a Linux System

Types of Problems
- Hardware
- Operating System (Kernel)
- Application Software
- Configuration (change /etc files, change .dotfiles)
- User


Plan of Attack

1.Observe problem first hand
2.Formulate a guess as to cause
3.Attempt to fix
4.Go back to step 1 until fixed


Preventative Measures
- Buy supported hardware
- Stay away from untested software (Beta versions)
- Don't overclock your processor

#cd /var/log

boot.log - information about boot messages
mail.log - info about mail utility

To keep track what does each files hold:
#cd /etc/
#more syslog.conf

#man syslog.conf:
Here you can find priorities:
debug,info,notice,warning,warn,err,error,critical,alert,emerg(should be fixed imidiately),panic

#Don't log private authentication messages
*.info;mail.none;authpriv.none;cron.none
/var/log/messages

#Log all the mail messages in one place
mail.* /var/log/maillog

#Log cron stuff
cron.* /var/log/cron

#Everybody gets emergency messages
*.emerg *

* - in emergency mean that log can be appeared every where and
everybody on a system can see this message



You can log log files on a remote computer,
It's more secure way of keeping your log files


dmesg - kernel messages

dmesg | more -
shows OS, Proc MHZ,kernel info,caches,info about driver
Information about hardware


ifconfig eth0 - gives information about ethernet interface


route - shows ip routing table

lpq - shows print queue

top - displays information about proccesses that are running in your system. Every 5 sec reload
PRI - priority


ps - process status command
kill -9 PID


#cd /etc/init.d
#ls
Here stores all main processes



#/etc/init.d/sendmail restart


#lock files --- ????

#more xinetd.conf

If you want to change this config (EXAMPLE) xinetd.conf,
than you should restart /etc/xinetd.conf restart command

BUT SOMEBODY CAN USE xinetd SERVICE!!!


Better solution to do HUP!

#kill -l

#kill -1 1234 --- will hup (1) the process 1234


Troubleshooting
- Types of problems (software,etc)
- Log files (gather information,mail error, cron error)
- Tools (ifconfig, fsck) to determine what a root of the problem is
- Stop,Start,HUP

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log global mode http option httplog option dontlognull         contimeout 5000    
Read more

tomcat catalina coyote jasper cluster

By OK -
Tomcat Component are Catalina Coyote Jasper Cluster Catalina :  Catalina is the name of the servlet container of Apache Tomcat since version 4.x. Tomcat implements Sun Microsystems' specifications for servlet and JavaServer Pages (JSP), which are important Java-based Web technologies. Tomcat's servlet container was redesigned as Catalina in Tomcat version 4.x. other components of the Tomcat engine are: Tomcat Jasper which converts the code portions within JavaServer Pages into servlets and pass them to Catalina to process. Tomcat Coyote which is an HTTP connector based on HTTP/1.1 specifications that receives and transmits web requests to the Tomcat engine by listening to a TCP/IP port and returns requests back to the requesting client. Coyote :  The Coyote JK Connector element represents a Connector component that communicates with a web connector via the JK protocol (also known as the AJP protocol). This is used for cases where you wish to invisibly integr
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availability ssh   ports:   protocols:   masquera
Read more