Debian Error Messages
Contents |
2014 in Commands, File system, LinuxI am a new Linux user. debian asix_rx_fixup bad header length I would like to know where are the log files debian error log located under Debian/Ubuntu or CentOS/RHEL/Fedora Linux server? How do I open or view log initramfs debian error files on Linux operating systems? Almost all logfiles are located under /var/log directory and its sub-directories on Linux. You can change to this linux error messages directory using the cd command. You need be the root user to view or access log files on Linux or Unix like operating systems. You can use the following commands to see the log files:less commandmore commandcat commandgrep commandtail commandzcat commandzgrep commandzmore commandHow do I view
Linux System Log Location
log files on Linux?Open the Terminal or login as root user using ssh command. Go to /var/log directory using the following cd command: # cd /var/log
To list files use the following ls command: # ls Sample outputs from RHEL 6.x server:anaconda.ifcfg.log boot.log-20111225 cron-20131110.gz maillog-20111218 messages-20131103.gz secure-20131027.gz spooler-20131117.gz up2date-20131117.gz anaconda.log btmp cron-20131117.gz maillog-20111225 messages-20131110.gz secure-20131103.gz squid uptrack.log anaconda.program.log btmp-20120101 cups maillog-20120101 messages-20131117.gz secure-20131110.gz swinstall.d uptrack.log.1 anaconda.storage.log btmp-20131101.gz dkms_autoinstaller maillog-20131027.gz mysqld.log secure-20131117.gz tallylog uptrack.log.2 anaconda.syslog collectl dmesg maillog-20131103.gz ntpstats setroubleshoot UcliEvt.log varnish anaconda.yum.log ConsoleKit dmesg.old maillog-20131110.gz prelink spooler up2date wtmp arcconfig.xml cron dracut.log maillog-20131117.gz rhsm spooler-20111211 up2date-20111211 yum.log atop cron-20111211 dracut.log-20120101 messages sa spooler-20111218 up2date-20111218 yum.log-20120101 audit cron-20111218 dracut.log-20130101.gz messages-20111211 secure spooler-20111225 up2date-20111225 yum.log-20130101.gz boot.log cron-20111225 httpd messages-20111218 secure-20111211 spooler-20120101 up2date-20120101 boot.log-20111204 cron-20120101 lastlog messages-20111225 secure-20111218 spooler-20131027.gz up2date-20131027.gz boot.log-20111211 cron-20131027.gz maillog messages-20120101 secure-20111225 spooler-20131103.gz up2date-20131103.gz boot.log-20111218 cron-20131103.gz maillog-20111211 messageknow where the log files are located, and what is contained in each and every log file.
Linux /var/log/messages
When your systems are running smoothly, take some time to learn linux log files explained and understand the content of various log files, which will help you when there is a crisis how to check logs in linux server and you have to look though the log files to identify the issue. /etc/rsyslog.conf controls what goes inside some of the log files. For example, following is the entry http://www.cyberciti.biz/faq/linux-log-files-location-and-how-do-i-view-logs-files/ in rsyslog.conf for /var/log/messages. $ grep "/var/log/messages" /etc/rsyslog.conf *.info;mail.none;authpriv.none;cron.none /var/log/messages In the above output, *.info indicates that all logs with type INFO will be logged. mail.none,authpriv.none,cron.none indicates that those error messages should not be logged into the /var/log/messages file. You can also specify *.none, which indicates that none of the log messages will be logged. The following are http://www.thegeekstuff.com/2011/08/linux-var-log-files the 20 different log files that are located under /var/log/ directory. Some of these log files are distribution specific. For example, you'll see dpkg.log on Debian based systems (for example, on Ubuntu). /var/log/messages - Contains global system messages, including the messages that are logged during system startup. There are several things that are logged in /var/log/messages including mail, cron, daemon, kern, auth, etc. /var/log/dmesg - Contains kernel ring buffer information. When the system boots up, it prints number of messages on the screen that displays information about the hardware devices that the kernel detects during boot process. These messages are available in kernel ring buffer and whenever the new message comes the old message gets overwritten. You can also view the content of this file using the dmesg command. /var/log/auth.log - Contains system authorization information, including user logins and authentication machinsm that were used. /var/log/boot.log - Contains information that are logged when the system boots /var/log/daemon.log - Contains information logged by the various background daemons that runs on the system
Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages ------------------------ Load Save SlideShow aptdaemonerror-messages Primary text (existing, proposed) Secondary text (existing, proposed) Buttons ERROR_NO_PACKAGE — The user has requested https://wiki.debian.org/aptdaemon/error-messages to install or remove a package which doesn't exist Package does not http://serverfault.com/questions/341919/how-to-find-error-messages-from-linux-init-d-rc-d-scripts exist Check the spelling of the package name, and that the appropriate repository is enabled. There’s no package named “X” in your current software sources. none “OK” ERROR_PACKAGE_UNAUTHENTICATED — The signing key of the repository owner ist not installed. This error can also occur if Requires installation of debian error untrusted packages The action would require the installation of packages from not authenticated sources. New title... New description ... ERROR_PACKAGE_DOWNLOAD_FAILED Failed to download package files Check your Internet connection. “X” could not be installed because it could not be downloaded. Check your Internet connection, or try again later. “Cancel” “Retry” ERROR_INCOMPLETE_INSTALL Previous installation hasn't been completed The installation could have failed debian error messages because of an error in the corresponding software package or it was cancelled in an unfriendly way. You have to repair this before you can install or remove any further software. Replace this error with automatically running dpkg--configure-a, and show a separate error if that fails. ERROR_PACKAGE_NOT_INSTALLED Package isn't installed There isn't any need for a removal. “X” can’t be removed because it isn’t installed. none “OK” ERROR_DAEMON_DIED Task cannot be monitored or controlled The connection to the daemon was lost. Most likely the background daemon crashed. New title... New description ... ERROR_CACHE_BROKEN The package system is broken Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f “X” can’t be installed because there is a serious problem with the software catalog. If repairing it doesn’t work, try removing third-party channels in Software Sources. “Software Sources…” “Cancel” “Repair” “X” can’t be removed because there is a serious problem with the software catalog. ERROR_PACKAGE_MANAGER_FAILED Package operation failed The installati
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to find error messages from Linux init.d/rc.d scripts? up vote 22 down vote favorite 5 In Linux, I've written some scripts to be executed during boot and played around with the various ways of installing them. For larger scripts I'll put in /etc/init.d and link the appropriate /etc/rc.d/rc?.d runlevels. For smaller scripts, I'll append to /etc/rc.d/rc.local. This process seems to be running smoothly. Now I've tweaked one of my scripts and it is failing. I'm having a heck of a time diagnosing it because I can't seem to capture the error output. I've checked /var/log/messages and poked around the rest of /var/log but can't find anything of use. Does anyone know: are these error messages automatically captured somewhere? if not, how can I capture the stdout/stderr from my init.d scripts? Thanks in advance. linux logging init.d rc.d share|improve this question edited Dec 17 '11 at 17:17 quanta 36.4k682160 asked Dec 17 '11 at 16:51 McKAMEY 3451313 1 serverfault.com/a/321926/59925 –quanta Dec 17 '11 at 17:19 @quanta that has some helpful tips, thanks. –McKAMEY Dec 17 '11 at 18:10 add a comment| 4 Answers 4 active oldest votes up vote 11 down vote accepted 1.: No - they go to STDOUT (if you use echo) or STDERR (if you use echo >&2). 2.: Your scripts have to write to logs and/or syslog on their own (your distribution might contain some init.d-functions that might help there - add your Distribution to your