Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi guys. We have a variety of Linux servers, and I want to start getting my non-Linux folks into the habit of checking them every morning for like disk space, logs, at least the basics for now.
Does anyone have, or know a link to, a good basic/general daily Linux server checklist that says what to check and how? Or maybe we can make-up one in this thread, as i'm not having any luck finding one. Heck, maybe i'll even learn a few things from this
Thanks in advance for everyone chiming in, this could be fun.
I want to start getting my non-Linux folks into the habit of checking them every morning for like disk space, logs, at least the basics
This may not be the type of response you were looking for but unless these servers have been problematic for ages w/o chance of change or require fussing over for whatever else reasons or are too disparate or there's too few of them to warrant any investment (or if you just want to play BOFH-like games with employees ;-p) I would suggest using a "dashboard" instead. Trending allows you to respond before problems manifest themselves, overview allows you to pinpoint and respond to problems quickly and using a dashboard is efficient anyway since it tends to consolidate all sorts of nfo (agents, SNMP, logs, whatever else) and may require less effort and knowledge to use. If you disagree then at least agree you don't need to check things that Just Work (tm) and focus on anomalies. Process reports (Monit), disk space, user, syslog and daemon errors (Logwatch), network anomalies (Snort report) about everything can be mailed to a central mailbox, right?
That's the kind of response I was looking for, kinda. We're trying to evaluate different free monitoring software now to see what works, although we haven't found one yet that does everything. All the servers I was thinking of having them monitor are very old, and do have problems from time to time, so thought maybe a daily morning check of certain things they could do on each one might give us an idea before something bad happens. Ideally we're hoping we'll find some monitoring software that can email us scheduled reports of disk space/usage, deamon errors, etc, but really not sure what would best do it. Not so concerned with the network anomalies as of yet. The next couple we're going to try are Nagios and OpenNMS, see how those work. but was just thinking of hopefully putting together a basic, until-we-get-monitoring-setup morning routine going. plus it would help familiarize these people with linux a bit more, as they have no experience now really.
but yeah, I do agree, a dashboard and email alerting is the end game for us, just looking for a good intermediate (manual labor) step till we get that squared away.
Well, as far as manual labour goes, you could run 'top' to check cpu load, RAM, swap space.
Also 'df -h' for disk space.
You should probably also check some key logfiles, but which ones would depend on the services each system runs.
The generic/default logfile is /var/log/messages.
Depending on the exact Distro, you could check /var/log/secure.
It's free and it does a decent job displaying all kinds of stuff in neat graphics.
You can find a lot of templates on the internet for various devices
(such as Linux machines, Cisco Routers etc..)
Generally I'd go Nagios for alerts and Cacti for graphs.
Theoretically Nagios has graphs ( sort of) but I can't recommend them.
There are many alert and graphing tools, some of which purport to do both, but as with Prog Langs or Linux distros, there's no 'best'; its a subjective choice.
As for my prev comment, it'd be pretty easy to write a simple script to do those basic checks once a day (eg 4am) and email the results.
Obviously there's an extensive list of things you could check for, but I'd keep it pared down if I were you; you do want people to actually read them, right?
Actually, a good tool that does a lot for you already as far as log check+email goes it the logwatch tool.