ViolentCrimes Posted April 29, 2011 Share Posted April 29, 2011 Right now TCADMIN2 creates one sets of logs per starting date, separate console logs, separate logs for each daemon, spread out over several directories. it makes it a pain to deal with this beta, since every time something breaks I have to scour through a buttload of files just to find if it logged an error. Is it possible to set up a single error log? Link to comment Share on other sites More sharing options...
LFA Posted April 29, 2011 Share Posted April 29, 2011 The single error log is console.log. It gets reset after every monitor or service manager restart. Having everything in a single file would is confusing because you would not be able to tell if the error is coming from the monitor or from the service manager. Link to comment Share on other sites More sharing options...
ViolentCrimes Posted April 29, 2011 Author Share Posted April 29, 2011 The single error log is console.log. It gets reset after every monitor or service manager restart. Having everything in a single file would is confusing because you would not be able to tell if the error is coming from the monitor or from the service manager. Seems a non-issue, given how daemon.log, user.log, dmesg or any other system log deals with it. I guess I can combine it myself with some scripts. Link to comment Share on other sites More sharing options...
ECF Posted May 3, 2011 Share Posted May 3, 2011 Seems a non-issue, given how daemon.log, user.log, dmesg or any other system log deals with it. I guess I can combine it myself with some scripts. Do you have a copy of a log file that you can post or send us that you mentioned above? Link to comment Share on other sites More sharing options...
ViolentCrimes Posted May 10, 2011 Author Share Posted May 10, 2011 Do you have a copy of a log file that you can post or send us that you mentioned above? What do you mean? Like a copy from /var/log/daemon? Apr 18 14:56:13 banhammer mdadm[1160]: NewArray event detected on md device /dev/md0 Apr 18 14:56:13 banhammer mdadm[1160]: NewArray event detected on md device /dev/md1 Apr 18 14:56:14 banhammer acpid: starting up with netlink and the input layer Apr 18 14:56:14 banhammer acpid: 1 rule loaded Apr 18 14:56:14 banhammer acpid: waiting for events: event logging is off Apr 18 14:56:14 banhammer dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 Apr 18 14:56:14 banhammer dhclient: Copyright 2004-2010 Internet Systems Consortium. It solves the issue by listing service as a column. Right now I could just combine and sort logs with scripts after the fact, it's just a convenience to be able to make a live tail and grep. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now