annc
Verified User
- Joined
- Jun 10, 2008
- Messages
- 26
I have two DA servers on CloudLinux, one is CL 8.10 and the other is 9.7. Both have the same problem.
After updating Apache to 2.4.66 today, all websites reported a 500 error.
The error.log from Apache displayed the following entries with every request:
And nothing else.
I wasted a lot of time debugging because none of the log permissions or anything like that had changed.
Finally, I just had to replace the suexec binary in /usr/sbin/ with the old version – everything started working.
I thought to myself, okay, something's broken with suexec in Apache 2.4.66 – I'll downgrade to 2.4.65, which I had until yesterday. The same thing – the suexec that compiled (identical to the one for 2.4.66) throws the same errors. Replacing it again works with 2.4.65.
What's changed in suexec is that the binary compiles from Apache2 sources, to which DirectAdmin applies its own proprietary patches.
This change caused our two production systems to take several hours of debugging time.
There was a very similar thread here in 2025-10: https://forum.directadmin.com/threads/cgi-scripts-stop-working-after-da-apache-update.81083/
It ended with a suggestion to replace the suexec binary (it worked) and the thread was closed.
This can't work in its current form, because I'll have to remember to restore the suexec binary with every Apache update.
Working suexec:
Corrupt suexec (binary is 2x larger!):
Update 1 month ago was fine, nothing was broken.
After updating Apache to 2.4.66 today, all websites reported a 500 error.
The error.log from Apache displayed the following entries with every request:
Code:
suexec failure: could not open log file
fopen: No such file or directoryAnd nothing else.
I wasted a lot of time debugging because none of the log permissions or anything like that had changed.
Finally, I just had to replace the suexec binary in /usr/sbin/ with the old version – everything started working.
I thought to myself, okay, something's broken with suexec in Apache 2.4.66 – I'll downgrade to 2.4.65, which I had until yesterday. The same thing – the suexec that compiled (identical to the one for 2.4.66) throws the same errors. Replacing it again works with 2.4.65.
What's changed in suexec is that the binary compiles from Apache2 sources, to which DirectAdmin applies its own proprietary patches.
This change caused our two production systems to take several hours of debugging time.
There was a very similar thread here in 2025-10: https://forum.directadmin.com/threads/cgi-scripts-stop-working-after-da-apache-update.81083/
It ended with a suggestion to replace the suexec binary (it worked) and the thread was closed.
This can't work in its current form, because I'll have to remember to restore the suexec binary with every Apache update.
Working suexec:
Code:
./suexec: setuid ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=f682e750e9ee11111f2e0229664ba0c22efc9173, for GNU/Linux 3.2.0, not stripped
MD5: 6e29764d27078e2c6257e67ff5b82fe4Corrupt suexec (binary is 2x larger!):
Code:
./suexec.new: setuid ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9c5ecab0fa4bef985917372d5a66757c22967093, for GNU/Linux 3.2.0, with debug_info, not stripped
MD5: 5db866432f62420f49a0503c8ce8feeb
Last edited:
