Cannot Build. Getting Warning: Transient problem: timeout

[d_noizeshakerz]

Hello,

I would appreciate urgent assistance on this. I can't build anything, and getting the following error:

curl: (28) Resolving timed out after 5514 milliseconds
Download of https://files.directadmin.com/services/custombuild/httpd-2.4.54.tar.gz failed, re-downloading the file...
Warning: Transient problem: timeout Will retry in 1 seconds. 3 retries left.
Warning: Transient problem: timeout Will retry in 2 seconds. 2 retries left.
Warning: Transient problem: timeout Will retry in 4 seconds. 1 retries left.

However, when I tried to download the file manually via wget, it works fine.

It's a new server install with Centos 7 and latest Directadmin.

Please help!

 

[Active8]

Which version of cURL you are using ?

 

[sec-is]

Hey, I just ran into the same problem (Centos 7)

# curl --version
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.36 zlib/1.2.7 libidn/1.28 libssh2/1.4.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets

I do can open curl https://files.directadmin.com from the commandline.
Trying to set downloadserver-files1.directadmin.com in options.conf did not help either.

# ./build exim_conf
Warning: Transient problem: timeout Will retry in 1 seconds. 3 retries left.
Warning: Transient problem: timeout Will retry in 2 seconds. 2 retries left.
Warning: Transient problem: timeout Will retry in 4 seconds. 1 retries left.

curl: (28) Resolving timed out after 5513 milliseconds
Download of https://files.directadmin.com/servi...3/exim.conf-SpamBlockerTechnology-v4.5.43.txt failed, re-downloading the file...

#curl https://files.directadmin.com/servi...3/exim.conf-SpamBlockerTechnology-v4.5.43.txt
(the complete file is now on my screen).
Line 1: # SpamBlockerTechnology* powered exim.conf, Version 4.5.43
LAST: # End of Exim 4 configuration

So our server is not being blocked in any way, it is the build program that seems to do something weird (parameters we can''t see?)

 

[sec-is]

I have found the issue.
# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 127.0.0.1
nameserver 213.186.33.99
search ovh.net

After this update:
nameserver 8.8.8.8
nameserver 127.0.0.1
nameserver 213.186.33.99
search ovh.net

it worked.
But now I know my local BIND is not letting me query (I tested this with nslookup on server 127.0.0.1).

After reviewing the configuration in /etc/named.conf, this part:
allow-recursion { 127.0.0.1; };
recursion yes;

I was missing the recursion yes;

After restarting named (it did not restart, it failed to stop, saw it in /var/log/messages as:
Dec 29 13:35:45 ns3108794 systemd: named.service stopping timed out. Terminating.)

After it had restarted, and I remarked 8.88.8. in "/etc/resolv.conf" as like this
#nameserver 8.8.8.8

(note: I tested from an external server to query the DNS on this server, to see if I could only request known domains, and that was the case, querying external domains gave errors).


Now it works!

[root@ns3108794 named]# cd /usr/local/directadmin/custombuild
[root@ns3108794 custombuild]# ./build exim_conf
######################################################################## 100.0%
######################################################################## 100.0%
Restarting exim.

Long story short: if your local DNS is not responding, the curl command seems to work from the command line, however the ./build command seems to force the first IP in your resolv.conf. And I remember this has always been the case (many years). Since the problem does not arise often, I had forgotten about this issue. And why it is like it is? Hmmmmm. Must have to do with the way it is invoked (curl).

CASE CLOSED.