Re: Tomcat logging - Persistence of Logs

2005-11-02 Thread Ronald Klop

Move the file to a new name in your startup script.

On Mon Oct 31 12:59:07 CET 2005 Tomcat Users List users@tomcat.apache.org 
wrote:
I have a problem with log files. I have a customer who has Tomcat 5.0.28 
running on Windows 2003 Server. The main output is being logged to 
stdout.log in the tomcat/logs directory - this is the Windows equivalent 
of catalina.out on a linux/unix system.


The problem is that for good reasons the customer is stopping  
restarting Tomcat every night (at our recommendation). This is a new app 
and it's not entirely bug-free yet, so giving thjem a clean start every 
day is useful. The trouble is that this also recreates stdout.log, which 
is a pity as sometime we aren't being alerted to problems until the day 
after, by which time the relevant log has disappeared.


Does anyone know how to make the Windows stdout.log file persistent?

Tom Burke 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





RE: Tomcat logging - Persistence of Logs

2005-10-31 Thread Steve Kirk

The Logger under 5.0.x uses -MM-DD format in the filename, so this
would change each day, would that give you what you need? See FileLogger
under Standard Implementation at:
http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html

PS note that Logger is deprecated in 5.5.x

 -Original Message-
 From: Tom Burke [mailto:[EMAIL PROTECTED] 
 Sent: Monday 31 October 2005 11:59
 To: Tomcat Users List
 Subject: Tomcat logging - Persistence of Logs
 
 
 I have a problem with log files. I have a customer who has 
 Tomcat 5.0.28 
 running on Windows 2003 Server. The main output is being logged to 
 stdout.log in the tomcat/logs directory - this is the Windows 
 equivalent 
 of catalina.out on a linux/unix system.
 
 The problem is that for good reasons the customer is stopping  
 restarting Tomcat every night (at our recommendation). This 
 is a new app 
 and it's not entirely bug-free yet, so giving thjem a clean 
 start every 
 day is useful. The trouble is that this also recreates 
 stdout.log, which 
 is a pity as sometime we aren't being alerted to problems 
 until the day 
 after, by which time the relevant log has disappeared.
 
 Does anyone know how to make the Windows stdout.log file persistent?
 
 Tom Burke 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat logging - Persistence of Logs

2005-10-31 Thread Steve Kirk
in case it helps but you haven't already seen it, the verbosity of Logger
can be tweaked, see same page as in last reply.

Can I just check what you are saying: are you saying that the standard
output to the file which captures stdout is different on the 2 platforms,
even with out-of-the-box TC config?  This would be a surprise, I was under
the impression that TC was functionally identical on whatever platform (the
only difference really being the exact pathnames to files).  So I just had a
quick look at catalina.bat vs catalina.sh on 5.5.9 (my installed version)
and it appears that there could be a difference:  catalina.sh starts the
bootstrap class with the redirection ' $CATALINA_BASE/logs/catalina.out
21' appended, whereas the windows bat file does nothing like this; there
is no redirection at all that I can see, or even a mention of the logfile
name.  Maybe this explains what you're seeing - the gubbins that is output
to the DOS window when you start in DOS is perhaps included in the log file
instead when you run under linux?  This is only a guess, I have not had time
to check it out.

 -Original Message-
 From: Tom Burke [mailto:[EMAIL PROTECTED] 
 Sent: Monday 31 October 2005 16:21
 To: Tomcat Users List
 Subject: Re: Tomcat logging - Persistence of Logs
 
 
 Indeed, I have a daily log already but it doesn't seem to be 
 as verbose 
 as the stdout.log.
 
 I was just wondering if the default log - stdout.log in Windows, 
 catalina.out in linux - could be made to behave the same way 
 on the two 
 platforms. But it looks as if this is an OS-specific difference, as I 
 can't see any difference in the configuration files between the two 
 servers.
 
 Tom Burke
 
 
 - Original Message - 
 From: Steve Kirk [EMAIL PROTECTED]
 To: 'Tomcat Users List' users@tomcat.apache.org
 Sent: Monday, October 31, 2005 12:52 PM
 Subject: RE: Tomcat logging - Persistence of Logs
 
 
 
  The Logger under 5.0.x uses -MM-DD format in the filename, so 
  this
  would change each day, would that give you what you need? See 
  FileLogger
  under Standard Implementation at:
  http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html
 
  PS note that Logger is deprecated in 5.5.x
 
  -Original Message-
  From: Tom Burke [mailto:[EMAIL PROTECTED]
  Sent: Monday 31 October 2005 11:59
  To: Tomcat Users List
  Subject: Tomcat logging - Persistence of Logs
 
 
  I have a problem with log files. I have a customer who has
  Tomcat 5.0.28
  running on Windows 2003 Server. The main output is being logged to
  stdout.log in the tomcat/logs directory - this is the Windows
  equivalent
  of catalina.out on a linux/unix system.
 
  The problem is that for good reasons the customer is stopping 
  restarting Tomcat every night (at our recommendation). This
  is a new app
  and it's not entirely bug-free yet, so giving thjem a clean
  start every
  day is useful. The trouble is that this also recreates
  stdout.log, which
  is a pity as sometime we aren't being alerted to problems
  until the day
  after, by which time the relevant log has disappeared.
 
  Does anyone know how to make the Windows stdout.log file 
 persistent?
 
  Tom Burke
 
 
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]