httpd 2.4.49

[damador]

Apache httpd 2.4.49 Released

Apache HTTP Server Project

 

[BadBlock]

After updating to this version Apache began to hang sliently after a few hours with no meaningful records in the error log. CentOS 8. Is it just me?

Rolled back to 2.4.48, will continue to watch it.

 

[ikkeben]

After updating to this version Apache began to hang sliently after a few hours with no meaningful records in the error log. CentOS 8. Is it just me?

Rolled back to 2.4.48, will continue to watch it.

No

apache 2.4.49,2.4.52 strange unreachable after pass few hours

Centos 8 with Nginx_Apache apache with mod_maxminddb (mod_maxminddb not recomplier) I just post here to anyone got same problem with me, in now I temporary back to 2.4.48 problem start after update to 2.4.49 first I try to find log /var/log/httpd/* test with "pstack {PID}" not show any...

forum.directadmin.com

 

[ju5t]

Same here. Has happened a few times now. Will do a rollback too.

 

[nmb]

After updating to this version Apache began to hang sliently after a few hours with no meaningful records in the error log. CentOS 8. Is it just me?

Rolled back to 2.4.48, will continue to watch it.

Got same problem with CentOS 7... It happened randomly.. No log.. So, rollback to older version for now.

 

[webmaster-hub]

Same on a few servers running Debian 9
Rolled back all servers to 2.4.48 two days ago.

 

[damador]

well ubuntu 20.04 .3 LTS works

 

[kebirhost]

We downgraded apache version as 2.4.48 for many servers. I hope the issue will be found.

 

[Richard G]

No issues here, Centos 7 and 8 servers (just Apache, no nGinx).
Maybe I'm lucky.

 

[Eureka]

Rocky Linux 8 on 5 servers. Apache no problems that I have noticed.

 

[dwight_d]

Also no issues here on CentOS 7, but I’ll keep a lookout for any signs of what’s being described here!

 

[yonatanp]

upgraded a sample of 20 servers so far to 2.4.49
will not upgrade the rest.. waiting to see if there are any user reports,
no reports of issues so far, 10 are shared hosting, 10 are dedicated with single website.

will give this some time, if any issue arises will update.

maybe someone with the issue run a strace on to try and get more insight ?

 

[Richard G]

Seems DA has stopped the updates of Apache. We're now getting Apache 2.4.49 to 2.4.48 update is available mails from Custombuild. So it seems the 2.4.49 update is suspended for the time being.

 

[yonatanp]

have you been able to reproduce any issue ?
I have updated last week and did not get any reports of issues,
should I downgrade anyway?

Please can someone from DA clarify ?

 

[doumu]

Updates should not be pushed unless they have been tested and proven stable. If users want a bleeding edge release, they can have that option, but to update this to thousands of users and leaving them all literally hanging is not worth paying for. This is the second time within a few months this has happened with Apache. Apache is the core function most for most DirectAdmin use cases and this is not acceptable.

Where is the DA team on this? No updates? CB issued a rollback update, but no communication.

 

[sufiyanshaikh]

I was facing same Apache hang issue without any logs.
Now a few mins ago saw Apache update but it was a downgrade.

Downgraded immediately thinking Apache update was the culprit.

 

[damador]

now downgrade to 2.4.48 killed nginx / apache sever - even after rebuild ....

 

[damador]

after downgrade - rebuild usual setup - not working then rebuild only nginx

now nginx alone 502 Bad Gateway

nginx-apache ...
nginx -apache show nginx functioning normally but apache backend not respond

now apache alone

Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xe" for details.
Restarting apache.
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xe" for details.


root@vps:~# systemctl status httpd.service
* httpd.service - The Apache HTTP Server
Loaded: loaded (/etc/systemd/system/httpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-09-21 11:23:06 CEST; 19s ago
Process: 169550 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 169550 (code=exited, status=1/FAILURE)
CPU: 50ms

Sep 21 11:23:06 vps.pozwa.pl systemd[1]: Starting The Apache HTTP Server...
Sep 21 11:23:06 vps.pozwa.pl httpd[169550]: httpd: Syntax error on line 51 of /etc/httpd/conf/httpd.conf: Syntax error on line 3 of /etc/httpd/conf/extra/httpd-phpmod>
Sep 21 11:23:06 vps.pozwa.pl systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 11:23:06 vps.pozwa.pl systemd[1]: httpd.service: Failed with result 'exit-code'.
Sep 21 11:23:06 vps.pozwa.pl systemd[1]: Failed to start The Apache HTTP Server.



line 51 is Include /etc/httpd/conf/extra/httpd-phpmodules.conf


fixed apache by turning off modesec

now unable to apache_nginx ... only pache 2.4.48 work ....

 

[sufiyanshaikh]

after downgrade - rebuild usual setup - not working then rebuild only nginx

Why did you downgrade when you had no issues?

well ubuntu 20.04 .3 LTS works

 

[damador]

Why did you downgrade when you had no issues?

indeed i should not touch this

but anyway Apache 2.4.48 with nginx-1.21.3 worked before .. with apache .49 update also ... now clean setup throw 502 error - seems that "new-old" 2.4.48 not work

systemctl status httpd.service and systemctl status nginx.service show that both started ok