A user has sent me the below error. I haven't been able to duplicate it yet. But the board is really slow. Check it out here. Note we just updated from 5.47e and launched around 2:15 EDT today...
Sorry, UBB has encountered an unexpected, fatal error. This error is extremely abnormal. Please contact the board administration. The error text is: [PARA]/home/DocumentRoots/Default/ubb/Forum1/forum_1.threads: Expected to write out 89334 bytes, but file on disk is only !][PARA]Here is the backtrace: [PARA] Backtrace: ubb_lib_filehandle.cgi:178 -> sub UBB::FileHandle::tracer [PARA] Backtrace: ubb_lib_filehandler.cgi:132 -> sub UBB::FileHandle::close [PARA] Backtrace: ubb_lib_files.cgi:411 -> sub UBB::FileHandler::close [PARA] Backtrace: ubb_lib_files.cgi:65 -> sub main::WriteHashToFile [PARA] Backtrace: ubb_lib_posting.cgi:145 -> sub main::UpdateForumTopics [PARA] Backtrace: ubb_new_reply.cgi:469 -> sub main::update_forum_summary [PARA] Backtrace: ultimatebb.cgi:696 -> sub main::submit_new_reply
This should not occur with 6.1.0.1 unless the .threads file really did write out to zero size..
The slowness you're noticing is somewhat normal for the upgrade, for the time being, at least. I would advise asking your host to install PHP so you can take advantage of the UBB Accelerator...
Your board is pretty big - you might also want to consider moving to UBBThreads.
-- Charles Capps Programmer, Infopop Corporation Please do not contact me privately for support - post on the board or open a support ticket instead!
I just got a similiar email message from a user. I'm running 6.1.0.2 for about 6 days after upgrading from 5.47a. Do I need to do anything?
Quote
FYI Sorry, UBB has encountered an unexpected, fatal error. This error is extremely abnormal. Please contact the board administration. The error text is: /home/ibsgroup/public_html/ubb/cache-2SEL4S8N/ubb_files/summary/summary.html : Expected to write out 68641 bytes, but file on disk is only !] Here is the backtrace: Backtrace: ubb_lib_filehandle.cgi:178 -> sub UBB::FileHandle::tracer Backtrace: ubb_lib_filehandler.cgi:132 -> sub UBB::FileHandle::close Backtrace: ubb_lib_files.cgi:522 -> sub UBB::FileHandler::close Backtrace: ubb_forum_summary.cgi:93 -> sub main::WriteFileAsString Backtrace: ultimatebb.cgi:535 -> sub main::forum_summary » Please use your browser's back button to return
Sorry, UBB has encountered an unexpected, fatal error. This error is extremely abnormal. Please contact the board administration. The error text is:
/home/DocumentRoots/Default/ubb/cache-UHVBCNQ7/ubb_files/summary/summary.html: Expected to write out 44248 bytes, but file on disk is only !] Here is the backtrace: Backtrace: ubb_lib_filehandle.cgi:178 -> sub UBB::FileHandle::tracer Backtrace: ubb_lib_filehandler.cgi:132 -> sub UBB::FileHandle::close Backtrace: ubb_lib_files.cgi:522 -> sub UBB::FileHandler::close Backtrace: ubb_forum_summary.cgi:93 -> sub main::WriteFileAsString Backtrace: ultimatebb.cgi:536 -> sub main::forum_summary
We have the disc space...but it stopped happening as soon as I clicked on the forum home link...
FYI Sorry, UBB has encountered an unexpected, fatal error. This error is extremely abnormal. Please contact the board administration. The error text is:
Out of memory during large request for 69632 bytes at /opt/httpd/Apache/1.3.12/cgi-bin/ubb_lib_filehandle.cgi line 428.
» Please use your browser's back button to return.
Only happens on Forum1. I pruned out 10,000 threads on Friday. What else can we do? I did re-index it on Friday. Should I re-index again? Is there a way to re-index on a forum by forum basis?
That would mean we'd have to pay our Sys Admin to install PHP and configure MySQL--and pay for the upgrade. Not even sure if it'd work in our current content management system which has Vignette Story Server working with Sybase.
Plus that'd mean I have to learn PHP & MySQL--which isn't a bad idea, but for the immediate future we--or I--don't have the time/resources to pick up another skill set...
Recall we were having a problem with runaway UBB processes. I put a limit in place which restricted each UBB process to a maximum of 50M of memory use.
This was being exceeded.
I've increased the limit to 75M, and the search is working.
ooooof... Vignette?? You may want to inform your company that even if they got Vignette for free, they still got reamed.
I've used Vignette. I hate Vignette with a passion. The software is utter crap. Documented features do not work, stuff literally just stops working for no reason (I'm dead serious...as a programmer I've been saying for years "code doesn't just stop working". It absolutley does with Vignette....I've seen it happen 4 times).
I've actually had Vignette's DATE_FORMAT command break on me...working fine, then one day just break. Patches that are released never work correctly, and often break things previously working.
The documentation is piss-poor. I've even cut and paste stuff right from the documentation into a template and gotten syntax errors for it.
As you can tell, I hate it. Your company would be far better off using a content system like Mason, which is Open Source. Vignette is far more trouble than it is worth.
Glad I do not have to use it any more. The company I worked for made a huge mistake in purchasing it. They finally agreed when a coworker and myself built a duplicate version of the site, on our desktop, using php and showed the boss the MASSIVE (like order of magnitude) speed increase...
Originally posted by Mark Badolato: ooooof... Vignette?? You may want to inform your company that even if they got Vignette for free, they still got reamed.
I've used Vignette. I hate Vignette with a passion. The software is utter crap. Documented features do not work, stuff literally just stops working for no reason (I'm dead serious...as a programmer I've been saying for years "code doesn't just stop working". It absolutley does with Vignette....I've seen it happen 4 times).
I've actually had Vignette's DATE_FORMAT command break on me...working fine, then one day just break. Patches that are released never work correctly, and often break things previously working.
The documentation is piss-poor. I've even cut and paste stuff right from the documentation into a template and gotten syntax errors for it.
As you can tell, I hate it. Your company would be far better off using a content system like Mason, which is Open Source. Vignette is far more trouble than it is worth.
Glad I do not have to use it any more. The company I worked for made a huge mistake in purchasing it. They finally agreed when a coworker and myself built a duplicate version of the site, on our desktop, using php and showed the boss the MASSIVE (like order of magnitude) speed increase...
Well I do agree that it is overpriced and they do sell you on a lot of features. But the big picture is that you really need MINIMALLY a 3-person team: DBA, Lead Template Developer & a Sys Admin that doubles as a template developer.
But I find your PHP comments comical. I mean, puhlease, do you really think PHP/My SQL is scaleable for hundreds of thousands of users (forget millions for now)? Can you honestly say that (if you had the resources) 5 people could simultaneously design and code templates and put them through a QA/workflow? And how about designing a CMA that dozens of editors (around the world who have limited or no HTML experience) could upload content and again put through a workflow where cetain users had different privileges, e.g., upload content, edit, launch? And how about the caching ability? You can cache (more efficiently that PHP) "libraries" and components and different parts of pages, e.g., nav bar, regularly used images, etc.
And how about the ability to place the sme article in different areas of a site? For instance, a guitar feature could also apply as a bass feature and could also be related to a keyboard review since there's a matching category/keyword pair?
Or how about the ability ro launch a new site in a week's time (keeping a similar design/layout) and being able to use an article that was already in the CMS and be able to populate content at the click of a button?
Don't get me wrong--this stuff doesn't happen overnight. It takes weeks--our months to get in place. I've done my share of Vignette-bashing too...as always there's 2 sides to every story.
And BTW, our sister company started building a CMS off of Mason, but it was just as expensive to build/support for!!!
I'm really surprised you didn't mention the other standards that have taken off: XML and Java. That's where things have been going for a while now. And guess what? XML, Java (JSP) and ASP are now compatible with Vignette...how do you like them apples?
I didn't say PHP was the solution to go, I said that a quick PHP version of the site that mimicked the Vignette setup was far, far faster.
We had a 3 person Sysadmin team, an Oracle DB, 3 different consultants from Vignette, and our programming team working on the system for months. It never ran correctly. It never did what it was supposed to.
It was the slowest, buggiest, piece of crap out there. No I'm not saying a PHP solution is better, I'm just saying that Vignette is not a solution.
It was so bad that we couldn't patch it because the patches would render the site useless and need to be backed out. Then support woudln't assist because we didn't have the latest patches. It was unreal...
Personally, I'm glad to see their stock tanked. They were hyped up as THE system to have, and it was nothing more then marketing hype...the product sucked.
If someone offered me $100 an hour for a Vignette job, I would probably turn it down.
Moderator for Unix Installation and HTML/CGI.<p>"Look! A wagon wheel!" --Time For Timer
This isn't your thread, ibsgroup. <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" />
Nevertheless, the error and the cause is the same. UBB's written a file that isn't there when it goes to look for it, so it freaks out and throws the error.
-- Charles Capps Programmer, Infopop Corporation Please do not contact me privately for support - post on the board or open a support ticket instead!
I'm running a dedicated server so I'll have a look at the maximum memory per process however I am running vanilla RedHat 6.2. Could this have anything to do with Php? Should I check out php.ini?
I'm getting a couple of these on 6.1.0.2 running under Windows 2000 with ActiveState Perl.
--- Undefined subroutine &main::floodcheck called at C:/Inetpub/bbs_root/cgi-bin/ubb_registration.cgi line 266. ----
Sorry, UBB has encountered an unexpected, fatal error. This error is extremely abnormal. Please contact the board administration. The error text is:
I got error 'No such device or address' while SHlocking C:/Inetpub/bbs_root/ubb/cache-27KGQYGU/lock/global.cgi
Here is the backtrace: Backtrace: ubb_lib_filehandle.cgi:105 -> sub UBB::FileHandle::tracer Backtrace: ubb_lib_filehandler.cgi:113 -> sub UBB::FileHandle::relock Backtrace: ubb_lib_files.cgi:833 -> sub UBB::FileHandler: pen Backtrace: ubb_lib.cgi:1091 -> sub main: penProfile Backtrace: ultimatebb.cgi:434 -> sub main::verify_id_num_2
You can't tell me there isn't a bug here somewhere. Just happened again to another user:
Quote
/home/ibsgroup/public_html/ubb/Forum3/forum_3.threads: Expected to write = out 63444 bytes, but file on disk is only !] Here is the backtrace:=20 Backtrace: ubb_lib_filehandle.cgi:178 -> sub UBB::FileHandle::tracer=20 Backtrace: ubb_lib_filehandler.cgi:132 -> sub UBB::FileHandle::close=20 Backtrace: ubb_lib_files.cgi:411 -> sub UBB::FileHandler::close=20 Backtrace: ubb_lib_files.cgi:65 -> sub main::WriteHashToFile=20 Backtrace: ubb_lib_posting.cgi:145 -> sub main::UpdateForumTopics=20 Backtrace: ubb_new_reply.cgi:469 -> sub main::update_forum_summary=20 Backtrace: ultimatebb.cgi:709 -> sub main::submit_new_reply=20
Could not perform buffered print() to '/www/boxingfanatics/ubb/cache-LEBZ4M67/ubb_files/summary/summary.html', handleglob is 'GLOB(0x8375f50)', error returned by OS is: 'Quota exceeded', length of print requested is: '10574', backtrace is: Backtrace: ubb_lib_filehandle.cgi:434 -> sub UBB::FileHandle::tracer Backtrace: ubb_lib_filehandle.cgi:118 -> sub UBB::FileHandle::__ANON__ Backtrace: ubb_lib_files.cgi:521 -> sub UBB::FileHandle::print Backtrace: ubb_forum_summary.cgi:93 -> sub main::WriteFileAsString Backtrace: ultimatebb.cgi:535 -> sub main::forum_summary
