RE: Error Log watcher

2003-02-14 Thread Shapira, Yoav

Howdy,
What would you require from this error log watcher ?


Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Ben Ricker [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 9:58 AM
To: Tomcat Users List
Subject: Error Log watcher

I am wondering if anyone has found a good error log watcher for Tomcat?
Swatch does not work because it is made for syslog-type logs where an
error message occurs on one line. So, it views a java error as one
line,
which really does not help.

Anyone try any other programs?

Ben Ricker

--
Ben Ricker [EMAIL PROTECTED]
Wellinx.com


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




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


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




RE: Error Log watcher

2003-02-14 Thread Ben Ricker
On Fri, 2003-02-14 at 09:16, Shapira, Yoav wrote:
 Howdy,
 What would you require from this error log watcher ?

Good question! Sorry I did not include it. I am looking for something
similar to swatch, but can handle the multiple-lined errors. I would
want the program to have some sort of rules setting functionality
(preferably regex) and that allows actions based upon the specified
rules.

The actions would basically be alpha pages which would include the error
message in the page. Some throttling would be nice, so multiple errors
would not flood my pager.

Ben Ricker


 -Original Message-
 From: Ben Ricker [mailto:[EMAIL PROTECTED]]
 Sent: Friday, February 14, 2003 9:58 AM
 To: Tomcat Users List
 Subject: Error Log watcher
 
 I am wondering if anyone has found a good error log watcher for Tomcat?
 Swatch does not work because it is made for syslog-type logs where an
 error message occurs on one line. So, it views a java error as one
 line,
 which really does not help.
 
 Anyone try any other programs?
 
 Ben Ricker
 
 --
 Ben Ricker [EMAIL PROTECTED]
 Wellinx.com
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 This e-mail, including any attachments, is a confidential business communication, 
and may contain information that is confidential, proprietary and/or privileged.  
This e-mail is intended only for the individual(s) to whom it is addressed, and may 
not be saved, copied, printed, disclosed or used by anyone else.  If you are not 
the(an) intended recipient, please immediately delete this e-mail from your computer 
system and notify the sender.  Thank you.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
-- 
Ben Ricker [EMAIL PROTECTED]
Wellinx.com


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




RE: Error Log watcher

2003-02-14 Thread Shapira, Yoav

Howdy,

Good question! Sorry I did not include it. I am looking for something
similar to swatch, but can handle the multiple-lined errors. I would
want the program to have some sort of rules setting functionality
(preferably regex) and that allows actions based upon the specified
rules.

OK.  I actually went and looked at the Swatch page out of interest.
Cool tool.

Here's an approach that may work for you: use log4j.  Implement a
TriggeringEventEvaluator
(http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/spi/Triggerin
gEventEvaluator.html) to do the regex or whatever rules you want to
decide required a page from a log message.  The evaluator will get every
log message, including its complete stack trace and any details you want
to add.  You can use log4j's MDC
(http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/MDC.html) to
provide any details needed in order to decide whether the event merits a
message to your page or not.

Log4j comes with an SMTP appender that sends email and has all the logic
you want: throttling and arbitrary rules for even evaluation.  See
http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SMTPAppend
er.html for details.

Log4j doesn't come with a pager appender right now.  You could use a JMS
appender to send events (that pass the triggering event evaluator's
criteria) to a JMS server somewhere, as there are J2EE servers that can
handle paging.  Alternatively, you can write the pager appender yourself
and maybe even donate it to us as a log4j contribution ;)

This may seem like a lot, but it's really more work explaining the
process than doing it ;)

Yoav Shapira
Millennium ChemInformatics



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


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




RE: Error Log watcher

2003-02-14 Thread Ben Ricker
On Fri, 2003-02-14 at 09:57, Shapira, Yoav wrote:
 Howdy,
 
 OK.  I actually went and looked at the Swatch page out of interest.
 Cool tool.

Yes it is. I use it on my Apache error logs and to security checks on
the access_logs. Easy to setup to boot.

 Here's an approach that may work for you: use log4j.  Implement a
 TriggeringEventEvaluator
 (http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/spi/Triggerin
 gEventEvaluator.html) to do the regex or whatever rules you want to
 decide required a page from a log message.  The evaluator will get every
 log message, including its complete stack trace and any details you want
 to add.  You can use log4j's MDC
 (http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/MDC.html) to
 provide any details needed in order to decide whether the event merits a
 message to your page or not.
 
 Log4j comes with an SMTP appender that sends email and has all the logic
 you want: throttling and arbitrary rules for even evaluation.  See
 http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SMTPAppend
 er.html for details.

Some more information about myself: I am a system administrator. The
extent of my programmin g experience ends at Perl for System
Administrators. So I have a questions that may sound dumb:

Can you use these appenders as part of catching exceptions from within
the Code? That is, if you catch a certain exception that is going to be
logged, you set isTriggeringEvent on it and Log4J can then do what needs
to be done? 

 Log4j doesn't come with a pager appender right now.  You could use a JMS
 appender to send events (that pass the triggering event evaluator's
 criteria) to a JMS server somewhere, as there are J2EE servers that can
 handle paging.  Alternatively, you can write the pager appender yourself
 and maybe even donate it to us as a log4j contribution ;)  

Using the SMTPAppender to email it my pager would be plenty.

 This may seem like a lot, but it's really more work explaining the
 process than doing it ;)

If I understand it right, you are right. This would be easily added to
our existing exception handling.

Thanks for the info!

Ben Ricker

-- 
Ben Ricker [EMAIL PROTECTED]
Wellinx.com


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




RE: Error Log watcher

2003-02-14 Thread Shapira, Yoav
Howdy,

Can you use these appenders as part of catching exceptions from within
the Code? That is, if you catch a certain exception that is going to be
logged, you set isTriggeringEvent on it and Log4J can then do what
needs
to be done?

The way it works is like this:
- You define the appender (SMTP appender for emails)
- You define the class (a java class) of the TriggeringEventEvaluator
- The above two can be done in a configuration file, no coding needed
- You write the triggering event evaluator (have to write java for this)
- The application uses log4j to do its logging normally.  It doesn't
need to know about the triggering event evaluator at all.  Log4j will
automatically evaluate events sent to the mail appender and decide
whether to send emails or not.

Using the SMTPAppender to email it my pager would be plenty.

Then you're pretty much all set.  I'll even attach a simple string match
evaluator for use as an example.  (Yes, I'm bored today ;))

Yoav Shapira
Millennium ChemInformatics



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


public class StringMatchEvaluator
  implements TriggeringEventEvaluator {
  /**
   * Interface method.
   * Returns true if the given
   * event should trigger 
   * the appender.
   *
   * This implementation checks for
   * the presence of the String blah.
   * Add a setter for blah to customize
   * the match string.
   *
   * @param event The logging event
   * @return boolean
   */
   public boolean isTriggeringEvent(LoggingEvent event) {
 if(event == null) {
   return false;
 }

 String eventMessage = event.getMessage();
 if((eventMessage != null) 
(eventMessage.indexOf(blah)  -1)) {
   return true;
 }

 ThrowableInformation ti = event.ThrowableInformation();
 if(ti != null) {
   String[] stackTrace = ti.getThrowableStrRep();
   if(stackTrace != null) {
 for(int i = 0; i  stackTrace.length; i++) {
   if(stackTrace[i].indexOf(blah)  -1) {
 return true;
   }
 }
   }
 }

 return false;
   }
}

// End of class: StringMatchEvaluator.java
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Error-Log file ?

2001-08-20 Thread Rob S.

The Unix command line allows for stderr redirection.  I'm sure there's a
command-line HOWTO somewhere that dishes out the details since I've since
forgotten =/

- r

 -Original Message-
 From: Kenny Ma [mailto:[EMAIL PROTECTED]]
 Sent: Sunday, August 19, 2001 11:49 PM
 To: [EMAIL PROTECTED]
 Subject: Error-Log file ?


 I am using Tomcat 3.2.3/Redhat 7.1

 I have a servlet program, the program line 1 is System.err.println(TEST)

 when i run the servlet, the output goes into console

 I want the err.println output to a file , what can I do ?
 or how to config Tomcat ?

 ps. I checked /usr/local/tomcat/logs/
 It havent output to those files.

 /* Kenny Ma
[EMAIL PROTECTED] */






Re: Error-Log file ?

2001-08-19 Thread Dmitri Colebatch

On Mon, 20 Aug 2001, Kenny Ma wrote:
 I have a servlet program, the program line 1 is System.err.println(TEST)
you would be better off using log(TEST);

 when i run the servlet, the output goes into console
stderr will... are you running linux or windows?  afaik tomcat doesn't do
anything to redirect the stdout/stderr streams.

 I want the err.println output to a file , what can I do ?
 or how to config Tomcat ?
again... I'd advise using servlet.log at least, or preferably some logging
packages like log4j (http://jakarta.apache.org/log4j).

you might also want to change your server.xml so that tc_log goes to
logs/tomcat.log if you haven't already.

 ps. I checked /usr/local/tomcat/logs/
 It havent output to those files.
servlet.log will go there (o:

hth,
cheesr
dim

 
 /* Kenny Ma
[EMAIL PROTECTED] */
 
 




Re: Error Log

2001-08-14 Thread Richard Draucker

We never get any of the 'cool' viruses. :-(


On Monday 13 August 2001 06:54 pm, you wrote:
 At 01:46 PM 8/13/2001, Jeff wrote:
 Nope.
 
  Jeff,
  
  This code_red virus seems a Microsoft IIS issue.  Do you think this
   virus also could attack an apache server?

 Well, yes, it can attack an Apache server all it wants,
 the good thing is that this vulnerability doesn't exist
 on Apache. The worst that happens is that your poor Apache
 server has to continually attempt to service requests
 for a resource it doesn't have.

-- 
Richard Draucker [EMAIL PROTECTED]
Protected-Data.Com www.protected-data.com
Remote Data Support For Web Developers




RE: Error Log

2001-08-13 Thread Randy Paries

This is an error from a user that bookmarks your site with an IE5 browser.
The browser looks by default for favicon.ico in the root directory.

/usr/local/apache/htdocs/favicon.ico

-Original Message-
From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 2:56 PM
To: [EMAIL PROTECTED]
Subject: Error Log


Does any one has any idea what the following errors mean?

[Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
exist:  /usr/local/apache/htdocs/favicon.ico

[Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
exist: /usr/local/apache/htdocs/default.ida

[Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
exist: /usr/local/apache/htdocs/default.ida

They are displayed at error_log of the apache server.  We looked those
files up the directory displayed, but they do not exist.  What is happening
is that after an applicatin at the tomcat server works for 10-12 hours, the
web crushes.  Folks here started male pattern baldness tying to solve this
error.

Any help will be highly appreciated.




Re: Error Log

2001-08-13 Thread Barnabas Yohannes

Thank you Randy,
This is very true.  In fact, I bookmarked the site and it did it again.
What do you think is the solution?  Is there any where that I can download
the favicon.ico and put it to the root directory?  We looked the file up in
all the directories, but non of the files are loaded in anywhere in the
apache server.  We even tried to find it at the apache server CDs, but the
files are not there.


- Original Message -
From: Randy Paries [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 13, 2001 3:00 PM
Subject: RE: Error Log


 This is an error from a user that bookmarks your site with an IE5 browser.
 The browser looks by default for favicon.ico in the root directory.

 /usr/local/apache/htdocs/favicon.ico

 -Original Message-
 From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
 Sent: Monday, August 13, 2001 2:56 PM
 To: [EMAIL PROTECTED]
 Subject: Error Log


 Does any one has any idea what the following errors mean?

 [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
 exist:  /usr/local/apache/htdocs/favicon.ico

 [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
 exist: /usr/local/apache/htdocs/default.ida

 [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
 exist: /usr/local/apache/htdocs/default.ida

 They are displayed at error_log of the apache server.  We looked those
 files up the directory displayed, but they do not exist.  What is
happening
 is that after an applicatin at the tomcat server works for 10-12 hours,
the
 web crushes.  Folks here started male pattern baldness tying to solve this
 error.

 Any help will be highly appreciated.





RE: Error Log

2001-08-13 Thread Martin van den Bemt

Create an nice windows icon file yourself..

Mvgr,
martin

 -Original Message-
 From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
 Sent: Monday, August 13, 2001 10:36 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Error Log


 Thank you Randy,
 This is very true.  In fact, I bookmarked the site and it did it again.
 What do you think is the solution?  Is there any where that I can download
 the favicon.ico and put it to the root directory?  We looked the
 file up in
 all the directories, but non of the files are loaded in anywhere in the
 apache server.  We even tried to find it at the apache server CDs, but the
 files are not there.


 - Original Message -
 From: Randy Paries [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, August 13, 2001 3:00 PM
 Subject: RE: Error Log


  This is an error from a user that bookmarks your site with an
 IE5 browser.
  The browser looks by default for favicon.ico in the root directory.
 
  /usr/local/apache/htdocs/favicon.ico
 
  -Original Message-
  From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
  Sent: Monday, August 13, 2001 2:56 PM
  To: [EMAIL PROTECTED]
  Subject: Error Log
 
 
  Does any one has any idea what the following errors mean?
 
  [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
  exist:  /usr/local/apache/htdocs/favicon.ico
 
  [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
  exist: /usr/local/apache/htdocs/default.ida
 
  [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
  exist: /usr/local/apache/htdocs/default.ida
 
  They are displayed at error_log of the apache server.  We looked those
  files up the directory displayed, but they do not exist.  What is
 happening
  is that after an applicatin at the tomcat server works for 10-12 hours,
 the
  web crushes.  Folks here started male pattern baldness tying to
 solve this
  error.
 
  Any help will be highly appreciated.
 
 





Re: Error Log

2001-08-13 Thread Barnabas Yohannes

Jeff,

This code_red virus seems a Microsoft IIS issue.  Do you think this virus
also could attack an apache server?


- Original Message -
From: Jeff Rancier [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 13, 2001 3:06 PM
Subject: RE: Error Log


 You're server is receiving what appears to be the code_red virus stuff.
You
 must be connected to the outside? If so, I'd turn off, disconnect your
 connection, get the patch from Microsoft, follow the instructions.
Forget
 what I said, you're not running IIS.   But I think that's what they are
 though.

 -Original Message-
 From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
 Sent: Monday, August 13, 2001 3:56 PM
 To: [EMAIL PROTECTED]
 Subject: Error Log


 Does any one has any idea what the following errors mean?

 [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
 exist:  /usr/local/apache/htdocs/favicon.ico

 [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
 exist: /usr/local/apache/htdocs/default.ida

 [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
 exist: /usr/local/apache/htdocs/default.ida

 They are displayed at error_log of the apache server.  We looked those
 files up the directory displayed, but they do not exist.  What is
happening
 is that after an applicatin at the tomcat server works for 10-12 hours,
the
 web crushes.  Folks here started male pattern baldness tying to solve this
 error.

 Any help will be highly appreciated.





RE: Error Log

2001-08-13 Thread Jeff Rancier

Nope.

-Original Message-
From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 4:39 PM
To: [EMAIL PROTECTED]
Subject: Re: Error Log


Jeff,

This code_red virus seems a Microsoft IIS issue.  Do you think this virus
also could attack an apache server?


- Original Message -
From: Jeff Rancier [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 13, 2001 3:06 PM
Subject: RE: Error Log


 You're server is receiving what appears to be the code_red virus stuff.
You
 must be connected to the outside? If so, I'd turn off, disconnect your
 connection, get the patch from Microsoft, follow the instructions.
Forget
 what I said, you're not running IIS.   But I think that's what they are
 though.

 -Original Message-
 From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
 Sent: Monday, August 13, 2001 3:56 PM
 To: [EMAIL PROTECTED]
 Subject: Error Log


 Does any one has any idea what the following errors mean?

 [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
 exist:  /usr/local/apache/htdocs/favicon.ico

 [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
 exist: /usr/local/apache/htdocs/default.ida

 [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
 exist: /usr/local/apache/htdocs/default.ida

 They are displayed at error_log of the apache server.  We looked those
 files up the directory displayed, but they do not exist.  What is
happening
 is that after an applicatin at the tomcat server works for 10-12 hours,
the
 web crushes.  Folks here started male pattern baldness tying to solve this
 error.

 Any help will be highly appreciated.






Re: Error Log

2001-08-13 Thread Pier P. Fumagalli

Barnabas Yohannes at [EMAIL PROTECTED] wrote:

 Jeff,
 
 This code_red virus seems a Microsoft IIS issue.  Do you think this virus
 also could attack an apache server?

It can NOT attack any other web server BUT Microsoft IIS... Apache, Tomcat
and all the others are NOT AFFECTED by code red... EVEN if you're running
them on Windows...

Pier




RE: Error Log

2001-08-13 Thread Martin van den Bemt

This is a specific thing to IIS so don't worry. Request can be done although
to see if it is infected. Check the ip addresses and see if they come from a
source likely to be a normal visitor, if not mail them that there is
something strange going on ;-))

Mvgr,
Martin

 -Original Message-
 From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
 Sent: Monday, August 13, 2001 10:39 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Error Log


 Jeff,

 This code_red virus seems a Microsoft IIS issue.  Do you think
 this virus
 also could attack an apache server?


 - Original Message -
 From: Jeff Rancier [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, August 13, 2001 3:06 PM
 Subject: RE: Error Log


  You're server is receiving what appears to be the code_red virus stuff.
 You
  must be connected to the outside? If so, I'd turn off, disconnect your
  connection, get the patch from Microsoft, follow the instructions.
 Forget
  what I said, you're not running IIS.   But I think that's what they are
  though.
 
  -Original Message-
  From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
  Sent: Monday, August 13, 2001 3:56 PM
  To: [EMAIL PROTECTED]
  Subject: Error Log
 
 
  Does any one has any idea what the following errors mean?
 
  [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
  exist:  /usr/local/apache/htdocs/favicon.ico
 
  [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
  exist: /usr/local/apache/htdocs/default.ida
 
  [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
  exist: /usr/local/apache/htdocs/default.ida
 
  They are displayed at error_log of the apache server.  We looked those
  files up the directory displayed, but they do not exist.  What is
 happening
  is that after an applicatin at the tomcat server works for 10-12 hours,
 the
  web crushes.  Folks here started male pattern baldness tying to
 solve this
  error.
 
  Any help will be highly appreciated.
 
 





RE: Error Log

2001-08-13 Thread Dmitri Colebatch

favicon.ico is a 16x16 icon that IE looks for if a user has bookmarked a
page.  If its present, IE puts it next to the address in the address bar.

cheers
dim

On Mon, 13 Aug 2001, Jeff Rancier wrote:

 You're server is receiving what appears to be the code_red virus stuff.  You
 must be connected to the outside? If so, I'd turn off, disconnect your
 connection, get the patch from Microsoft, follow the instructions.   Forget
 what I said, you're not running IIS.   But I think that's what they are
 though.
 
 -Original Message-
 From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
 Sent: Monday, August 13, 2001 3:56 PM
 To: [EMAIL PROTECTED]
 Subject: Error Log
 
 
 Does any one has any idea what the following errors mean?
 
 [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
 exist:  /usr/local/apache/htdocs/favicon.ico
 
 [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
 exist: /usr/local/apache/htdocs/default.ida
 
 [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
 exist: /usr/local/apache/htdocs/default.ida
 
 They are displayed at error_log of the apache server.  We looked those
 files up the directory displayed, but they do not exist.  What is happening
 is that after an applicatin at the tomcat server works for 10-12 hours, the
 web crushes.  Folks here started male pattern baldness tying to solve this
 error.
 
 Any help will be highly appreciated.
 
 




RE: Error Log

2001-08-13 Thread Dmitri Colebatch

sorry - should read all my mail before replying (o:

On Tue, 14 Aug 2001, Dmitri Colebatch wrote:

 favicon.ico is a 16x16 icon that IE looks for if a user has bookmarked a
 page.  If its present, IE puts it next to the address in the address bar.
 
 cheers
 dim
 
 On Mon, 13 Aug 2001, Jeff Rancier wrote:
 
  You're server is receiving what appears to be the code_red virus stuff.  You
  must be connected to the outside? If so, I'd turn off, disconnect your
  connection, get the patch from Microsoft, follow the instructions.   Forget
  what I said, you're not running IIS.   But I think that's what they are
  though.
  
  -Original Message-
  From: Barnabas Yohannes [mailto:[EMAIL PROTECTED]]
  Sent: Monday, August 13, 2001 3:56 PM
  To: [EMAIL PROTECTED]
  Subject: Error Log
  
  
  Does any one has any idea what the following errors mean?
  
  [Mon Aug 13 12:22:53 2001] [error] [client 204.30.247.252] File does not
  exist:  /usr/local/apache/htdocs/favicon.ico
  
  [Mon Aug 13 12:30:47 2001] [error] [client 217.128.68.93] File does not
  exist: /usr/local/apache/htdocs/default.ida
  
  [Mon Aug 13 12:52:13 2001] [error] [client 212.68.231.10] File does not
  exist: /usr/local/apache/htdocs/default.ida
  
  They are displayed at error_log of the apache server.  We looked those
  files up the directory displayed, but they do not exist.  What is happening
  is that after an applicatin at the tomcat server works for 10-12 hours, the
  web crushes.  Folks here started male pattern baldness tying to solve this
  error.
  
  Any help will be highly appreciated.
  
  
 
 




RE: Error Log

2001-08-13 Thread Tim O'Neil

At 01:46 PM 8/13/2001, Jeff wrote:
Nope.


 Jeff,

 This code_red virus seems a Microsoft IIS issue.  Do you think this virus
 also could attack an apache server?

Well, yes, it can attack an Apache server all it wants,
the good thing is that this vulnerability doesn't exist
on Apache. The worst that happens is that your poor Apache
server has to continually attempt to service requests
for a resource it doesn't have.