Linux error

[arvin.royo]

Hello I'm new to this community but just wanted to ask, I currently using rocky linux and ubuntu and I work at a linux based company, can someone teach me about techniques i can use to read errors and how to fix them?

 

[Mike-BTU]

Hello I'm new to this community but just wanted to ask, I currently using rocky linux and ubuntu and I work at a linux based company, can someone teach me about techniques i can use to read errors and how to fix them?

Welcome to linux.org! This seems to me to be kind of a broad question; could you be more specific about what type of errors?

 

[kc1di]

Hello @arvin.royo
Welcome to the Linux.org forum, enjoy the journey!
That would depend a lot on what kind of error your talking about. system error? boot? program? there are log files for system errors and boot error on most distros. As for program/ application errors that often time depends on the app itself. Give us a little more to go on as to what your trying to do.
If your new to linux I would recommend you start here.

Home | Linux Journey

linuxjourney.com

 

[Brickwizard]

One way to learn is just read other people's problems on this and other sites, and the eventual fixes you will be surprised how much you can learn, also learn the use of apps like inxi [on Debian distros] and ls, on all distributions to help you trace problems, If you have a spare external drive [or 64 bit USB pen-drive] you could install a distribution to it, and boot it up when you see any instructions you want to try for yourself, then if it all goes base over apex, you only need to wipe and re-install.

Oh and welcome to the forums

 

[dos2unix]

You find errors in different ways for different things.

A couple of good places to start...

sudo dmesg | grep -Ei 'error|warn|fail|unsupported'

cd /var/log

Look at the file names. messages is kind of a generic file.

cat /var/log/messages

Is there a certain kind of problem you are having?

 

[CaffeineAddict]

teach me about techniques i can use to read errors and how to fix them?

Reading logs is 99% of what you need to diagnose a cause.

Master the following commands to read logs:

• dmesg
• who (/var/run/utmp)
• last (/var/log/wtmp)
• lastlog (/var/log/lastlog)
• lastb (/var/log/btmp)
• faillog (/var/log/faillog)
• logger
• utmpdump
• savelog
• lnav *
• logrotate
• journalctl

# Recommended
sudo apt install lnav