Opened 8 years ago

Closed 7 years ago

#81 closed defect

vbulletin 3.6.4 / 3.6.5 rare fatal errors viewing threads w xcache 1.0.3

Reported by: vissa Owned by: moo
Priority: major Milestone: 1.2.2
Component: cacher Version: 1.2-dev
Keywords: xcache vbulletin Fatal error Cc:
Application: vbulletin PHP Version: 4.4.5
Other Exts: SAPI: FastCGI
Probability: Rare Blocked By:
Blocking:

Description

Vbulletin 3.6.4 (security patched)
RHEL4
php 4.4.5
xcache 1.0.3 (compiled from source -- you are missing this version in your ticket dropdowns)

Overall xcache is running excellent. However, I have had sporadic reports of users getting the following error when clicking a thread after using "new posts." I have also seen reports of this at vbulletin.com.

Fatal error: Direct instantiation of vB_Postbit class prohibited. Use the vB_Postbit_Factory class. in /includes/class_postbit.php on line 239

Here is a link of other reports of this error at vbulletin.com
http://www.vbulletin.com/forum/showthread.php?t=215068

I also noticed when upgrading from vb 3.5.3 to 3.6.5 on another forum that there were some problems during the upgrade that never happened before xcache. May be unrelated. I had to disable xcache for moodle on one site (I'll make another ticket for that).

Change History (7)

comment:1 follow-up: Changed 8 years ago by judas_iscariote

  • Milestone set to 1.2.1
  • Version set to 1.2-dev

Please DO NOT use 1.0.3 as it is deprecated !! however I can reproduce your problem with 1.2-dev too with php 4.4.6.

comment:2 in reply to: ↑ 1 Changed 8 years ago by vissa

Replying to judas_iscariote:

Please DO NOT use 1.0.3 as it is deprecated !! however I can reproduce your problem with 1.2-dev too with php 4.4.6.

Thank you for confirming and replicating.

Your reply confuses me. The Download page http://trac.lighttpd.net/xcache/wiki/ReleaseArchive itself says 1.0.3 is the version to get for php4 for "stability." Is this no longer true? And if that is a release version, why is there no dropdown/option for 1.0.3 in the ticket system? Does 1.2 fix anything wrong with 1.0.3 or is it about performance enhancements? How much performance will I lose if I turn off "optimizer" to see if that is causing problems -- or is that not really doing anything (hard to find these details here).

comment:3 Changed 8 years ago by moo

  • Status changed from new to assigned

i'm tracking down the vB_Postbit problem, but moodle problem should have been fixed, in 1.2.0 IIRC

comment:4 Changed 7 years ago by moo

  • pending set to 1
  • SAPI set to FastCGI

can anyone reproduce it in php 4.4.7 + XCache-1.2.1-rc2 ?

comment:5 Changed 7 years ago by moo

  • Milestone changed from 1.2.1 to 1.2.2

comment:1 follow-up: Changed 7 years ago by trac-robot

  • pending changed from 1 to 0
  • Status changed from assigned to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 28 days.

Note: See TracTickets for help on using tickets.