Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 3 ■ MONITORING AND UPDATINGFigure 3-1. The Nagios tactical overview with only the basic configuration set upThe tactical overview shows an overview of hosts, services, and their states. For Nagios, hosts andservices can be in one of several states:• Pending means that it’s not done checking yet.• OK (shown in green) means that all is well.• There are several levels of not-OK states: yellow for Warning and red for Critical.You can set the detail of when these levels should be triggered in the config files. If you click aservice, you’ll be taken to a detailed page of information about that service (or host). There arenumerous other ways provided of looking at the information; click around a bit to try them.66Download at WoweBook.Com
CHAPTER 3 ■ MONITORING AND UPDATING■ Note To make the front page of the Nagios web interface more useful, you can set it to go straight to thetactical overview rather than to a home page. Edit /usr/share/nagios3/htdocs/index.html, and replacethis line:with this one:3-2. Adding Another Host to NagiosSo far, Nagios is monitoring the Nagios server machine itself and that one default gateway. Next, youneed to add a host, that is, another machine that you’re monitoring. The best way to do this is to create aconf.d/host-hostname.cfg file, named for the machine you want to monitor (here cepheus, so the file willbe conf.d/host-cepheus.cfg):define host{use generic-hosthost_name cepheusaddress 10.0.0.2}As you can see, this can be very basic; almost all the information is taken from the host template(see recipe 3-3 for more information about templates). Reload Nagios:/etc/init.d/nagios3 reloadIt will take maybe a minute to run the various checks before the data shows up on the web page, sobe patient.That’s your first very basic Nagios setup done. The server now checks itself and an external clientand will alert you to any problems.3-3. Using Templates in NagiosNagios provides templates as a way of saving yourself work. The previous recipe used one of these: take alook at the defaults defined for the localhost in conf.d/localhost_nagios2.cfg. The host definition andthe first service definition should look a bit like this:67Download at WoweBook.Com
Page 2:
Download at WoweBook.Com
Page 5 and 6:
Download at WoweBook.Comiii
Page 7 and 8:
Contents■About the Author .......
Page 9 and 10:
■ CONTENTS3-7. Writing a Nagios P
Page 11 and 12:
■ CONTENTS■Chapter 8: Using the
Page 13 and 14:
■ CONTENTSAbout the Author■Juli
Page 15 and 16:
■ CONTENTSAcknowledgmentsMany tha
Page 17 and 18:
■ CONTENTSIntroductionThis book i
Page 19 and 20:
■ INTRODUCTIONDownloading the Cod
Page 21 and 22:
C H A P T E R 1■ ■ ■Saving Yo
Page 23 and 24:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36: CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 41 and 42: C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 83 and 84: C H A P T E R 3■ ■ ■Monitorin
Page 85: CHAPTER 3 ■ MONITORING AND UPDATI
Page 89 and 90: CHAPTER 3 ■ MONITORING AND UPDATI
Page 115 and 116: C H A P T E R 4■ ■ ■Taking Ba
Page 117 and 118: CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 137 and 138:
CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 139 and 140:
C H A P T E R 5■ ■ ■Working w
Page 141 and 142:
CHAPTER 5 ■ WORKING WITH FILESYST
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
C H A P T E R 6■ ■ ■Securing
Page 157 and 158:
CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
CHAPTER 7 ■ WORKING WITH APACHEOn
Page 181 and 182:
CHAPTER 7 ■ WORKING WITH APACHEdi
Page 183 and 184:
CHAPTER 7 ■ WORKING WITH APACHE4.
Page 185 and 186:
CHAPTER 7 ■ WORKING WITH APACHE
Page 187 and 188:
CHAPTER 7 ■ WORKING WITH APACHEAl
Page 189 and 190:
CHAPTER 7 ■ WORKING WITH APACHE
Page 191 and 192:
C H A P T E R 8■ ■ ■Making Be
Page 193 and 194:
CHAPTER 8 ■ USING THE COMMAND LIN
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
CHAPTER 9 ■ WORKING WITH TEXT IN
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
C H A P T E R 10■ ■ ■Things G
Page 225 and 226:
CHAPTER 10 ■ THINGS GO IN, THINGS
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
C H A P T E R 11■ ■ ■Tracking
Page 235 and 236:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 237 and 238:
CHAPTER 11 ■ TRACKING DOWN BUGS01
Page 239 and 240:
CHAPTER 11 ■ TRACKING DOWN BUGS
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247 and 248:
CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 249 and 250:
CHAPTER 11 ■ TRACKING DOWN BUGS#
Page 251 and 252:
C H A P T E R 12■ ■ ■Managing
Page 253 and 254:
CHAPTER 12 ■ MANAGING TIME AND PE
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
APPENDIX■ ■ ■Perl TipsSee rec
Page 269 and 270:
APPENDIX ■ PERL TIPS• Date::Par
Page 271 and 272:
APPENDIX ■ PERL TIPSPerl Syntax N
Page 273 and 274:
■ ■ ■Index■Symbols$CDPATH,
Page 275 and 276:
■ INDEXenscript option (printing)
Page 277 and 278:
■ INDEX■NNagiosadding hosts to,
Page 279 and 280:
■ INDEXsyslogcentralized logging
Page 281 and 282:
Download at WoweBook.Com
show all

Linux System Administration Recipes A Problem-Solution Approach

Create successful ePaper yourself

Delete template?

Save as template?