IW Caching/loading setting changed -- Let me know if you have errors

[Ziroc]

Originally posted by Annatar: Don't know if this has anything to do with it, but around 8:33 this morning (europe time), I got the same DNS error that I got 2 weeks ago, me not getting on IW for 2 days. It wasn't able to enter IW for at least an hour, after that everything was fine. Is this linked to the thing your now doing Ziroc?

I had IW off and unplugged the Server and opened it up, and it was FULL of dust! I mean LOTS!!! So I cleaned everything, and the fans. Now it's running cooler, and MUCH quieter. [img]smile.gif[/img]

The DNS issue is not on our end anymore. We use Timewarner's DNS, and they have the best supported systems in Florida. Call your ISP and complain!!

[Ziroc]

Originally posted by Kakero: I don't see any difference. I still occasionally get the 30-second CGI timeout.

Ok, I'll change that timeout to 100. (I thought I DID that last time, I guess when I re-installed it, it wrote a new ini file.)

Let me know if you see any errors now.

[pcgiant]

Z,
I've been getting this error at the top of almost every page I load:

X-Powered-By: PHP/4.1.2 Date: Thu, 17 Apr 2003 00:26:21 GMT Expires: Thu, 17 Apr 2003 00:27:21 GMT Last-Modified: Thu, 17 Apr 2003 00:26:21 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache X-Reason: redirect Location: http://www.ironworksforum.com/ubb/cg...DaysPrune=1000 Content-type: text/html PHP Warning: Unable to load dynamic library './php/php_zlib.dll' - The specified module could not be found. in Unknown on line 0.

I also got a blank page with the exact same message on it.
I don't know whether this is a problem at my end or your end, but I figured you'd like to know.

[Ziroc]

Originally posted by pcgiant: Z, I've been getting this error at the top of almost every page I load: X-Powered-By: PHP/4.1.2 Date: Thu, 17 Apr 2003 00:26:21 GMT Expires: Thu, 17 Apr 2003 00:27:21 GMT Last-Modified: Thu, 17 Apr 2003 00:26:21 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache X-Reason: redirect Location: [URL=http://www.ironworksforum.com/ubb/cgi-bin/ultimatebb.cgi?ubb=forum;f=18;DaysPrune=1000]http://www.ironworksforum.com/ubb/cgi-bin/ultimatebb.cgi?ubb=forum;f=18;DaysPrune=1000[/ URL] Content-type: text/html PHP Warning: Unable to load dynamic library './php/php_zlib.dll' - The specified module could not be found. in Unknown on line 0. I also got a blank page with the exact same message on it. I don't know whether this is a problem at my end or your end, but I figured you'd like to know.

Don't worry, I was just trying something [img]smile.gif[/img] That error won't show up again. (I was messing with zlib compression). Thanks though [img]smile.gif[/img]

[Luvian]

I got the same as pcgiant about 5 mins ago, I could not open any page without getting this message.

[Bahamut]

Well I get sometimes trailing posts like...

"Hey! Blahblahblah< insert whatever technical thing here you are not supposed to see >"

anyway once i get my hands on it I will post it here

[ 04-16-2003, 11:24 PM: Message edited by: Bahamut ]

[GokuZool]

Last night every page I clicked on didn't load properly. It got half way and then it came up with something like this.

"a href="http://www.ironworksforum.com/ubb/cgi-bin/ultimatebb.cgi?ubb=recent_user_posts;u=00011836" style="color: #E3B573; tex
Fatal error: Maximum execution time of 30 seconds exceeded in C:\Inetpub\wwwroot\ironworksforum\ubb\noncgi\cache-ECQOC5PU\ubb_files\forums\Forum10\015104.cgi on line 1100" thing.

[TheCrimsomBlade]

I haven't gotten any errors but for the last two days but IW has been Loading V ery......V.....e.....r.....y........V.........e... .....r........y...........S........L........o..... ...w..........l.........y!!
hay this is my 600th post I cant wait to see My new Avatar

[Bardan the Slayer]

Jeez, it looks like I'm the only person who is better off! LOL!

The message is clear - if you want to get the best out of IW, move to Newcastle. That's obviously the differentiating factor

[Bardan the Slayer]

Though I have to add, I am still getting the timeout on PM sending (but naturally, the PM still sends as it always did)