Tag Info

Hot answers tagged

18

The default connection timeout in IIS7 is 2 minutes. Click on your web site in IIS Mgr, click Advanced Settings, and expand Connection Limits. The Connection Timeout (Seconds) setting is what governs this. If IIS doesn't receive activity on a connection for this duration then it will time the connection out. This is regardless of whether or not the ...


17

I found answer on my posting on nginx forum - http://forum.nginx.org/read.php?2,127854 The answer, in my case, is to set: request_terminate_timeout=30s in php-fpm config. Note, you can use values other than 30s also. I used it to match my value in main php.ini file which is: max_execution_time = 30 Thanks All. :-)


15

HA! I finally found the problem myself. It's more related to programming than server admin, but I decided to put the answer here anyway because by searching google I found I'm not the only one with that kind of problem (and since Apache hangs, the first guess is that there's a problem with the server). The issue is not with Apache, but with my Wordpress. ...


12

It looks like the CentOS box's SSHD config is not set to do the client KeepAlive. Drop these two lines in your CentOS sshd config (/etc/ssh/sshd_config), restart it, and enjoy! KeepAlive yes ClientAliveInterval 60 While you're at it, I'd recommend using gnu screen to keep your session alive on the CentOS side.


11

Sounds like a timeout setting. So your SSMS thinks it takes too long and cancels the connection for you. The SQL server roles back. But there is help. You are not the first person to encounter this. See here. For everybody who doesn't want to click the link. Here is the price winning answer: After hitting the same error, I stumbled upon the corrent ...


11

fping might be a better tool than the stock ping you are using. What OS are you on?


9

Here how it resolved my issue: make following changes to /etc/nginx/nginx.conf in http { section proxy_connect_timeout 600s; proxy_send_timeout 600s; proxy_read_timeout 600s; fastcgi_send_timeout 600s; fastcgi_read_timeout 600s; and then restart nginx /etc/init.d/nginx restart


8

On Ubuntu the command timeout exists, which is part of coreutils. You can use it like this to set a timeout. Older versions of Debian/Ubuntu didn't build and include this command, but there is a comparable timeout package that you can install. # puppet shouldn't take more then 40 minutes! 47 * * * * root /usr/bin/timeout 2400 /usr/bin/puppet agent ...


7

Yes. Configure SSH to send keepalive packets.


7

Maybe it's proxies - proxies are configured in the environment, so might be different for different users, but be consistently set up for those users by their login scripts. I'd suggest env | grep proxy to find out what is set.


6

Generally with any service you will get these sometimes if the server is too busy to respond, hickup in network etc. You might try to see if the server in under load when you get these alerts. I think the main thing you want to look at is the max_check_attempts directive associated with the service or the service's template so you don't get an alert until ...


6

The actual answer is almost always that you have a NAT device of some sort in the path, usually a firewall, whose state tables have a fairly aggressive timeout. Because you leave your ssh connection idle for some periods of time, the NAT device "forgets" the mapping between your inside address and source port number, and your ephemeral outside NATted ...


6

curl -I will generate a HEAD request. Adding the -L option will make it follow redirects. Timeouts can be controlled with several options depending on which bit of the request you want to time out. From the man page: --connect-timeout <seconds> Maximum time in seconds that you allow the connection to the server to take. This only limits ...


6

You could always try doing 310 minutes instead.


5

exponential back-off http://en.wikipedia.org/wiki/Exponential_backoff


5

It is probably a connection rate limit, imposed by the platform's equivalent of iptables. Three connections per minute is the most common setting, which looks suspiciously like what you're seeing.


5

Hm, it's possible you did not enable to the correct web extensions which could explain it's intermittent working. I'll link you to this article from technet: technet But the snippet I'd pay attention to is this; IIS6 Dynamic Content: A 404.2 entry in the W3C Extended Log file is recorded when a Web Extension is not enabled. Use the IIS Microsoft ...


5

The accepted alternative to port 25 is port 587 as has been recorded in RFC2476 since 1998. You can read all about it if you are into RFCs at http://www.ietf.org/rfc/rfc2476.txt. This is what we have been using for many years to circumvent the ISPs blocks on port 25.


5

Try connection to it remotely with PowerShell. This usually requires less resources then a full fledged RDP-session. Example: invoke-command -computername myServer -scriptblock {Get-Process} This way you can get a look at what's running remotely and later on, kill it.


5

This happens in dual stack IPv4/IPv6 environments where the machine doing a DNS lookup sends requests for AAAA and A records on the same socket, expecting to receive two replies back. This is default behavior for relatively recent versions of glibc. The Juniper firewall, however, drops the connection after the first reply comes back. The Juniper knowledge ...


5

If DNS resolution simply times out and a response never comes back from the DNS server at all, or the return is SERVFAIL, then the message is supposed to be queued and tried again later. If DNS resolution returns NXDOMAIN (the name doesn't exist) then the message is supposed to be returned immediately. See RFC 5321, section 5.1: The lookup first ...


4

There is a good writeup on this problem here. They recommend: ssh -o TCPKeepAlive=yes or: ssh -o TCPKeepAlive=no -o ServerAliveInterval=15 However, I do have an issue at my work site where I get disconnected from sessions, where at home they are fine. I believe my firewall (SonicWall) may be flucking with TCPKeepAlive, maybe because of NAT. My SSH ...


4

I found the cause of this problem. Port 443 was closed in my firewall configuration. It worked sometimes because my IP was added to firewall as a safe one. That's why it did not work for other IPs. All I had to do is open port 443 in firewall and it works just fine :)


4

On your server, add the following line to /etc/ssh/sshd_config and restart the SSH daemon: ClientAliveInterval 30 This will cause the server to send a message to the client requesting a response, if there has been no activity for 30 seconds. (Basically a ping to see if the client is still there). If the hotel's firewall is kicking off "inactive" ...


4

You could use replication to replicate the database to another then backup the replica instead.


4

If you are using php 5.3, increase the backlog. If you are using php 5.2, backport the patch to increase the backlog size from 128. Also, use a unix socket rather than a TCP socket. unix:/tmp/php5-cgi.sock (or the relevant path)


4

I would be using nmap for this task. nmap -sP --max-retries=1 --host-timeout=1500ms 10.0.0.1 See the nmap Documentation for more details on this.


4

A good discussion about time-wait is given by How to forcibly close a socket in time-wait. According to this reference, the number of time-wait connections should correspond to the traffic in the last 4 minutes. Do these numbers approximately match?


4

Quite often this is due to a reverse DNS lookup of your host IP. Make sure your client IP has a reverse IP DNS record. See this link for more details of a work around if setting up reverse records is out of your sphere of influence.


4

I was actually unable to reproduce this on: 2011/08/20 20:08:43 [notice] 8925#0: nginx/0.8.53 2011/08/20 20:08:43 [notice] 8925#0: built by gcc 4.1.2 20080704 (Red Hat 4.1.2-48) 2011/08/20 20:08:43 [notice] 8925#0: OS: Linux 2.6.39.1-x86_64-linode19 I set this up in my nginx.conf: proxy_connect_timeout 10; proxy_send_timeout 15; proxy_read_timeout ...



Only top voted, non community-wiki answers of a minimum length are eligible