Custombuild & Issues

M

metrovps

New member
Joined
Oct 28, 2022
Messages
11
Hello,

Recently, I'm seeing a weird issue with Almalinux 8.

Custombuild plugin isn't installed by default. When I install it manually, it shows "{}" in edit options page. Although the options.conf is present, but ./build all says,

"
[root@server-103-174-50-224 custombuild]# ./build all
./build: line 1516: [: 1231fc54d10578e379ebf6f73a6bc24987e05b90: integer expression expected
./build: line 1521: [: 1231fc54d10578e379ebf6f73a6bc24987e05b90: integer expression expected
./build: line 1529: [: 1231fc54d10578e379ebf6f73a6bc24987e05b90: integer expression expected
./build: line 1534: [: 1231fc54d10578e379ebf6f73a6bc24987e05b90: integer expression expected
Your DirectAdmin version (1231fc54d10578e379ebf6f73a6bc24987e05b90) is older than minimal required for this version of CustomBuild (1.63). Please run '/usr/local/directadmin/custombuild/build update_da'

I'm already on 1.644.

Screenshot_2.jpg


Screenshot_3.jpg
 
metrovps said:
Custombuild plugin isn't installed by default. When I install it manually, it shows "{}" in edit options page. Although the options.conf is present, but
Click to expand...
I think your installation hasn't finished, please check "Message System".
 
smtalk said:
I think your installation hasn't finished, please check "Message System".
Click to expand...
I can find,
CustomBuild installation has failed, please check the following file for more information:
/usr/local/directadmin/custombuild/install.txt

[root@server-103-174-50-224 ~]# cat /usr/local/directadmin/custombuild/install.txt
cat: /usr/local/directadmin/custombuild/install.txt: No such file or directory

How to reinstall custombuild ? I have tried the solutions in the forum/tutorials.
 
I found the install.txt with this:

checking if event MPM supports this platform... yes
checking if mpmt_os2 MPM supports this platform... no
checking if prefork MPM supports this platform... yes
checking if WinNT MPM supports this platform... no
checking if worker MPM supports this platform... yes
checking whether to enable mod_http2... checking dependencies
checking for OpenSSL... (cached) yes
setting MOD_LDFLAGS to "-lssl -lcrypto -lrt -lcrypt -lpthread -ldl"
setting MOD_CFLAGS to ""
setting MOD_CPPFLAGS to "-DH2_OPENSSL"
checking for nghttp2... checking for user-provided nghttp2 base directory... none
checking for pkg-config along /usr/local/lib/pkgconfig:... checking for nghttp2 version >= 1.2.1... FAILED
configure: WARNING: nghttp2 version is too old
no
checking whether to enable mod_http2... configure: error: mod_http2 has been requested but can not be built due to prerequisite failures

*** There was an error while trying to configure Apache 2. Check the configure/ap2/configure.apache file
 
I have re-run the DirectAdmin installation & now ./build all command is working, but still I can't see the CustomBuild Options via GUI. It shows {} still !
 
metrovps said:
I have re-run the DirectAdmin installation & now ./build all command is working, but still I can't see the CustomBuild Options via GUI. It shows {} still !
Click to expand...
What's your system version of PHP?
 
smtalk said:
What's your system version of PHP?
Click to expand...
It was 8.1 selected I saw. Why the previous custombuild (in default installation) failed I have no clue. I used 'auto' variable. After completing the ./build all, the custombuild plugin is now working. In the meantime, what I did is, I didn't ran yum update at the first installation but ran that before the 2nd installation. Not updating the system is that which has made all these issues ?
 
metrovps said:
Isn't it possible at your end to include the update command as well (as per the OS detected) ?
Click to expand...
It's doable, but I'm not sure if everyone would like to get yum -y update done automatically with every installation of DA?
 
smtalk said:
It's doable, but I'm not sure if everyone would like to get yum -y update done automatically with every installation of DA?
Click to expand...
I asked that because I found another user posting the same error like the above I mentioned. Not sure if he did the same or not. But, if that solves an issue, I don't think people would get hurt. Also, cPanel updates the system prior & then starts their own installation.
 
smtalk said:
It's doable, but I'm not sure if everyone would like to get yum -y update done automatically with every installation of DA?
Click to expand...
IMO, if the new update was designed in an updated OS, then logically it should include that command too.
 
metrovps said:
I asked that because I found another user posting the same error like the above I mentioned. Not sure if he did the same or not. But, if that solves an issue, I don't think people would get hurt. Also, cPanel updates the system prior & then starts their own installation.
Click to expand...
What was the OS there? CentOS 7, which was older than 7.3?
 
"yum -y update" should running by yourself. Not depending on the script. Also It linux knowledge when you install new OS or get new Server from Provider.
 
jamgames2 said:
"yum -y update" should running by yourself. Not depending on the script. Also It linux knowledge when you install new OS or get new Server from Provider.
Click to expand...

The command `yum update` was the solution he discovered by trial and error as he mentioned, and the DA installer did not mention that he has an old OS. I think @smtalk was giving an option there and IMO it is no harm to put it as I have seen many installer scripts from other developers include that as well. So everyone gets the same update on the same OS builds.
 
MaXi32 said:
So everyone gets the same update on the same OS builds.
Click to expand...
If that would be done only on fresh installs I don't mind.

But I agree with @jamgames2 this should not be done on existing systems.
Some people do not upgrade everything always of their OS or just wait to update a little bit for a reason.

That other devs do it, does not automatically make it right. For example cP also use their own binaries so they need everything to be compatible with their own rpm's.

Ofcourse people should keep their systems up to date.
 
Richard G said:
Ofcourse people should keep their systems up to date.
Click to expand...

Sadly, should and do are two very different things.

I think hosting providers should do a much better job than they do in providing an up-to-date OS out-the-box. A lot of security incidents could be prevented this way, leading to less servers being compromised, and less abuse reports for the host to process.

With that said, I'm aware it's not just hosts - ISOs provided by the flavours like CentOS, Debian, Ubuntu, etc. often have hundreds of updates available out-the-box.

Me personally, I deploy with AlmaLinux 8, run a full yum update, reboot the system (never hurts to make sure an update didn't cause upset, resulting in an unbootable OS), and then install DirectAdmin. I've had very few issues with DirectAdmin, the amount of bugs I've noticed has been extremely minimal. Maybe part of my luck comes from updating the OS first? :)
 
EthernetServers said:
I think hosting providers should do a much better job than they do in providing an up-to-date OS out-the-box.
Click to expand...
I think that job is for the root admins, not for the datacenters or hosting providers which provide an OS. They provide images mostly as provided by the OS mirrors. It would be too much work and too expensive to download updates and create new iso's every time.
I see you too acknowledge that the iso's are provided.

Keeping systems up to date is for the main users of the system. So for the root administrators, just as it is for home users with their Windows machines to run the Windows update regularly.

In fact, you can also create an automatic system update via cron.

Personally I also regularly do a yum update, especially at first after a new/fresh OS install.

But it's also a blaim/support question. If an OS update on CP goes wrong, I will blame CP and demand support for it, and they will give that support (you pay the price for it).
If DA would be starting to update OS on existing systems (not systems with DA already installed), and something goes wrong, then it can be said it's their fault and experienced on the forum with other things learn us that they will be blaimed.
While a DA issue caused by the user not updating it's system is the users fault. The few times it happens.

Big question is then, do we want DA to raise prices and also support the OS? Or should we behave as admins should, know the system and take care of the updates ourselves, or with a crontab, and let people who don't, have a learning moment for the future?
I'd rather choose for the latter.
 
Richard G said:
It would be too much work and too expensive to download updates and create new iso's every time.
Click to expand...

Providers can implement something like cloud-init to automatically handle updates on first boot - saving the need to be re-creating templates, except the very first time when they add the template. Some providers do this already.

And don't get me wrong, I'm not saying that templates should be fully up-to-date, all the time - that's not realistic, but they should at least be refreshed every time there is a minor release for a given template, i.e. Ubuntu 22.04 -> Ubuntu 22.04.1.... Debian 11.4 -> 11.5, etc.

If you deployed a CentOS 7 server with some providers now, they'd have the template exactly as it was back in 2014 when it was released, leaving a very scary number of serious root-level vulnerabilities unpatched.

It should be up to a systems administrator to properly secure a system, but sadly, many people who buy servers are not systems administrators - just hobbyists who run nothing more than `bash <(curl -LSs https://download.directadmin.com/setup.sh || curl -LSs https://download-alt.directadmin.com/setup.sh) 'KEY'` and forget about it. And consequently, they either have buggy DirectAdmin installations (and come to complain about them being buggy) or they find their server is hacked, again, coming to complain thinking the control panel is at fault.
 
You must log in or register to reply here.
Back
Top