UBB.Developers Forums UBB.threads 7 Development How Do I? i guess this be the right forum

the server running our ubb today crashed and we was meant to be the cause of it as were the only clients on that server at the moment

so far all i can post is the log from our tech support guys as i cant get any more info at this time

DPrincetonNOC: yeah you overloaded the whole server the load was 99.00 before it booted me out of ssh
wnxwakko: really
DPrincetonNOC: you were the only clients on that server
DPrincetonNOC: yeah
DPrincetonNOC: did you add any hacks to UBB lately
wnxwakko: hmm we only showed 25 online when it went down which is alot lessthan normal
wnxwakko: lately no
wnxwakko: last hack added was maybe 2 weeks ago or more
DPrincetonNOC: that had to be the problem
wnxwakko: but it was only an update of next version
DPrincetonNOC: it spawns to many apche processes and doesnt close them
DPrincetonNOC: their new versions neve work right
DPrincetonNOC: they forger to use the garbage collection built into perl
wnxwakko: we upgraded from 6.3 to 6.3.0.1
wnxwakko: we dont use the garbage collection hack
DPrincetonNOC: no no
DPrincetonNOC: its part of the unix operation system
DPrincetonNOC: nothign to do with UBB
wnxwakko: oh ok
DPrincetonNOC: but we need to get you on a better box ASAP
DPrincetonNOC: any way that you can call the office and speak to

Digital Princeton must be good because when I crashed my server my hosts were going to shut me down.

Feel free to quote this to their techs.

"they forger to use the garbage collection built into perl"

Uh, Perl does automatic garbage collection. The DESTROY routines are there to make sure that everything is done CLEANLY.

If they'd bother to look into the exact cause of the problems, they'd find the same exact deadlock in Recent Visitors that we've known about for months now.

If the lockups continue, I would advise simply turning off Recent Visitors while we continue to search for a solution to the deadlock.

thanks for the quick responce
ill pass tis on to them
but they say were also being moved to a better server to handle the ubb better
so ill find out how we run there

thanks again

It seems that the Cobalt Raq servers have an issue with the newer versions of UBB. I hate to say it but I've not heard many good things about the Raq's.

All Cobalt RaQs have issues with the UBB. They are not a recommended platform due to very poor I/O speed. I/O speed is the major UBB bottleneck. Slow I/O + many requests -> a heavily loaded server -> slower I/O -> more requests due to speed -> more load -> slower I/O -> etc, etc...

The instant that things start to get out of synch due to delayed I/O, PNTF throws a fit and the deadlock as mentioned above occurs.

That explains a lot.

Sure would have been nice if I'd read this thread before I turned Recent Visitors on. With an average of between 100-150 visitors on line at all times, it took less than 24 hours to overload my server and take the whole freakin' thing down. Yep... they are REAL happy with me right now!

So how come no warnings came with this or it wasn't more broadly publicized/advertised that this might be an issue? I have over 2000 members who are just a tad bit miffed right now... and I gots lots of 'splainin' to do.