DigitalOcean - Centos Stream 9 - Directadmin Installation

KataKotop

Verified User
Joined
May 13, 2022
Messages
21
Hello fellows,
i have been using DA over ten years but this is the first time i have faced an installation error.
I dont know if it is related to DO or Centos 9 but i would be glad if you could assist me.

I have tried to make fresh installations like 10 times or so but on all of them nearly half of the services are not installed.Screenshot_1.jpg


I have also run below commands with no luck :

[root@box ~]# cd /usr/local/directadmin/scripts
[root@box scripts]# ./exim.sh
-bash: ./exim.sh: No such file or directory
[root@box scripts]# ./build proftpd d
-bash: ./build: No such file or directory
[root@box scripts]# ./getlicense
-bash: ./getlicense: No such file or directory




What am i doing wrong here ? :(
 
How fast after installation did you check this?
Because if you remember from those 9 years it always took some time for DA to install and not like in 2 minutes.

Nowadays DA installs very fast and the rest is done on the background so those can get up later on.
So you have to wait some time, maybe 15-30 minutes depending on your system, for things to appear.
Or did you already waited?

Also, you can't run ./build from /user/local/directadmin/scripts that was always done from the /user/local/directadmin/custombuild directory.
 
Hello,
i have waited like 1 hour or so but nothing has changed.
I dont have custombuild directory as it is not installed as i see.

[root@box /]# cd /user/local/directadmin/custombuild
-bash: cd: /user/local/directadmin/custombuild: No such file or directory
[root@box /]#
 
I'm not sure if that is the cause, but Centos Stream 9 is not on the supported OS list yet.
You might want to check the logs to see what might have gone wrong.
Especially logs in the /var/log/directadmin directory.

Or maybe choose for another OS like Alma Linux 8.6 or Rocky Linux. Because for hosting you might want to use a more stable OS.
 
Hey richard,
I am glad to see you are very kind on helping me .
Which OS would be your Suggestion ? Which is more close to CentOS ?
Or shall i choose CentOS 8 or 7 ?
Thanks.
 
I have tried rocky and faced xfs issue again like i did in CentOS 9 :

Admin admin is being created by root.
Error with quotas: xfs_quota: cannot set limits: Function not implemented

secure_access_group='access' did not exist (9999). Creating it and adding defaults.
Admin user created



Any idea ?
 
Or shall i choose CentOS 8 or 7 ?
Neither. As I suggested Alma Linux 8.6 or Rocky. They are both 1 on 1 compatible with Centos.
If you want to make use of Cloudlinux later on I would suggest Alma Linux because that is supported by Cloudlinux.

As for the quota, that can be fixed by where @BillyS is pointing to probably.
 
I have waited like 10 hours today after the installation on a RockyLinux 8.5 droplet in DigitalOcean but no luck:

CustomBuild installation has failed​

2022-05-16 08:35
CustomBuild installation has failed, please check the following file for more information:
/usr/local/directadmin/custombuild/install.txt


Log of install.txt :

Thank you for using PHP.

Done Configuration.
Trying to make php...
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/date/lib -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -DHAVE_TIMELIB_CONFIG_H=1 -Iext/date/ -I/usr/loca$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -Iext/libxml/ -I/usr/local/directadmin/custombuild/php-7.4.29/ex$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/openssl/ -I/usr/local/directadmin/custombuild/php-7.4.29/ext/openssl/ -DPHP_ATOM_INC -I/usr/l$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/openssl/ -I/usr/local/directadmin/custombuild/php-7.4.29/ext/openssl/ -DPHP_ATOM_INC -I/usr/l$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
/bin/sh /usr/local/directadmin/custombuild/php-7.4.29/libtool --silent --preserve-dup-deps --mode=compile cc -DHAVE_CONFIG_H -I/usr/local/directadmin/custombuild/php-7.4.29/ext/pcre/pcre2lib -DZEND_ENABLE_STAT$
cc: fatal error: Killed signal terminated program cc1
compilation terminated.
make: *** [Makefile:790: ext/pcre/pcre2lib/pcre2_match.lo] Error 1
 
RockyLinux 8.5 droplet in DigitalOcean but no luck
That is strange because I installed DA on Rocky without any problems. Does the hardware set up / partitions meet the requirements on this page?


Also, before attempting the installation, you need to update the system and run these pre-installations commands found here:

 
I have waited like 10 hours today after the installation
Also in addition to previous responses, you don't have to wait 10 hours. Normally the DA installation should take no longer then 30 minutes to (on very slow systems) 60 minutes maximum. So mostly you should have most things or everything running within 30-40 minutes.
I just mention this so you don't have to wait too long. Often people thing they can start within 5 minutes and that is not the case, so that's why I asked how long you waited in my first reply.
 
I have increased RAM to 2gb and all seems good for now.Moved websites.
Quota shows the disk usage values properly.All services up.

There is one single issue left : scripts cant send email.

I have uninstalled csf but all emails wait in the email queue :



2022-05-18 01:43:06 H=gmail-smtp-in.l.google.com [142.250.27.26] Connection timed out
2022-05-18 01:45:18 H=alt2.gmail-smtp-in.l.google.com [142.250.150.26] Connection timed out
2022-05-18 02:03:15 H=gmail-smtp-in.l.google.com [2a00:1450:4025:402::1a] Network is unreachable
2022-05-18 02:05:26 H=alt3.gmail-smtp-in.l.google.com [74.125.200.27] Connection timed out
2022-05-18 02:07:37 H=alt4.gmail-smtp-in.l.google.com [142.250.157.26] Connection timed out
2022-05-18 02:07:37 [email protected] R=lookuphost T=remote_smtp defer (110): Connection timed out
2022-05-18 03:00:44 H=gmail-smtp-in.l.google.com [2a00:1450:4025:401::1b] Network is unreachable
2022-05-18 03:02:55 H=gmail-smtp-in.l.google.com [142.250.102.26] Connection timed out
2022-05-18 03:02:55 H=alt1.gmail-smtp-in.l.google.com [2a00:1450:4025:c03::1a] Network is unreachable
2022-05-18 03:05:06 H=alt1.gmail-smtp-in.l.google.com [142.251.9.26] Connection timed out
2022-05-18 03:05:06 H=alt2.gmail-smtp-in.l.google.com [2a00:1450:4010:c1c::1a] Network is unreachable
2022-05-18 03:05:06 H=alt3.gmail-smtp-in.l.google.com [2404:6800:4003:c00::1b] Network is unreachable
2022-05-18 03:05:06 H=alt4.gmail-smtp-in.l.google.com [2404:6800:4008:c13::1a] Network is unreachable
2022-05-18 03:05:06 [email protected] R=lookuphost T=remote_smtp defer (101): Network is unreachable
2022-05-18 04:03:16 H=gmail-smtp-in.l.google.com [142.250.27.26] Connection timed out
2022-05-18 04:05:27 H=alt4.gmail-smtp-in.l.google.com [142.250.157.26] Connection timed out
2022-05-18 04:05:27 [email protected] R=lookuphost T=remote_smtp defer (110): Connection timed out
2022-05-18 06:54:33 H=gmail-smtp-in.l.google.com [2a00:1450:4025:401::1b] Network is unreachable
2022-05-18 06:54:33 [email protected] R=lookuphost T=remote_smtp defer (101): Network is unreachable
2022-05-18 09:54:58 H=alt1.gmail-smtp-in.l.google.com [142.251.9.26] Connection timed out
2022-05-18 09:54:58 [email protected] R=lookuphost T=remote_smtp defer (110): Connection timed out
2022-05-18 09:56:46 H=gmail-smtp-in.l.google.com [2a00:1450:4025:401::1b] Network is unreachable
2022-05-18 09:58:56 H=gmail-smtp-in.l.google.com [142.250.27.27] Connection timed out
2022-05-18 09:58:56 H=alt1.gmail-smtp-in.l.google.com [2a00:1450:4025:c03::1a] Network is unreachable
 
I have got a ticket response regarding this issue from DigitalOcean :

Hello there,

Thanks for reaching out to DigitalOcean!

Stopping spam is a constant fight and due to this, your account has
restrictions specifically on port 25.

However, you are able to use mail services using ports 587, 993, 995 and
465. You will need to open these ports in your firewall. Here is our
guide to common iptables commands:

https://www.digitalocean.com/commun...mmon-firewall-rules-and-commands#service-mail

We realize this is inconvenient for sending mail from your Droplet. As a
solution, you can consider using a third party service such as SendGrid
or similar to processes mail there instead of your Droplet. We apologize
for the frustration but we're not able to lift this port restriction at
this time.

In terms of a workaround, here are a few alternatives:

1. Utilize port 587 for SMTP relay via another mail provider, for
example, G Suite/Gmail, Mailgun, etc. We have a guide on doing so using
Postfix here:

https://www.digitalocean.com/commun...elay-with-postfix-and-mailgun-on-ubuntu-16-04

2. Configure your app or service to send mail directly using either an
SMTP client connection (typically using port 587), or API call via
another mail provider such as Sendgrid, Mailgun, Mandrill, etc.

Please note that with this restriction in place on port 25, mail servers
hosted here will be unable to directly relay email to other mail
servers, as communication between mail servers typically takes place on
port 25.

We think the API is the best solution, as it is honestly more scalable
and what we would use if we wanted to "future proof" the project.

Please feel free to reach out to us if you have any additional queries.
We're always here for you!
 
I didn't realize DigitalOcean blocked port 25 but that makes sense given the cost of a droplet. Google Cloud does the same thing and they have a deal with SendGrid to handle reasonable volumes of mail. Since I had to go through this process myself, I documented how to use DA with Sendgrid if you go that route:


Once Exim is set up, then you'll have to set up the DNS, that process is well documented by SendGrid.

 
I didn't realize DigitalOcean blocked port 25 but that makes sense given the cost of a droplet. Google Cloud does the same thing and they have a deal with SendGrid to handle reasonable volumes of mail. Since I had to go through this process myself, I documented how to use DA with Sendgrid if you go that route:


Once Exim is set up, then you'll have to set up the DNS, that process is well documented by SendGrid.


Hello,
i have tried to setup exim to forward emails via sendgrid but i could not achieve this.
When i click rety on frozen mails on DA admin panel, i see "list processed" in a green bubble but emails still staying there.
 
What do your email logs say? Have you looked into your sendgrid account to see what is happening with the emails there? Are you sure that is set up correctly?
 
This is the log from exim :

022-05-24 23:52:47 H=smtp.sendgrid.net [108.128.229.184]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:52:47 H=smtp.sendgrid.net [54.228.39.88]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:52:47 H=smtp.sendgrid.net [18.197.194.208]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:52:47 H=smtp.sendgrid.net [52.57.139.126]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:52:47 [email protected] R=smart_route T=auth_relay defer (-27): failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:54:16 H=smtp.sendgrid.net [18.197.194.208]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:54:16 H=smtp.sendgrid.net [54.228.39.88]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:54:16 H=smtp.sendgrid.net [108.128.229.184]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:54:16 H=smtp.sendgrid.net [52.57.139.126]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-24 23:54:16 [email protected] R=smart_route T=auth_relay defer (-27): failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-25 00:10:58 H=smtp.sendgrid.net [54.228.39.88]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-25 00:10:58 H=smtp.sendgrid.net [108.128.229.184]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-25 00:10:58 H=smtp.sendgrid.net [18.197.194.208]: failed to expand helo_data: $ not followed by letter, digit, or {
2022-05-25 00:10:58 H=smtp.sendgrid.net [52.57.139.126]: failed to expand helo_data: $ not followed by letter, digit, or {
 
Back
Top