"Tempoarily out of resourse, please try again later." Error Message in Web Browser

carboncopy · 08-04-2005, 04:33 AM

Hi!

I have a Slackware machine which I configured so that NAT works on it.

It is Slackware-current with 2.6.12.3 compiled using gcc4.0 which is compiled on the machine itself.

Now, I have been getting the following message on my browsers regardless of operating system (Linux, Mac Os X, or Windows): (Note the spelling mistakes are not my work, am quoting verbatim.)

Code:

Tempoarily out of resourse, please try again later.

Intermittently I get the message while browsing the Internet, a simple click of reload will bring me to the web page I intended to go.

I notice this started happening lately after a tcpip, iptables, etc upgrades. But it has reduced (one time today) after peaking a few days ago.

What could be the problem?

win32sux · 08-04-2005, 05:38 AM

are you using the adblock extension?? if so, try disabling it to see if it's the culprit...

carboncopy · 08-05-2005, 03:26 AM

But, I am getting that error even in Safari and Camino.

Yesterday, I tried browsing using Firefox on Slackware, I get that error message twice in very short period. And, with Slackware machine not running any progs, I have not been getting it.

Oh, another note, I did use bittorrent, could it be that the new iptables or tcpip is limitting the number of connections?

Note, I did not touch iptables rules.

Edit:
And, my camino, firefox, etc. Are set to use high maximum connections.

win32sux · 08-05-2005, 03:34 AM

Quote:

Originally posted by carboncopy
But, I am getting that error even in Safari and Camino.

Yesterday, I tried browsing using Firefox on Slackware, I get that error message twice in very short period. And, with Slackware machine not running any progs, I have not been getting it.

Oh, another note, I did use bittorrent, could it be that the new iptables or tcpip is limitting the number of connections?

Note, I did not touch iptables rules.

Edit:
And, my camino, firefox, etc. Are set to use high maximum connections.

hmmm... what's your current ephemeral port range??

Code:

cat /proc/sys/net/ipv4/ip_local_port_range

n0xvb · 08-05-2005, 03:34 AM

Believe it or not, I think that is a server error 503, and the server has too many connections on it. When you hit refresh there is a connection available and it lets you in.

I'd bet it's coincidental to your upgrades.

carboncopy · 08-05-2005, 04:13 AM

Code:

root@carboncopy:~# cat /proc/sys/net/ipv4/ip_local_port_range
32768   61000

What does those figure means?

carboncopy · 08-05-2005, 04:18 AM

Quote:

Originally posted by n0xvb
Believe it or not, I think that is a server error 503, and the server has too many connections on it. When you hit refresh there is a connection available and it lets you in.

I'd bet it's coincidental to your upgrades.

The thing is, it is purely random. And it happens even with almost omni-potent sites, such as IBM, BBC etc.

And if it is error 503, the browser will catch it its own error message.

It is still happening today. Even without bittorrent running, single client connected to Slackware (NAT machine).

Strange.

win32sux · 08-05-2005, 04:27 AM

Quote:

Originally posted by carboncopy

Code:

root@carboncopy:~# cat /proc/sys/net/ipv4/ip_local_port_range 32768 61000

What does those figure means?

look here: http://www.ncftp.com/ncftpd/doc/misc...ral_ports.html

basically, it's the range of (source) ports your box will use when making connections to remote boxes... try increasing the range a little to see if it helps, although you have a pretty wide range set already:

Code:

echo "32768 64000" > /proc/sys/net/ipv4/ip_local_port_range

what's your tcp fin timeout set to?? you can check with:

Code:

cat /proc/sys/net/ipv4/tcp_fin_timeout

if it's set to something like 180 bring it down to 30:

Code:

echo "30" > /proc/sys/net/ipv4/tcp_fin_timeout

then see if the problem continues...

on a side note, i had a similar problem for the past couple weeks, i was suspecting it was my squid proxy server but it ended up being my ISP's DNS servers that were messed-up... if you wanna look at the thread it's this one:

http://www.linuxquestions.org/questi...hreadid=346094

of course i'm not saying the issues are related or anything like that...

carboncopy · 08-05-2005, 04:35 AM

Ah, cool. Thanks a great deal win32sux!

Code:

root@carboncopy:~# cat /proc/sys/net/ipv4/tcp_fin_timeout
60

I brought it down to 30 as suggested.

Will this setting stays this way? Or do I have to include it into rc.local? Or is there some config file somewhere?

Edited:
Oh, it still happens

Just happens as I click edit this post.

Anyhow, I changed the port range as well.

So, guess those are not the prob.

carboncopy · 08-05-2005, 04:41 AM

I will download iptables and tcpip source and search for

"Tempoarily out of resourse, please try again later."

And maybe a search through the kernel?

First, I need to find the bash command to do that. Any fast help?

keefaz · 08-05-2005, 04:45 AM

Go into your source dir then try :

Code:

grep -rlni 'Tempoarily out of resourse, please try again later.' .

Or maybe just grep for "Tempoarily", that should be efficient

win32sux · 08-05-2005, 05:04 AM

check this out: http://forum.mydefcon.org/viewtopic.php?t=463

what on earth is Streamyx??

carboncopy · 08-05-2005, 05:05 AM

Thanks keefaz!

With first class help and pointers from LQ-Slackware. One can really be lazy

Or spoilted.

win32sux · 08-05-2005, 05:06 AM

Quote:

Originally posted by carboncopy
Will this setting stays this way? Or do I have to include it into rc.local? Or is there some config file somewhere?

yeah, it'll be gone upon reboot, so you need to put the echoes in rc.local or similar... BTW, if you're on slackware it's common to instead use the rc.firewall script for this...

carboncopy · 08-05-2005, 05:09 AM

Quote:

Originally posted by win32sux
check this out: http://forum.mydefcon.org/viewtopic.php?t=463

what on earth is Streamyx??

Streamyx is what MY (idiotic) ISP called it's ADSL service.

http://www.tm.net.my/html/pstreamyx.cfm

Great. Thanks for the info. Now I can call and bug them.

Case is close for Slackware being the suspect.

Thanks everybody!

At least I learn something more about networking parameters in Linux.