DirectAdmin v1.643 has been released

Is versions.txt also integrated with DirectAdmin? Not possible anymore to update only versions.txt?
 
Yes, CustomBuild is bundled with DA including versions.txt and other helper files:

Code:
$ tar tf directadmin_8c5c161f99047c9098e7bf4f89005929dea3942e_linux_amd64.tar.gz  | grep ./custombuild/
./custombuild/
./custombuild/configure/
./custombuild/configure/ap2/
./custombuild/configure/ap2/cert_config.txt
./custombuild/configure/ap2/conf/
./custombuild/configure/ap2/conf/extra/
./custombuild/configure/ap2/conf/extra/directadmin-vhosts.conf
./custombuild/configure/ap2/conf/extra/httpd-alias.conf
...
./custombuild/patches/suexec-safe.patch
./custombuild/patches/unit_cgroup.patch
./custombuild/build
./custombuild/versions.txt
 
Last directadmin's Custombuild tell me PHP 7.4 7.4.32 update to 7.4.30 is available
Is that real?? thanks
 
I'm back from the recovery! I have tested the latest DA alpha and opened various tickets, is this really your serious?
 
Are you sure it is latest version of DA?
This is why I ask about it, before 35e666716a8844ef1fa219efed8fdb23bd74b267 this version, it ask me upgrade to 7.4.32
Snap2.jpg

but after build 8c5c161f99047c9098e7bf4f89005929dea3942e it ask me "Upgrade" yes, it say upgrade to 7.4.30 so i feel weird

Snap1.jpg
 
8c5c161f99047c9098e7bf4f89005929dea3942e should have 7.4.32 in versions.txt. Please let us know the output of:
Code:
grep php74 /usr/local/directadmin/custombuild/versions.txt
da update current --force
grep php74 /usr/local/directadmin/custombuild/versions.txt
 
8c5c161f99047c9098e7bf4f89005929dea3942e should have 7.4.32 in versions.txt. Please let us know the output of:
Code:
grep php74 /usr/local/directadmin/custombuild/versions.txt
da update current --force
grep php74 /usr/local/directadmin/custombuild/versions.txt
Thank you, after your command, the update message was change to "There are no updates available" , thanks

Snap1.jpg
 
8c5c161f99047c9098e7bf4f89005929dea3942e should have 7.4.32 in versions.txt. Please let us know the output of:
So why do the older versions of DA to not have this in custombuild? I don't had any notice (which I normally get) that there is an update to php 7.4.32 (running 7.4.30 now). But we don't always want to update Directadmin instantly, for obvious reasons.
Which is why we still keep using just custombuild to update. And we only update DA if it's really stable and without issues.
We're not happy with this.
 
So why do the older versions of DA to not have this in custombuild? I don't had any notice (which I normally get) that there is an update to php 7.4.32 (running 7.4.30 now). But we don't always want to update Directadmin instantly, for obvious reasons.
Which is why we still keep using just custombuild to update. And we only update DA if it's really stable and without issues.
We're not happy with this.
it's weird now, I think there was a bug here(maybe version file'scloud server synchronization problem???), after some hours, I see php7 version in custombuild back to 7.4.30 again(because I'm runing PHP 7.4.32 so it tell me to "update"[not downgrade] to 7.4.30 ), and custombuild main page tell me to "update".
 
Last edited:
Finally I find a problem in custombuild's log
Warning: DateTime::setTimestamp() expects parameter 1 to be int, string given in /usr/local/directadmin/plugins/custombuild/admin/tabs/log_files.php
Warning: filesize(): stat failed for /usr/local/directadmin/plugins/custombuild/logs/..log in /usr/local/directadmin/plugins/custombuild/admin/tabs/log_files.php on line 29 0 B

Is that causes this problem? any help? thanks
 
it's weird now, I think there was a bug here(maybe version file'scloud server synchronization problem???), after some hours, I see php7 version in custombuild back to 7.4.30 again(because I'm runing PHP 7.4.32 so it tell me to "update"[not downgrade] to 7.4.30 ), and custombuild main page tell me to "update".
I guess you're on stable branch, not current? I'd suggest using current for latest versions.
 
@Richard G so running ./build update on older DA versions doesn't show the update to 7.4.32??:unsure:
I'm not sure, didn't look yet, because I don't mind that part. But normally I always get a notice via the cron that the update from 7.4.30 to 7.4.32 is available. I didn't get any such message now. That is the problem.

And I'm on current branch.
 
I'm not sure, didn't look yet, because I don't mind that part. But normally I always get a notice via the cron that the update from 7.4.30 to 7.4.32 is available. I didn't get any such message now. That is the problem.

And I'm on current branch.
I'm wondering do you try these command?

grep php74 /usr/local/directadmin/custombuild/versions.txt
da update current --force
grep php74 /usr/local/directadmin/custombuild/versions.txt

to check your the php7 version in your versions.txt are same as me?
before runing "da update current --force"

it show 7.4.30 after "da update current --force" , it show 7.4.32 again, but... after few hours, it back to 7.4.30 again.
(I just try it again and again, yes, 7.4.30 > force update > 7.4.32 > few hours later > 7.4.30...)

Are you got same problem as me? can you check this for me?
Thanks
 
@Dettol, PHP 7.4.32 is shipped with DA current upgrade versions.txt file. Old CustomBuild available on the files.directadmin.com mirrors is still having PHP 7.4.30. I think something on your system is pulling versions.txt from files servers.

Code:
# da v
DirectAdmin v.1.643 8c5c161f99047c9098e7bf4f89005929dea3942e

# grep php74 /usr/local/directadmin/custombuild/versions.txt
php74:7.4.32:

# curl -s https://files.directadmin.com/services/custombuild/versions.txt | grep php74
php74:7.4.30:

So I have two hypothesis to explain such behaviour:

1. You are still having old Custombuild script version (that still pulls versions.txt from mirrors). Please check if checksums match:

Code:
# md5sum /usr/local/directadmin/custombuild/build /usr/local/directadmin/custombuild/versions.txt
b8f5628041c6117c176ed3695b90f5d0  /usr/local/directadmin/custombuild/build
a32e7f4f677a6bc15d9dd0746512c26a  /usr/local/directadmin/custombuild/versions.txt

2. You have some cronjob or other 3rd party tool that automatically pulls versions.txt from mirrors.
 
Back
Top