a log file for the Custombuild package build process

[Aar]

Does DirectAdmin also keep a log file for the Custombuild package build process—for example, when building PHP—that records details such as which version's build was initiated, which patches were installed, etc.?

 

[zEitEr]

Hello,

Check /var/log/directadmin/custombuild.*.log

[root@poralix directadmin]# ls -1 /var/log/directadmin/custombuild.*.log
/var/log/directadmin/custombuild.1789981200.2442421.Y3Jvbl9leGVjdXRlAA.log
/var/log/directadmin/custombuild.1790140346.6238.Y2xlYW4A.log
/var/log/directadmin/custombuild.1790140349.6768.aW5zdGFsbAA.log
...
...
/var/log/directadmin/custombuild.1792732683.3792803.Y2xlYW4A.log
/var/log/directadmin/custombuild.1792732684.3793728.aW5zdGFsbAA.log
/var/log/directadmin/custombuild.1792732703.3795341.dXBkYXRlX3ZlcnNpb25zAA.log

[root@poralix directadmin]#

 

[Aar]

That is the entire output.
I was actually hoping for a simple log that would just indicate which processes were executed—along with a date and time—and when the recent security PHP patches were applied. After all, how am I supposed to tell from this log whether the patch has actually been implemented?

 

[Aar]

grep -n "109618" custombuild.1792592597.3552864.cGhwAA.log doesn't find anything?

 

[zEitEr]

After all, how am I supposed to tell from this log whether the patch has actually been implemented?

If the logs miss such details, then you have no evidences. There are possible options:

1. Run da build php and connect to the process with strace or another debugger.
2. Run custombuild/directadmin with --debug flag:

da build php --debug 2>&1 | tee out.txt

will catch:

...
patching file sapi/fpm/tests/ghsa-7qg2-v9fj-4mwv-status-xss.phpt
++ for patch_file in "${WORKDIR}/patches/${dir}"/*.patch
++ '[' '!' -f /usr/local/directadmin/custombuild/patches/php-5.6/172-php-cve-2026-14355.patch ']'
++ patch -p1
patching file NEWS
patching file ext/openssl/openssl.c
Hunk #1 succeeded at 5566 with fuzz 1 (offset 144 lines).
Hunk #2 succeeded at 5680 with fuzz 1 (offset 143 lines).
patching file ext/openssl/tests/gh22186.phpt
++ for patch_file in "${WORKDIR}/patches/${dir}"/*.patch
++ '[' '!' -f /usr/local/directadmin/custombuild/patches/php-5.6/173-php-5.6-cve-2026-109618.patch ']'
++ patch -p1
patching file Zend/zend_API.c
...

In any way if you don't trust custombuild/directadmin, you should quit using it.

 

[Aar]

I was just curious.
Fortunately, I have full confidence that everything worked out after a 'da build update' and 'da build php'. I saw the patch neatly in my custombuild patch directory.

And I am also a bit wiser about debugging now.