I've been getting an error message lately when accessing the Forums:

CGI Wrap Error: The server load is too busy, please try again later. (Or words to that effect)

I've contacted the Web Host company to see if this can be resolved.

If you experience this error, please make a note of the date and time and either post it as a reply to this thread (once you can access the Forums again) or email me to let me know that info.

If you can copy the error message (Drag across it with your mouse and hit CTRL-C or Open Apple-C, then paste it into the message, it might help.

Thanks,

John

John--I got the same thing yesterday and today at 2:15 PM This is how it read:
CGIwrap Error: Server load too high, please try again later.
"the lightkeeper"-Mike

>>CGI Wrap Error: The server load is too busy, please try again later. <<

Yep I got it. 3 times in succession at around 1:45 Central before I got an individual forum page to load.

More info below on what this CGI thing is...

CGI (Common Gateway Interface) is a way for a web server to execute a program and pass information to it. Strictly speaking its an interface definition.

A CGI program is one executed on a Web server in response to a request from a web page. A typical program is one that receives information from the user's web page (the one they're on when they make a request), accesses a database, gets some information, then dynamically formats a web page to return to the requesting end-user. Each user making a request causes the CGI program to load then execute - once it sends a response back, the program then dies.

CGI is pretty simple to do, but its expensive in terms of Web server resources. A major expense is loading the CGI program every time its executed. Typically, the Web server must go 'out of process' to execute the CGI program - the Operating System must allocate memory separate from the the memory in which the Web server runs, read the CGI program from disk, pass it data from the web page, then execute it. This is easy when requests are low, but resource requirements (memory, cpu cycles, etc.) can add up quickly with multiple concurrent requests.

The error message is probably an indication there is a bottleneck some where. Luckily there are lots of ways to deal with the issue, but usually none of these are super cheap.

With more folks off work during the Holiday time, its likely a greater load is being placed on the Web server during time periods in which it normally does not see much load. Its important for ISPs to keep close watch on server performance - Web sites *do* become popular!

Do you have a Service Level Agreement with your ISP? That is, a contract that spells out the minimum service (including performance) they'll provide?

Geeks. What can you say...
__
/im

CGIwrap Error: Server load too high, please try again later.

Got it around 2:50 PM Mountain Time.

FWIW, I just keep re-trying until I connnect.

One other thing....and it's probably at my end, but when I tried to respond to this around 15 minutes ago, it wouldn't go through my company's firewall, which has never happened before. Then I tried sending a test message through and it connected without a problem.

As I said, it's probably at my end, but I thought I'd mention it.

Oh yeah....one OTHER item...when I tried sending this NOW, I'm getting the CGI error message again.

Regards,
Brian

[This message has been edited by PamBrian (edited 12-22-98).]

I've gotten the same CGI message 5 or 6 times in the last 10 minutes (5:07 EST). I just keep trying until I get through.

I gotten them several times in the past.
Just figured it was AOL again.
Signed off. Back on. Everything copesetic.
You mean it wasn't AOL? Just serendipity?

Neither, Fred.

Fwiw, if you encounter the error there's no need to sign-off then on. Just click your browser's 'Back' button at the 'CGIWrap error' message, then try your request again. You can keep doing this til you connect or get fed up. :-)

__
/im

I have been getting it off and on for a couple of days now.

Paul

Got the message 2 times here.
Once Sunday night at approx. 9:30pm EST,
once again last night at about the same time.
I was able to get through both times on my first retry.
Hope this helps.

Debbie

I got the CGI server too busy or something like that several times today.

I got a quick response from the Web Hosting company which has been seeing this CGI Wrap error. They are going to be moving the site to a "Silicon Graphics Origin" machine from the current Pentium Pro 233. The new one promises to be "tons faster" (according to my account rep.)

I expect the move to happen between now and the end of the year. It should not affect visitors in anyway except there will be a brief time when you'll get an "Under Construction" message while the 7,850 files at HL-dot-com and the 4,483 files at LHK-dot-com (Totalling 145 MB!) are moved from one machine to another.

So if when you try to go to these sites in the near future and you see and "Under Contruction" page, don't panic!! [Attn: WACKO's - take note!!]

It just means something faster will be up soon.

John

[This message has been edited by JChidester (edited 12-23-98).]

CGIwrap Error: Server load too high, please try again later.

This is the second day in a row that I have gotten these messages. It gets frustrating but, as previously mentioned, you eventually get in. I'll be glad when the newer/better machine takes over.

Ron

CGI wrap error again today. Happend a few times in a row so I bailed out and checked the Forum later in the day.

Only 145 megabytes? The WACKOS are going to have to get busy. LOL

Tons faster - wow - I can't weight. Hopefully they'll change the gearing of the hard disks too, giving the site a better newton/meters ratio. You'll know it when you log-on if you really get pushed back in your chair.

Rgds,
Peter Torque

[This message has been edited by JTimothyA (edited 12-27-98).]

I was a victim of the "CGI wrap error" several times again today!

"CGI wrap strikes again at around 8:10PM EST.I merely re-clicked and it went through the second time. First time it happen to me.jake

Thanks everyone. We should have the problem fixed by year's end.

John