Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFSSlave servers can’t modify the database, so it tries to redirect to the master and fails. If you now useldapsearch to look for your new entry, you will not find it.You can confirm this diagnosis by trying ldapsearch -H ldaps://masterldap.example.com to force abind to the master server.The next stage is to find out what’s causing the problem. Set the log level in /etc/ldap/slapd.conf to1, and then restart slapd and check the logs.These are two common problems:• An old slapd process that hasn’t been killed off properly. Check with ps and kill it ifnecessary.• An alock problem, which looks like this in the log:slapd[27069]: bdb_db_open: alock package is unstableslapd[27069]: backend_startup_one: bi_db_open failed! (-1)To resolve this, stop the server, delete the old alock file, and restart the server:/etc/init.d/slapd stoprm /var/lib/ldap/alock/etc/init.d/slapd startslapd may take a little while to recover the database after this and may also needto be restarted again. It’s probably wise to run a database dump before doing this.Again, this is something that you should be doing regularly anyway.Remember to return the log level to normal afterward, or the server will be very slow.If slurpd isn’t working properly, stop slapd, check the output of ps -A for old slapd processes andkill them if necessary, and then restart slapd. Check ps -A again to confirm that slapd is running.If the slave server is missing some entries (for example, if entries were added to the main databasethat relied on new schemas that weren’t available on the slave, which means that the slave will ignorethe changes):1. Stop slapd on the slave.2. On the master server, run the following:/usr/sbin/slapcat -l backupdb.ldif3. Copy backupdb.ldif onto the slave server.4. slapcat -c -l backupdb.ldif on the slave. Ignore any errors regardingduplicate entries.5. Restart slapd on the slave server.When you are troubleshooting, bear in mind that the replog file is expected to be empty, becauseslurpd truncates it immediately on read. In other words, if you see an empty replog, this is not on its ownan indication of or a source of any problems! However, the truncation happens whether a full successfulreplication has been completed, because the file is truncated immediately on read. If you have aproblem with replication, you’ll usually lose the replication data from the replog file, though the correctdata will still be in the master database. This means that when you do get replication working again, thenew data will never be transferred. To resolve this problem, use the method mentioned previously.46Download at WoweBook.Com
CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFS2-9. Setting Up Kerberos ReplicationJust as with LDAP, it’s a good idea to configure a second Kerberos server for backup purposes. WithKerberos, more than one server can act as a KDC and respond to auth requests, but only one canmanage changes to the database (the admin server).First of all, configure your second server as a Kerberos client (see recipes 2-1 and 2-2). Next, installkrb5-kdc and libkrb5-dev (not admin server).Edit /etc/krb.conf to include the following in the [realms] section under the relevant realm:kdc = krb_slave.example.comAlso add a logging section:[logging]kdc = FILE:/var/log/kerberos/krb5kdc.logdefault = FILE:/var/log/kerberos/krb5lib.logEdit /etc/krb5kdc/kpropd.acl to include names of both master and slave servers:host/kerberos.example.com@EXAMPLE.COMhost/krb_slave.example.com@EXAMPLE.COMExtract the host keys to the appropriate servers:• On the slave server:klist -k /etc/krb5.keytab• Ensure that it includes an entry for host/krb5_slave.example.com. If it’s missing,still from the slave server, run the following:kadmin -p krbadm• Check that there is a host/krb5_slave.example.com principal present in thedatabase. If not, run this:kadmin: addprinc -randkey host/krb5_slave.example.com• Extract the slave server’s key to the keytab:kadmin: ktadd host/krb5_slave.example.com• On the master server:klist -k /etc/krb5.keytab• Check that there is an entry for host/kerberos.example.com, and if not, create it asshown earlier.Next, you need to set up kpropd to run on the slave server. This can be done via inetd byuncommenting the following line in /etc/inetd.conf and then restarting inetd:krb5_prop stream tcp nowait root /usr/sbin/kpropd kpropd47Download 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 41 and 42: C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 65: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 83 and 84: C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86: 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 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:
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?