Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 11 ■ TRACKING DOWN BUGSThis outputs data (to the file specified in line 10 of the script) in the following form:Mar-19-00:30:02 0.40Mar-19-00:31:01 3.54Mar-19-00:32:01 2.68The best way to get an idea of what’s going on here is to plot it, which is where gnuplot comes in.gnuplot expects two space-delimited columns of input, which is why line 18 uses the format it does.Check man strftime for more details or for other format options to use (the script imports this POSIXmodule in Line 08). Here the usage is %b (short form of month), %d (date of month in digits), and %H:%M:%S(time in hours/minutes/seconds), separated by hyphens.Check whether you have gnuplot installed on your system, and install the gnuplot package if not.Now, here’s the gnuplot config file for this data, nfs-ping.conf:01 set terminal png size 1200,80002 set xdata time03 set timefmt "%b-%d-%H:%M:%S"04 set output "nfs-ping.png"05 set xrange ["Mar-25-00:00:00":"Mar-26-00:00:00"]06 set yrange [0:50]07 set grid08 set xlabel "Date\\nTime"09 set ylabel "Ping Response"10 set title "NFS server ping times"11 set key left box12 plot "nfs-ping-1.dat" using 1:2 index 0 title "ahost" with points■ Note In line 05, change the range to match whatever the dates of your own data are. This gives the start andend points of the x range.Line 01 sets the output as a PNG file and the size of the plot in pixels, and line 04 sets the name ofthe output file. Line 02 identifies this as a time plot, and line 03 gives the time format as it has beenrecorded in your data file; you can use man date to get more information about how to specify time data.In line 05, the specified time range must be in this format as well. Lines 08–10 set the labels for the axesand the main graph.Line 12 is the one that does most of the work. The input data file is specified first. using 1:2 meansthat columns 1 and 2 of the input data are used to create the plot. index 0 means that you use the firstdata set in the file. You can have multiple data sets in a single file, delimited by two blank lines betweeneach. Here’s an example:# data for NFS host 1col1 col2col1 col2228Download at WoweBook.Com
CHAPTER 11 ■ TRACKING DOWN BUGS# data for NFS host 2col1 col2col1 col2You could replace line 12 with the following and thereby plot data for both your NFS hosts on thesame plot:plot "nfs-ping-1.dat" using 1:2 index 0 title "nfs1" with points, \plot "nfs-ping-1.dat" using 1:2 index 1 title "nfs2" with pointsThis would be useful if you were having reports of problems with one host but not the other; youcould directly compare the data to help work out where unusual changes were occurring. points is thebest plotting option for this data; you can also try lines as an alternative or one of the many otheroptions (linespoints, dots, steps...).Now run the following:cat nfs-ping.conf | gnuplotand then take a look at the generated file, nfs-ping.png. You can use Firefox or an image viewer such asghostview or imagemagick.■ Note gnuplot is a very versatile program and capable of far more complex tasks than this! Check out infognuplot to access the full user manual, or check out http://www.gnuplot.info/.229Download 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:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44:
CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86:
CHAPTER 3 ■ MONITORING AND UPDATI
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
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 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
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:
C H A P T E R 7■ ■ ■Working w
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:
CHAPTER 8 ■ USING THE COMMAND LIN
Page 197 and 198: CHAPTER 8 ■ USING THE COMMAND LIN
Page 205 and 206: C H A P T E R 9■ ■ ■Working w
Page 207 and 208: CHAPTER 9 ■ WORKING WITH TEXT IN
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 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 245 and 246: CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247: CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 251 and 252: C H A P T E R 12■ ■ ■Managing
Page 253 and 254: CHAPTER 12 ■ MANAGING TIME AND PE
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?