Build script doesn't respond anymore

Suurbier

Suurbier

Verified User
Joined
Apr 23, 2007
Messages
246
Code: 
[root@reverse ~]#cd /usr/local/directadmin/custombuild
[root@reverse custombuild]#./build update

The build script doesn't respond anymore (I tried it several times).
How to solve this?
 
Code: 
-rwxr-xr-x 1 root root 300485 Mar 18 02:47 /usr/local/directadmin/custombuild/build
[root@reverse custombuild]#
 
Well, when i run the build script (help, update, versions etc) I don't get any outpout.. It waits for me to do ctrl+c and try it again (and it fails again)..
 
try running it like this:
sh -x build update
and see what line it is hung on. Did you install/update your firewall, perhaps it is hung trying to access one of the web servers.
 
toml said:
try running it like this:
sh -x build update
and see what line it is hung on. Did you install/update your firewall, perhaps it is hung trying to access one of the web servers.
Click to expand...

Code: 
+ ADDITPHP=4
++ grep php5_cgi /usr/local/directadmin/custombuild/options.conf
++ cut -d= -f2
+ DEFPHP_CGI=no
+ DACONF_APACHE_VER=1.3
+ '[' -e /usr/local/directadmin/conf/directadmin.conf ']'
++ grep '^apache_ver=' /usr/local/directadmin/conf/directadmin.conf
++ cut -d= -f2
+ DACONF_APACHE_VER=2.0
+ '[' yes = yes ']'
+ wget http://files1.directadmin.com/services/custombuild/versions.txt -O /usr/local/directadmin/custombuild/versions.txt
Probably wget fails?

Edit:
My versions.txt seems to be empty?
When i fill versions.txt manually with the content of http://files1.directadmin.com/services/custombuild/versions.txt and try to run build update the file gets empty again...

Another test:
Code: 
[root@reverse custombuild]#wget http://files1.directadmin.com/services/custombuild/versions.txt
--2012-03-26 10:17:31--  http://files1.directadmin.com/services/custombuild/versions.txt
Resolving files1.directadmin.com... 216.144.254.90
Connecting to files1.directadmin.com|216.144.254.90|:80...

Wget works fine if I try to use another URL (like google.com)
 
Last edited:
Yes that means your wget is blocking. I am guessing that perhaps a firewall is blocking access. I would assume that after a certain amount of time it should time-out and move onto the next step. How long have you let the script run? Please check your firewall, and make sure you are not blocking port 80 ingress/incoming (in this case).
 
toml said:
Yes that means your wget is blocking. I am guessing that perhaps a firewall is blocking access. I would assume that after a certain amount of time it should time-out and move onto the next step. How long have you let the script run? Please check your firewall, and make sure you are not blocking port 80 ingress/incoming (in this case).
Click to expand...

I have been waiting for minutes, without success. My firewall is fine, no directadmin ip's on the banlist.

I am using another files server now, that solved the problem.
 
You must log in or register to reply here.
Back
Top