Re: Help Needed for Root cause - ApacheTomcat services stopped

2022-05-13 Thread Christopher Schultz

Sahil,

On 5/11/22 14:56, Verma, Sahil wrote:

Yes, we are using both Apache & Tomcat environment.

Apache - 2.4.25 version
Tomcat - 8.5.5 version


If this version number is correct, you should *seriously* consider 
upgrading to the latest Tomcat 8.5.x release. That release is more than 
5 years old and contains published security vulnerabilities.



You are correct, we got this error in Apache webserver logs. We are
attaching both Apache httpd (error.log) and Tomcat (Catalina.out) logs

Please let us know if any other information required.


Are you sure you actually have a problem? Or is the only problem that 
you are seeing this message in your log files?


For example, are you observing any decrease in availability or 
performance when you see these messages appear in the logs?


-chris


-Original Message-
From: Mark Thomas 
Sent: Wednesday, May 11, 2022 11:39 PM
To: users@tomcat.apache.org
Subject: Re: Help Needed for Root cause - ApacheTomcat services stopped

That is an Apache Web Server (httpd) log message, not an Apache Tomcat log 
message. Are you sure you are using Apache Tomcat?

Mark


On 11/05/2022 19:01, Verma, Sahil wrote:

Hi Team,



In our production environment, ApacheTomcat services went down. We
have checked the logs and found below error -



[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
140464737793792] AH00484: server reached MaxRequestWorkers setting,
consider raising the MaxRequestWorkers setting



Please help to find the root cause of the issue why services got stopped. 
Kindly let us know if any other information required.

Apache version - 2.2
OS - Linux


Thanks,
Sahil

DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
600113. CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of 
DXC Technology Company or one of its affiliates. It is intended exclusively for 
the addressee. The substance of this message, along with any attachments, may 
contain proprietary, confidential or privileged information or information that 
is otherwise legally exempt from disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended recipient 
of this message, you are not authorized to read, print, retain, copy or 
disseminate any part of this message. If you have received this message in 
error, please destroy and delete all copies and notify the sender by return 
e-mail. Regardless of content, this e-mail shall not operate to bind DXC 
Technology Company or any of its affiliates to any order or other contract 
unless pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



RE: Help Needed for Root cause - ApacheTomcat services stopped

2022-05-13 Thread Verma, Sahil
Hi Thomas,

Thank you very much for the valuable information. It will surely help us to 
find the root cause of the issue. We are monitoring our environment as per your 
suggestions.

Regards,
Sahil

-Original Message-
From: Thomas Hoffmann (Speed4Trade GmbH) 

Sent: Thursday, May 12, 2022 12:01 PM
To: Tomcat Users List 
Subject: AW: Help Needed for Root cause - ApacheTomcat services stopped

Hello Sahil,

> -Ursprüngliche Nachricht-
> Von: Verma, Sahil 
> Gesendet: Mittwoch, 11. Mai 2022 20:56
> An: Tomcat Users List 
> Betreff: RE: Help Needed for Root cause - ApacheTomcat services
> stopped
>
> Hi Mark,
> Good day!
>
> Thank you very much for the reply!
>
> Yes, we are using both Apache & Tomcat environment.
>
> Apache - 2.4.25 version
> Tomcat - 8.5.5 version
> OS - Linux
>
>
> You are correct, we got this error in Apache webserver logs. We are
> attaching both Apache httpd (error.log) and Tomcat (Catalina.out) logs
>
> Please let us know if any other information required.
>
> Thanks,
> Sahil
>
>
>
> -Original Message-
> From: Mark Thomas 
> Sent: Wednesday, May 11, 2022 11:39 PM
> To: users@tomcat.apache.org
> Subject: Re: Help Needed for Root cause - ApacheTomcat services
> stopped
>
> That is an Apache Web Server (httpd) log message, not an Apache Tomcat
> log message. Are you sure you are using Apache Tomcat?
>
> Mark
>
>
> On 11/05/2022 19:01, Verma, Sahil wrote:
> > Hi Team,
> >
> >
> >
> > In our production environment, ApacheTomcat services went down. We
> > have checked the logs and found below error -
> >
> >
> >
> > [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
> > 140464737793792] AH00484: server reached MaxRequestWorkers setting,
> > consider raising the MaxRequestWorkers setting
> >
> >
> >
> > Please help to find the root cause of the issue why services got stopped.
> Kindly let us know if any other information required.
> >
> > Apache version - 2.2
> > OS - Linux
> >
> >
> > Thanks,
> > Sahil
> >

Tomcat-Logs looks fine (except some warnings which doesn’t matter here).

The MaxRequestWorkers is documented here:
https://clicktime.symantec.com/3VtPgJ8rmEck16yTrydmCdA6xU?u=https%3A%2F%2Fhttpd.apache.org%2Fdocs%2F2.4%2Fen%2Fmod%2Fmpm_common.html%23maxrequestworkers

You actually have a load or performance issue. This is usually related to your 
application or environment.
You can activate the access-log (either on apache or tomcat side) to view the 
number of requests.
Also log the processing time to see if some requests are taking too long.
Another option would be to activate and check tomcat-manager about the 
currently processed requests or use Apachetop 
(https://clicktime.symantec.com/3WxaHnjWYoWZzcQmX18dHkP6xU?u=https%3A%2F%2Flinux.die.net%2Fman%2F1%2Fapachetop)

I can think of two possible cases:
1) Requests are taking too long (performance issue in the application) and thus 
the number of workers get exhausted
2) You have a high load / number or requests. If you still have CPU and memory 
left, you can increase the workers in the Apache configuration

Greetings,
Thomas


DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
600113. CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of 
DXC Technology Company or one of its affiliates. It is intended exclusively for 
the addressee. The substance of this message, along with any attachments, may 
contain proprietary, confidential or privileged information or information that 
is otherwise legally exempt from disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended recipient 
of this message, you are not authorized to read, print, retain, copy or 
disseminate any part of this message. If you have received this message in 
error, please destroy and delete all copies and notify the sender by return 
e-mail. Regardless of content, this e-mail shall not operate to bind DXC 
Technology Company or any of its affiliates to any order or other contract 
unless pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.


AW: Help Needed for Root cause - ApacheTomcat services stopped

2022-05-12 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello Sahil,

> -Ursprüngliche Nachricht-
> Von: Verma, Sahil 
> Gesendet: Mittwoch, 11. Mai 2022 20:56
> An: Tomcat Users List 
> Betreff: RE: Help Needed for Root cause - ApacheTomcat services stopped
> 
> Hi Mark,
> Good day!
> 
> Thank you very much for the reply!
> 
> Yes, we are using both Apache & Tomcat environment.
> 
> Apache - 2.4.25 version
> Tomcat - 8.5.5 version
> OS - Linux
> 
> 
> You are correct, we got this error in Apache webserver logs. We are attaching
> both Apache httpd (error.log) and Tomcat (Catalina.out) logs
> 
> Please let us know if any other information required.
> 
> Thanks,
> Sahil
> 
> 
> 
> -Original Message-
> From: Mark Thomas 
> Sent: Wednesday, May 11, 2022 11:39 PM
> To: users@tomcat.apache.org
> Subject: Re: Help Needed for Root cause - ApacheTomcat services stopped
> 
> That is an Apache Web Server (httpd) log message, not an Apache Tomcat log
> message. Are you sure you are using Apache Tomcat?
> 
> Mark
> 
> 
> On 11/05/2022 19:01, Verma, Sahil wrote:
> > Hi Team,
> >
> >
> >
> > In our production environment, ApacheTomcat services went down. We
> > have checked the logs and found below error -
> >
> >
> >
> > [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
> > 140464737793792] AH00484: server reached MaxRequestWorkers setting,
> > consider raising the MaxRequestWorkers setting
> >
> >
> >
> > Please help to find the root cause of the issue why services got stopped.
> Kindly let us know if any other information required.
> >
> > Apache version - 2.2
> > OS - Linux
> >
> >
> > Thanks,
> > Sahil
> >

Tomcat-Logs looks fine (except some warnings which doesn’t matter here).

The MaxRequestWorkers is documented here:
https://httpd.apache.org/docs/2.4/en/mod/mpm_common.html#maxrequestworkers

You actually have a load or performance issue. This is usually related to your 
application or environment.
You can activate the access-log (either on apache or tomcat side) to view the 
number of requests.
Also log the processing time to see if some requests are taking too long.
Another option would be to activate and check tomcat-manager about the 
currently processed requests or use Apachetop 
(https://linux.die.net/man/1/apachetop)

I can think of two possible cases:
1) Requests are taking too long (performance issue in the application) and thus 
the number of workers get exhausted
2) You have a high load / number or requests. If you still have CPU and memory 
left, you can increase the workers in the Apache configuration

Greetings,
Thomas



RE: Help Needed for Root cause - ApacheTomcat services stopped

2022-05-11 Thread Verma, Sahil
Hi Mark,
Good day!

Thank you very much for the reply!

Yes, we are using both Apache & Tomcat environment.

Apache - 2.4.25 version
Tomcat - 8.5.5 version
OS - Linux 


You are correct, we got this error in Apache webserver logs. We are attaching 
both Apache httpd (error.log) and Tomcat (Catalina.out) logs

Please let us know if any other information required.

Thanks,
Sahil



-Original Message-
From: Mark Thomas  
Sent: Wednesday, May 11, 2022 11:39 PM
To: users@tomcat.apache.org
Subject: Re: Help Needed for Root cause - ApacheTomcat services stopped

That is an Apache Web Server (httpd) log message, not an Apache Tomcat log 
message. Are you sure you are using Apache Tomcat?

Mark


On 11/05/2022 19:01, Verma, Sahil wrote:
> Hi Team,
> 
> 
> 
> In our production environment, ApacheTomcat services went down. We 
> have checked the logs and found below error -
> 
> 
> 
> [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
> 140464737793792] AH00484: server reached MaxRequestWorkers setting, 
> consider raising the MaxRequestWorkers setting
> 
> 
> 
> Please help to find the root cause of the issue why services got stopped. 
> Kindly let us know if any other information required.
> 
> Apache version - 2.2
> OS - Linux
> 
> 
> Thanks,
> Sahil
> 
> DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
> TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
> 600113. CIN: U72900TN2015FTC102489.
> DXC Technology Company -- This message is transmitted to you by or on behalf 
> of DXC Technology Company or one of its affiliates. It is intended 
> exclusively for the addressee. The substance of this message, along with any 
> attachments, may contain proprietary, confidential or privileged information 
> or information that is otherwise legally exempt from disclosure. Any 
> unauthorized review, use, disclosure or distribution is prohibited. If you 
> are not the intended recipient of this message, you are not authorized to 
> read, print, retain, copy or disseminate any part of this message. If you 
> have received this message in error, please destroy and delete all copies and 
> notify the sender by return e-mail. Regardless of content, this e-mail shall 
> not operate to bind DXC Technology Company or any of its affiliates to any 
> order or other contract unless pursuant to explicit written agreement or 
> government initiative expressly permitting the use of e-mail for such purpose.
> 

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

-bash-4.1$ cat error_log.20220505
rm: cannot remove `/share/images/pdf/Statementkimpickett20220505.zip': No such 
file or directory
rm: cannot remove `/share/images/pdf/Statementcweishuhn20220505.zip': No such 
file or directory
[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising the MaxRequestWorkers setting
[Thu May 05 11:28:16.826878 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27465 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.826994 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27466 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827047 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27467 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827098 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27698 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827151 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27896 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827205 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27971 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827254 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 28071 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827307 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 28135 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829711 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27465 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829835 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27466 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829901 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27467 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829970 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27698 still did not exit, sending a SIGTERM
[Thu 

Re: Help Needed for Root cause - ApacheTomcat services stopped

2022-05-11 Thread Mark Thomas
That is an Apache Web Server (httpd) log message, not an Apache Tomcat 
log message. Are you sure you are using Apache Tomcat?


Mark


On 11/05/2022 19:01, Verma, Sahil wrote:

Hi Team,



In our production environment, ApacheTomcat services went down. We have checked 
the logs and found below error -



[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising the MaxRequestWorkers setting



Please help to find the root cause of the issue why services got stopped. 
Kindly let us know if any other information required.

Apache version - 2.2
OS - Linux


Thanks,
Sahil

DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
600113. CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of 
DXC Technology Company or one of its affiliates. It is intended exclusively for 
the addressee. The substance of this message, along with any attachments, may 
contain proprietary, confidential or privileged information or information that 
is otherwise legally exempt from disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended recipient 
of this message, you are not authorized to read, print, retain, copy or 
disseminate any part of this message. If you have received this message in 
error, please destroy and delete all copies and notify the sender by return 
e-mail. Regardless of content, this e-mail shall not operate to bind DXC 
Technology Company or any of its affiliates to any order or other contract 
unless pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Help Needed for Root cause - ApacheTomcat services stopped

2022-05-11 Thread Verma, Sahil
Hi Team,



In our production environment, ApacheTomcat services went down. We have checked 
the logs and found below error -



[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising the MaxRequestWorkers setting



Please help to find the root cause of the issue why services got stopped. 
Kindly let us know if any other information required.

Apache version - 2.2
OS - Linux


Thanks,
Sahil

DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
600113. CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of 
DXC Technology Company or one of its affiliates. It is intended exclusively for 
the addressee. The substance of this message, along with any attachments, may 
contain proprietary, confidential or privileged information or information that 
is otherwise legally exempt from disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended recipient 
of this message, you are not authorized to read, print, retain, copy or 
disseminate any part of this message. If you have received this message in 
error, please destroy and delete all copies and notify the sender by return 
e-mail. Regardless of content, this e-mail shall not operate to bind DXC 
Technology Company or any of its affiliates to any order or other contract 
unless pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.