No, CustomBuild is really a part of DirectAdmin! pubkey access is fine: https://www.directadmin.com/authorized_keys
No, CustomBuild is really a part of DirectAdmin! pubkey access is fine: https://www.directadmin.com/authorized_keys
I think "Update All" is the culprit As "Build php" is needed after PHP changes. May you check if that solves the problem?
2 thumbs up...I went into the custombuild2 options on DirectAdmin and did a Build on PHP, I can see it went through the motions (php-7.2.20, php56 etc...)
Installing online manual
make[1]: Leaving directory `/usr/local/directadmin/custombuild/mod_fcgid-2.3.9'
mod_fcgid-2.3.9 has been installed successfully.
PHP has been secured.
Restarting php-fpm72.
Rewriting all users httpd.conf files, please wait...
Debug mode. Level 10
dataskq: command: action=rewrite&value=httpd
Restarting php-fpm72.
Restarting apache.
Done!
After I refresh the whole page (not just go back to the Update tab), the message disappears!
For my future reference...
Is this a normal action for custombuild to not run PHP to finish the updates?
How does this work when you have DirectAdmin set to auto update everything (including custombuild stuff) -- will it ever run a bunch of updates and then get stuck needing me to manually "Build" PHP again? I'm sure auto update everything will be set for a lot of "ns2" style backup DNS (ala cPanel DNSONLY) and that's why I'm curious.
I am going to run this on the other servers now to clear them up!
The problem is that you did not have any initial configuration of PHP When you have it - "update" is really fine to be used. If you change phpX_mode/release, "build PHP" is recommended. Of course - we could try detecting it and show a warning, if you find it confusing.
The problem is that you did not have any initial configuration of PHP When you have it - "update" is really fine to be used. If you change phpX_mode/release, "build PHP" is recommended. Of course - we could try detecting it and show a warning, if you find it confusing.
At least coming from the cPanel world, I would assume that custombuild (like EasyApache) would complete the entire task if it detects fresh install, as I don't know many web control panels that do not include PHP at some point. For me, and I'm sure many new DA users, custombuild + web GUI is literally a requirement, as is LetsEncrypt. Hell, I know cPanel runs some things twice just because it can do less checks...since the server hardware has gotten faster cPanel has gotten lazier, fatter.
I think part of what confused me is during the DirectAdmin setup, it asks if you want to go with some default php7 stuff, and when I say yes, then install custombuild + GUI, I only assume that my first interaction with updating PHP (adding versions) or changing modules (imagick), it would do a sanity check for new installations and build/rebuild PHP.
I've just rewrite that part completely, it has the 'expected' behaviour now (it's fine to click "update" now, and it'd get configs ready for you). CustomBuild 2.0 rev. 2166 and newer. Thank you!
Hello,
the same error on all FreeBSD servers:
Done. Making ImageMagick-7.0.8-46...
Trying to make imagemagick...
--- all ---
make all-am
--- utilities/.deps/.dirstamp ---
--- utilities/.dirstamp ---
--- MagickCore/.deps/.dirstamp ---
--- coders/.dirstamp ---
--- coders/.deps/.dirstamp ---
--- filters/.dirstamp ---
--- filters/.deps/.dirstamp ---
--- MagickCore/.dirstamp ---
--- MagickWand/.deps/.dirstamp ---
--- MagickWand/.dirstamp ---
--- Magick++/lib/.deps/.dirstamp ---
--- Magick++/lib/.dirstamp ---
make[1]: make[1]: don't know how to make MagickCore/ImageMagick-7.Q16HDRI.pc. Stop
make[1]: stopped in /usr/local/directadmin/custombuild/ImageMagick-7.0.8-46
*** [all] Error code 2
make: stopped in /usr/local/directadmin/custombuild/ImageMagick-7.0.8-46
make: stopped in /usr/local/directadmin/custombuild/ImageMagick-7.0.8-46
*** The make has failed, would you like to try to make again? (y,n):
CustomBuild 2.0 rev.2167
The man, the myth, the legend.
Thank you, Sir!