thank you, but my CB UI is weird... it will auto update, that is why I want to disable itIt nowadays gets updated together with Directadmin updates.
So that would mean not to auto update Directadmin.
Thank you, so I can set cb_version_check_odds_percent=0 for thatYou have to check this one and the link in there.
There is one in the directadmin.conf and one in options.conf file. The one in directadmin.conf is for auto updating directadmin (or not).
Maybe it can also be done to change this setting, but I'm not 100% sure.
cd /usr/local/directadmin/custombuild
./build update
./build versions
or can I just set cb_version_check_odds_percent=0You have to check this one and the link in there.
There is one in the directadmin.conf and one in options.conf file. The one in directadmin.conf is for auto updating directadmin (or not).
Maybe it can also be done to change this setting, but I'm not 100% sure.
Yes ./buil update and ./build update_versions if I'm correct.by myself to check new version, right? thanks
I can't say because don't know. I never used that one.or can I just set cb_version_check_odds_percent=0
Thanks, so that mean no matter I set, it will random to rollback me..."cb_version_check_odds_percent" will triggered when you login and it random number percent to execute command.
Explain with php code
Code:$b =rand(0 , 1000); if($b <= 10){ exec('/usr/local/directadmin/custombuild/build update'); }
Thanks, I find my CB UI will rollback my versions.txt, so even I just update my directadmin to new version, and new directadmin will force my cb update to 2.0.0 and work without problem, but after few hours, my CB UI will auto rollback to 2.0.0 (rev: 2945) because it's old and check failed for the directadmin version(they show only hash "2138cff12eb6d60eec6bde18b2bf38b208f9ae51", not the version like 1.644)Yes ./buil update and ./build update_versions if I'm correct.
That would update DA and all other stuff, including for example php and the GUI.
I can't say because don't know. I never used that one.
Also I don't know how it's going to work with versions.txt nowadays since that changed. The versions.txt is now bound to DA, so I don't know if and how the rollbacks can be done now.
Since I'm not native English the new way of working got me a bit confused on this.
Thank you, so I just change it to 0 and restart my directadmin@ASUS
Nope, if you change it to "0", it will not triggered.
I just explain workflow how logics work.
da update current --force
As said before... versions.txt is now bound to DA versions and not updated anymore as was done the way it was done before.till rollback my versions.txt
Thanks, I know it, I'm not talking about directadmin and custombuild, I mean "custombuild UI"As said before... versions.txt is now bound to DA versions and not updated anymore as was done the way it was done before.
Thank you, I find one inside my cron.d and deleted itWe are fine and not have problem rollback. Only your server.
Just check in
/etc/cron.daily/
/etc/cron.d/
find the file that contents relate to custombuild update.
Assume we can't do anything unless there have someone to check directly in your server.
if you out of idea, just create Tickets and let DA team fixed it for you.
also, cloud you share your /etc/cron.daily/custombuild file's content? I want to check this file get any problem inside too, thanksWe are fine and not have problem rollback. Only your server.
Just check in
/etc/cron.daily/
/etc/cron.d/
find the file that contents relate to custombuild update.
Assume we can't do anything unless there have someone to check directly in your server.
if you out of idea, just create Tickets and let DA team fixed it for you.
Thank you, so can I confirm about:I don't enable automatic update with cronjob. So that's why I suggest you to check cronjob, that problem may come from these cronjob.
also it could be in
cron.hourly , cron.daily , cron.weekly , cron.monthly
however, create support tickets, will solves your problem in no time.