apache 2.4.49,2.4.52 strange unreachable after pass few hours

2.4.53 will available in this month and solves this issued.

don't try to update 2.4.52, it problem on busy server.
 
matkra said:
I can see that apache 2.4.52 is available for update again in custombuild. Any changes since last problems with "strange unreachables" ? Problem solved ?
Click to expand...
It includes the patch.
 
We have updated all our server to this version and didnt encounter any problems
 
I have problem too after update Apache to 2.4.52.
In log I have this info:
Code: 
AH00016: Configuration Failed
But if I check config the syntax is oki.

Any idea how solve this problem? Or where I can try found problem?
 
Did you try:
Code: 
./build rewrite_confs

Also how do you check config? By checking the configuration manually or are you running
Code: 
apachectl configtest
 
infosun said:
I have problem too after update Apache to 2.4.52.

Any idea how solve this problem? Or where I can try found problem?
Click to expand...

How to ask for help here on the forum

All: I wanted to make this post for all of those that might be new or just need guidance on how to post a question. Most important things first. This forum is Community based the questions are generally answered by community members. It is frequented by Directadmin support members but it is...
forum.directadmin.com forum.directadmin.com
 
@staff_nowa
what's your issued ???

Ours issued is hang, and no any log/error show.

Please create your own Threads Issued.

And we not face with that your issued.

AH00045: child process 427266 still did not exit, sending a SIGTERM

What wrong with apache2 every time drops connection /var/log/httpd/error_log:[Tue Mar 08 11:44:31.111581 2022] [core:warn] [pid 130022:tid 140085277390784] AH00045: child process 157611 still did not exit, sending a SIGTERM /var/log/httpd/error_log:[Tue Mar 08 11:44:31.111602 2022] [core:warn]...
forum.directadmin.com forum.directadmin.com

Thanks
 
Same here. It seems to be problem with Directadmin because problem is always when new domain is added or logs are rotated and there's need to reload httpd.
Doing killall httpd -9, service httpd start works.
 
pat0 said:
Same here. It seems to be problem with Directadmin because problem is always when new domain is added or logs are rotated and there's need to reload httpd.
Doing killall httpd -9, service httpd start works.
Click to expand...
Longer ago we had "same problem" changed then in a config file the reload in restart, that solved as kind of workarround.

don't know where i did that then!
 
Apache 2.4.53 @Centos 7
crash with this error

[mpm_event:error] [pid 13732:tid 140429964114048] AH03490: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.
 
yak983 said:
AH03490: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.
Click to expand...
stackoverflow.com

Scoreboard is full,not at MaxRequestWorkers

I an using Apache and Tomcat with mod-jk in my project. My web application is in Tomcat instances. I am using Apache jmeter for testing http load on tomcat. But I'm getting the error Scoreboard is ...
stackoverflow.com stackoverflow.com

scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit

Hi, after about month of working my apache is not serving any website, even if it is running just fine, until apache is restarted (then everything work just fine), it happens like 3 times now since last months. In error log I found this: [Tue Jul 13 10:37:54.440017 2021] [mpm_event:error] [pid...
forum.directadmin.com forum.directadmin.com
 
Seems also 2.4.53 has the issue on Centos 7. Apache stopped yesterday during a busy time leaving the following error messages in the log:

[Mon Apr 18 17:05:42.998690 2022] [http2:warn] [pid 30166:tid 139708167579776] AH10291: h2_workers: cleanup, 4 idle workers did not exit after 5 seconds.
[Mon Apr 18 18:00:17.178299 2022] [http2:warn] [pid 30468:tid 139708167579776] AH10291: h2_workers: cleanup, 5 idle workers did not exit after 5 seconds.

Considering rolling back to 2.4.51 although a little reluctant to do so. Also putting in place a nightly Apache restart and enhanced monitoring.
 
We're also still seeing more and more servers that are coping with this issue, all with Apache 2.4.53, and even on CentOS7/CloudLinux7 as well as CloudLinux6.

Pinning version 2.4.51 in the custom_versions.txt seems to work in all cases for these hosts, so it looks more and more likely that the underlying issue in Apache has not been fixed yet.

Apart from manually reverting to the .51 version, there seems to be little we can do, as I assume the issue is known and being worked on by Apache?
 
You must log in or register to reply here.
Back
Top