Sponsored Content
Operating Systems Linux Do you still googling error messages? Post 302811261 by wakatana on Thursday 23rd of May 2013 11:40:49 AM
Old 05-23-2013
Do you still googling error messages?

I am intermediate Linux user which has basic knowledge of programming (c, perl, js ...) and some system troubleshooting (strace, SystemTap, lsof ...) and I am tired of Googling the messages which comes to Linux logs (/var/log/messages). I would like to improve my Linux kernel knowledge. Since Linux (and it's utilities like ssh etc.) is open source there are source codes available somewhere. So my question is: How can I troubleshoot/debug Linux problems on source code level? Is this even possible for intermediate Linux user? Where to begin and how to improve my programming skills and Linux kernel knowledge this way? Any best practices are welcomed.

Something like this:

  1. Copy your error message
  2. Paste it to online search engine for kernel source codes which can be found *
  3. Now you have file name where it appears under kernel structures
  4. See folders and files structure contained in kernel here *
  5. You can deduce from file location what is purpose of this file under kernel, or find further documentation here *
  6. Use tool * to find further files in kernel on which your incriminated file depends
  7. Now read their source until it will be clear
  8. Now you can see under which conditions this message happens (if else statements)
  9. You can use software like * to debug or write some kind of exception to see when this message appears.

Thank you.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

error messages

Dear Guys , AM using linux R.H 6.1 , I configured sendmail , when i update the alias file , i keep getting the following message : " Warning: .cf file is out of date: sendmail 8.11.6 supports version 9, .cf file is version 8 " so what does it mean , even though .cf file is not empty or... (1 Reply)
Discussion started by: tamemi
1 Replies

2. UNIX for Advanced & Expert Users

System Error messages

Hi Experts, I'm getting the following errors on /var/adm/messages file permanently. Dec 28 10:19:38 ioocsrv1 bsd-gw: open(dfA415ioocsrv3): File exists Dec 28 10:20:53 ioocsrv1 bsd-gw: open(dfA415ioocsrv3): File exists Dec 28 10:22:08 ioocsrv1 bsd-gw: open(dfA415ioocsrv3): File exists Dec... (1 Reply)
Discussion started by: nikk
1 Replies

3. UNIX for Dummies Questions & Answers

Error Messages

I have got script like this #!/bin/ksh -e function errtrap { es=$? print "ERROR line $1: Command exited with status $es." ... (1 Reply)
Discussion started by: akrathi
1 Replies

4. UNIX for Advanced & Expert Users

error messages in /var/adm/messages

Hi, I have a SunFire V490, Solaris 10 with XP1024 storage and HP Library. I have noticed the following error messages in the /var/adm/messages file. These errors are being generated constantly. Also commands like devfsadm, format cfgadm etc are getting hung. After a reboot it works fine for a... (1 Reply)
Discussion started by: nitinp82
1 Replies

5. Solaris

error messages

dear all i have the following error in messages in solaris server named devweb does any one can help me about the error the disk devapp connect by nfs to another server called devdb : Oct 10 09:55:41 devweb nfs: WARNING: NFSMAPID_DOMAIN does not match the server: devdb domain. Oct 10... (0 Replies)
Discussion started by: murad.jaber
0 Replies

6. Shell Programming and Scripting

ftp error messages!

Please see the below script- ftp $FTPREMOTESERVER prompt mput $DATAPATH/*.dat quit | ftp -in > FTPRETURNMSGLOGFILE # iam trying write the eroor messages inside a file when the ftp quits. Based on the above script te ftp is properly working but writing into the file wen ftp quits is nor... (1 Reply)
Discussion started by: dineshr85
1 Replies

7. UNIX for Dummies Questions & Answers

WHat do these error messages mean

New to UNIX. I saw these messages in my logs. What do they mean? What is a forward and reverse map? Unable to add forward map from Rogers.ga.com to 205.150.86.252: timed out unable to add reverse map from 241.86.150.205.in-addr.arpa. to FFXXB2RNHR71.NA.XOM.COM: timed out (2 Replies)
Discussion started by: mojoman
2 Replies

8. Shell Programming and Scripting

Appending error messages from log file next to the corresponding error record

Hi Everyone, I have an issue and trying to get a solution but was not succesful yet. Any help is greatly appreciated. I am using ksh to inoke sql loader to load data from txt file into two oracle tables based on the condition written in the control file. If an error occurs while loading into... (8 Replies)
Discussion started by: vpv0002
8 Replies

9. AIX

Error messages in syslog

Hi, Can you please look into the below errors from syslog in AIX? And let me know is this a issue? How can I avoid these errors with out affecting my LPAR. Detail Data SYSLOG MESSAGE <27>Aug 23 08:24:28 syslog: slp: 0660-084 The SA failed to decode and compute received message:... (0 Replies)
Discussion started by: System Admin 77
0 Replies

10. SuSE

Some error messages in var/log/messages

How are you? SUSE V10 and 11. In /var/log/messages I see these lines in some servers. I'd like to know what causes these errors and how to fix them. Thank you, error: PAM: Authentication failure for root from XXXXXXXX Did not receive identification string from XXXXXXX Invalid user suse-gm... (2 Replies)
Discussion started by: JDBA
2 Replies
SYSLOG(2)						     Linux Programmer's Manual							 SYSLOG(2)

NAME
syslog, klogctl - read and/or clear kernel message ring buffer; set console_loglevel SYNOPSIS
int syslog(int type, char *bufp, int len); /* No wrapper provided in glibc */ /* The glibc interface */ #include <sys/klog.h> int klogctl(int type, char *bufp, int len); DESCRIPTION
Note: Probably, you are looking for the C library function syslog(), which talks to syslogd(8); see syslog(3) for details. This page describes the kernel syslog() system call, which is used to control the kernel printk() buffer; the glibc wrapper function for the system call is called klogctl(). The kernel log buffer The kernel has a cyclic buffer of length LOG_BUF_LEN in which messages given as arguments to the kernel function printk() are stored (regardless of their log level). In early kernels, LOG_BUF_LEN had the value 4096; from kernel 1.3.54, it was 8192; from kernel 2.1.113, it was 16384; since kernel 2.4.23/2.6, the value is a kernel configuration option (CONFIG_LOG_BUF_SHIFT, default value dependent on the architecture). Since Linux 2.6.6, the size can be queried with command type 10 (see below). Commands The type argument determines the action taken by this function. The list below specifies the values for type. The symbolic names are defined in the kernel source, but are not exported to user space; you will either need to use the numbers, or define the names yourself. SYSLOG_ACTION_CLOSE (0) Close the log. Currently a NOP. SYSLOG_ACTION_OPEN (1) Open the log. Currently a NOP. SYSLOG_ACTION_READ (2) Read from the log. The call waits until the kernel log buffer is nonempty, and then reads at most len bytes into the buffer pointed to by bufp. The call returns the number of bytes read. Bytes read from the log disappear from the log buffer: the information can be read only once. This is the function executed by the kernel when a user program reads /proc/kmsg. SYSLOG_ACTION_READ_ALL (3) Read all messages remaining in the ring buffer, placing them in the buffer pointed to by bufp. The call reads the last len bytes from the log buffer (nondestructively), but will not read more than was written into the buffer since the last "clear ring buffer" command (see command 5 below)). The call returns the number of bytes read. SYSLOG_ACTION_READ_CLEAR (4) Read and clear all messages remaining in the ring buffer. The call does precisely the same as for a type of 3, but also executes the "clear ring buffer" command. SYSLOG_ACTION_CLEAR (5) The call executes just the "clear ring buffer" command. The bufp and len arguments are ignored. This command does not really clear the ring buffer. Rather, it sets a kernel bookkeeping variable that determines the results returned by commands 3 (SYSLOG_ACTION_READ_ALL) and 4 (SYSLOG_ACTION_READ_CLEAR). This command has no effect on commands 2 (SYS- LOG_ACTION_READ) and 9 (SYSLOG_ACTION_SIZE_UNREAD). SYSLOG_ACTION_CONSOLE_OFF (6) The command saves the current value of console_loglevel and then sets console_loglevel to minimum_console_loglevel, so that no mes- sages are printed to the console. Before Linux 2.6.32, the command simply sets console_loglevel to minimum_console_loglevel. See the discussion of /proc/sys/kernel/printk, below. The bufp and len arguments are ignored. SYSLOG_ACTION_CONSOLE_ON (7) If a previous SYSLOG_ACTION_CONSOLE_OFF command has been performed, this command restores console_loglevel to the value that was saved by that command. Before Linux 2.6.32, this command simply sets console_loglevel to default_console_loglevel. See the discus- sion of /proc/sys/kernel/printk, below. The bufp and len arguments are ignored. SYSLOG_ACTION_CONSOLE_LEVEL (8) The call sets console_loglevel to the value given in len, which must be an integer between 1 and 8 (inclusive). The kernel silently enforces a minimum value of minimum_console_loglevel for len. See the log level section for details. The bufp argument is ignored. SYSLOG_ACTION_SIZE_UNREAD (9) (since Linux 2.4.10) The call returns the number of bytes currently available to be read from the kernel log buffer via command 2 (SYSLOG_ACTION_READ). The bufp and len arguments are ignored. SYSLOG_ACTION_SIZE_BUFFER (10) (since Linux 2.6.6) This command returns the total size of the kernel log buffer. The bufp and len arguments are ignored. All commands except 3 and 10 require privilege. In Linux kernels before 2.6.37, command types 3 and 10 are allowed to unprivileged pro- cesses; since Linux 2.6.37, these commands are allowed to unprivileged processes only if /proc/sys/kernel/dmesg_restrict has the value 0. Before Linux 2.6.37, "privileged" means that the caller has the CAP_SYS_ADMIN capability. Since Linux 2.6.37, "privileged" means that the caller has either the CAP_SYS_ADMIN capability (now deprecated for this purpose) or the (new) CAP_SYSLOG capability. /proc/sys/kernel/printk /proc/sys/kernel/printk is a writable file containing four integer values that influence kernel printk() behavior when printing or logging error messages. The four values are: console_loglevel Only messages with a log level lower than this value will be printed to the console. The default value for this field is DEFAULT_CONSOLE_LOGLEVEL (7), but it is set to 4 if the kernel command line contains the word "quiet", 10 if the kernel command line contains the word "debug", and to 15 in case of a kernel fault (the 10 and 15 are just silly, and equivalent to 8). The value of console_loglevel can be set (to a value in the range 1-8) by a syslog() call with a type of 8. default_message_loglevel This value will be used as the log level for printk() messages that do not have an explicit level. Up to and including Linux 2.6.38, the hard-coded default value for this field was 4 (KERN_WARNING); since Linux 2.6.39, the default value is a defined by the kernel configuration option CONFIG_DEFAULT_MESSAGE_LOGLEVEL, which defaults to 4. minimum_console_loglevel The value in this field is the minimum value to which console_loglevel can be set. default_console_loglevel This is the default value for console_loglevel. The log level Every printk() message has its own log level. If the log level is not explicitly specified as part of the message, it defaults to default_message_loglevel. The conventional meaning of the log level is as follows: Kernel constant Level value Meaning KERN_EMERG 0 System is unusable KERN_ALERT 1 Action must be taken immediately KERN_CRIT 2 Critical conditions KERN_ERR 3 Error conditions KERN_WARNING 4 Warning conditions KERN_NOTICE 5 Normal but significant condition KERN_INFO 6 Informational KERN_DEBUG 7 Debug-level messages The kernel printk() routine will print a message on the console only if it has a log level less than the value of console_loglevel. RETURN VALUE
For type equal to 2, 3, or 4, a successful call to syslog() returns the number of bytes read. For type 9, syslog() returns the number of bytes currently available to be read on the kernel log buffer. For type 10, syslog() returns the total size of the kernel log buffer. For other values of type, 0 is returned on success. In case of error, -1 is returned, and errno is set to indicate the error. ERRORS
EINVAL Bad arguments (e.g., bad type; or for type 2, 3, or 4, buf is NULL, or len is less than zero; or for type 8, the level is outside the range 1 to 8). ENOSYS This syslog() system call is not available, because the kernel was compiled with the CONFIG_PRINTK kernel-configuration option dis- abled. EPERM An attempt was made to change console_loglevel or clear the kernel message ring buffer by a process without sufficient privilege (more precisely: without the CAP_SYS_ADMIN or CAP_SYSLOG capability). ERESTARTSYS System call was interrupted by a signal; nothing was read. (This can be seen only during a trace.) CONFORMING TO
This system call is Linux-specific and should not be used in programs intended to be portable. NOTES
From the very start, people noted that it is unfortunate that a system call and a library routine of the same name are entirely different animals. SEE ALSO
dmesg(1), syslog(3), capabilities(7) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 SYSLOG(2)
All times are GMT -4. The time now is 07:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy