Results 1 to 4 of 4
We have a problem in that everytime we run a full back up the /var/log/messages file continuosly writes an error related to edirectory OID............. Subsequently the server will freeze and ...
- 02-05-2010 #1Just Joined!
- Join Date
- Nov 2009
- Location
- Georgia
- Posts
- 2
/var/log/messages logging
We have a problem in that everytime we run a full back up the /var/log/messages file continuosly writes an error related to edirectory OID............. Subsequently the server will freeze and we need to re-boot it. Novell is working on fixing this. (Had a fix at one time. Then we did some patching and it's back). In the meantime is there a way to change the level of logging to the /var/log/messages file. I'm thinking if we stop these messages, which mean nothing to anyone, the server will not freeze and I won't have to get up in the middle of the night to re-boot. Thanks ahead!
SLES 10sp2 OES2sp1
- 02-05-2010 #2
what logging mechanism are you using? syslog, syslog-ng?
- 02-05-2010 #3Just Joined!
- Join Date
- Nov 2009
- Location
- Georgia
- Posts
- 2
/etc/syslog-ng/syslog-ng.conf
- 02-05-2010 #4
so you're probably looks like this:
you just have to add more filters, and send them to another destinationCode:filter f_messages { not facility(news, mail) and not filter(f_iptables); }; ... destination messages { file("/var/log/messages"); }; log { source(src); filter(f_messages); destination(messages); };
Code:filter f_warn { level(warn, err, crit) and not filter(f_iptables); }; destination warnings { file("/var/log/warn-messages"); }; log { source(src); filter(f_warn); destination(warnings); };


Reply With Quote