connection timed out: No input given before connect_timeout reached

shivahost

Verified User
Joined
Mar 7, 2013
Messages
209
Hi,

Please check attached image:

da.jpg

it says: Your connection has timed out Details: No input given before connect_timeout reached

I see this many times. in admin level and also in user level. in any page it may happen: process monitor, service monitor, file manager and even when I want to save an edited html file!

It happens immediately! no time to wait! when I click on link this message comes in less then a second without any waiting.

Please help me.
 

shivahost

Verified User
Joined
Mar 7, 2013
Messages
209
I think these are related to my problem:


in /var/log/directadmin/error.log


2013:07:19-05:36:26: Timeout from from 2.178.137.130 : last flagged: Sockets::handshake:done

2013:07:19-05:36:26: Timeout from from 2.178.137.130 : last flagged: Sockets::handshake:done

2013:07:19-05:36:38: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the program catches, blocks or ignores this signal.)
 

ditto

Verified User
Joined
Apr 27, 2009
Messages
2,565
Are you running newest version of DirectAdmin? If not, upgrade:

Code:
cd /usr/local/directadmin/custombuild
./build update
./build update_da
Does this directory exist?: /home/tmp/ If not, create it and set permissions to 777

What are the group/owner and file permissions on these directories and files?:

/usr/local/directadmin/conf/ (should be 700 and diradmin diradmin)
/usr/local/directadmin/custombuild/ (should be 755 and root root)
/usr/local/directadmin/data/ (should be 711 and diradmin diradmin)
/usr/local/directadmin/plugins/ (should be 711 and diradmin diradmin)
/usr/local/directadmin/scripts/ (should be 711 and diradmin diradmin)

Are you using a custom skin, or standard "enhanced" skin?

Are you running out of free space in /tmp?

Clear cache in your web browser, and restart the web browser and try again. If it does not help, try a different web browser.

Try restart DirectAdmin in shell: service directadmin restart
 

shivahost

Verified User
Joined
Mar 7, 2013
Messages
209
Are you running newest version of DirectAdmin? If not, upgrade:

Code:
cd /usr/local/directadmin/custombuild
./build update
./build update_da
Does this directory exist?: /home/tmp/ If not, create it and set permissions to 777

What are the group/owner and file permissions on these directories and files?:

/usr/local/directadmin/conf/ (should be 700 and diradmin diradmin)
/usr/local/directadmin/custombuild/ (should be 755 and root root)
/usr/local/directadmin/data/ (should be 711 and diradmin diradmin)
/usr/local/directadmin/plugins/ (should be 711 and diradmin diradmin)
/usr/local/directadmin/scripts/ (should be 711 and diradmin diradmin)

Are you using a custom skin, or standard "enhanced" skin?

Are you running out of free space in /tmp?

Clear cache in your web browser, and restart the web browser and try again. If it does not help, try a different web browser.

Try restart DirectAdmin in shell: service directadmin restart
thanks, but there is no problem with all of these: DA version, permissions, skin, /tmp, browser and etc.
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,005
Hello,

As mentioned in the error, the connect_timeout limit is being hit, eg:
Code:
cd /usr/local/directadmin
./directadmin c | grep connect_timeout
where the default is 5 seconds.

You can increase this value to a higher number in the directadmin.conf to allow more time.
The value doesn't exist in the directadmin.conf, so add it to override the internal default.

I'll also change the default value from 5 to 10.
http://www.directadmin.com/features.php?id=1494

John
 

shivahost

Verified User
Joined
Mar 7, 2013
Messages
209
Hello,

As mentioned in the error, the connect_timeout limit is being hit, eg:
Code:
cd /usr/local/directadmin
./directadmin c | grep connect_timeout
where the default is 5 seconds.

You can increase this value to a higher number in the directadmin.conf to allow more time.
The value doesn't exist in the directadmin.conf, so add it to override the internal default.

I'll also change the default value from 5 to 10.
http://www.directadmin.com/features.php?id=1494

John
thanks, I will test it.
 

shivahost

Verified User
Joined
Mar 7, 2013
Messages
209
Hello,

As mentioned in the error, the connect_timeout limit is being hit, eg:
Code:
cd /usr/local/directadmin
./directadmin c | grep connect_timeout
where the default is 5 seconds.

You can increase this value to a higher number in the directadmin.conf to allow more time.
The value doesn't exist in the directadmin.conf, so add it to override the internal default.

I'll also change the default value from 5 to 10.
http://www.directadmin.com/features.php?id=1494

John
I didn't see any error after using this solution, about 24 hours.
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,541
Location
Maastricht
I did not changed it to 10 seconds yet, but I still have the error some times, but in those cases the error appears instantly, not after 5 seconds.
 

shivahost

Verified User
Joined
Mar 7, 2013
Messages
209
I did not changed it to 10 seconds yet, but I still have the error some times, but in those cases the error appears instantly, not after 5 seconds.
try this solution! my problem was same to yours. I changed to 20 and there is no error yet.
 
Top