Linux - Newbie This 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! |
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
12-12-2009, 11:10 AM
|
#1
|
Member
Registered: Dec 2008
Posts: 59
Rep:
|
Linux Admin Tasks
Hello,
I am kinda new to linux, I have some scripting knowledge, etc, but I have been asked to preform some Administration tasks on our Linux (Redhat, CentOS, Fedora) servers.
I have some basic crons running that email me things such as disk usage and warn me if disk space gets to low, etc.
What I need to kinda know now is things like:
Load
Hardware Failures
Etc.
I guess the more advanced stuff! I have looked at "Logwatch" which I notice I can divert to an external address. I assume this would warn me failures and such?
Do you guys use any software for monitoring and such?
Or if you think there should be anything else I should be monitoring (No websites running on these servers they are purely database servers, with user numbers in excess of 800 on some servers.)
Would appriceate the ideas
Thanks 
Last edited by stuaz; 12-12-2009 at 11:11 AM.
|
|
|
12-12-2009, 12:28 PM
|
#2
|
LQ Veteran
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Mint
Posts: 17,809
|
You don't say exactly what you have been asked to do.....
Have you been put in charge of these servers? Is there a more senior/experienced person guiding you?
|
|
|
12-12-2009, 02:04 PM
|
#3
|
Senior Member
Registered: May 2004
Location: In the DC 'burbs
Distribution: Arch, Scientific Linux, Debian, Ubuntu
Posts: 4,290
|
You might look into Nagios or something similar for monitoring. Depending on what type of database server you're using, it might have its own monitoring tools.
|
|
|
12-12-2009, 02:10 PM
|
#4
|
Member
Registered: Dec 2008
Posts: 59
Original Poster
Rep:
|
Quote:
Originally Posted by pixellany
You don't say exactly what you have been asked to do.....
Have you been put in charge of these servers? Is there a more senior/experienced person guiding you?
|
yeah they are all under my control
|
|
|
12-12-2009, 02:12 PM
|
#5
|
Member
Registered: Dec 2008
Posts: 59
Original Poster
Rep:
|
Quote:
Originally Posted by btmiller
You might look into Nagios or something similar for monitoring. Depending on what type of database server you're using, it might have its own monitoring tools.
|
The database part is under someone elses control and management, mine is the email server, users, printers, hardware, etc
I already do basic checks manually, and I am trying to automate things. But also making sure I am checking things I should be.
Last edited by stuaz; 12-12-2009 at 02:16 PM.
|
|
|
12-12-2009, 06:54 PM
|
#6
|
LQ Guru
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
|
The first thing is to bullet proof outside access, as much as possible. The 2.6 kernel uses iptables to build networking packet filters. You should look at /etc/hosts.allow and /etc/hosts.deny to make sure access terminates with an ALL or NONE statement. There are man pages for these files. Disable all services that you don't need. Bullet proof ssh by not allowing root logins, or remote X sessions. Run snort to monitor network intrusuion, unless it's running on a firewall somewhere.
Get a spam filter, and train it. It doesn't take long. Make sure the ports for local services are blocked to the outside world. Configure syslog to log what you want. And configure one machine to gather all syslog data remotely. Splunk is good. Make sure the program files you don't need are deleted.
You can install bastille to harden the system. If you want realtime log monitoring, for say root logins, try w | grep 'root'. If there is any output, you've got a root login. If you want monitoring for syslog for a specific thing, sudo tail -f /var/log/syslog | grep 'eth0' | 'died' | 'root' | 'sudo' will monitor syslog for the strings listed.
|
|
|
12-12-2009, 06:55 PM
|
#7
|
LQ Guru
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
|
The first thing is to bullet proof outside access, as much as possible. The 2.6 kernel uses iptables to build networking packet filters. You should look at /etc/hosts.allow and /etc/hosts.deny to make sure access terminates with an ALL or NONE statement. There are man pages for these files. Disable all services that you don't need. Bullet proof ssh by not allowing root logins, or remote X sessions. Run snort to monitor network intrusuion, unless it's running on a firewall somewhere.
Get a spam filter, and train it. It doesn't take long. Make sure the ports for local services are blocked to the outside world. Configure syslog to log what you want. And configure one machine to gather all syslog data remotely. Splunk is good. Make sure the program files you don't need are deleted.
You can install bastille to harden the system. If you want realtime log monitoring, for say root logins, try w | grep 'root'. If there is any output, you've got a root login. If you want monitoring for syslog for a specific thing, sudo tail -f /var/log/syslog | grep 'eth0' | 'died' | 'root' | 'sudo' will monitor syslog for the strings listed.
|
|
|
All times are GMT -5. The time now is 11:26 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|