[RESOLVED] Weird problem after upgrade.
 

I upgraded my vB4 today to most current version and have been experiencing some very weird behaviour by the forum since then. Not just me, my members as well. Any time a topic/thread gets to be 20 posts (total) long when someone posts the 21st post it 'disappears', the thread will show as having 3 pages (20 posts per page) but if you click 'page 3' then page 2 simply reloads, the post shows in the vB_posts table in the d/b, but no matter what we try we can not 'see' the post (or any replies attempted after the 21st one) in the forum.

It's weird because it's ONLY the 21st post, everything works a charm until a thread gets to that point.

--------------- Added 12 Feb 2014 at 01:24 ---------------

new or rather 'last' posts are also not being shown as the last post in a thread on Forum Home, Forum view/sub forum view, nor the Activity Stream.

Try disabling all plugins via the config and wait until someone posts there 21st post

To temporarily disable the plugin system, edit includes/config.php and add this line right under <?php

Maintenance > General Update Tools > Rebuild Thread Information and then Rebuild Forum Information

That helped for the first 15 minutes then things went wonky again. I re-downloaded vB4.2.2, extracted it, and ftp'd all the 'upload' files to my server/forum directory, re-ran upgrade script, deleted 'install' folder from server/forum directory, I have disabled in admincp the forumrunner, panjo, postrelease, cms products & plugins. I ran 'Repair & Optimize' database tables. Then I tried running 'maintenance>general update tools>rebuild threads' and got the following error:
--------------- Added [DATE]1392231168[/DATE] at [TIME]1392231168[/TIME] ---------------

the following are lines 417-431 of the above mentioned file 'includes>class_core.php'

Out of Memory? That is a server issue and you will need to show the error to your host in order for them to fix it.

If you are using a dedicated server you need to configure your my.cnf file among other things.

You may get away with being able to run the counter update though using a smaller amount of posts. i think default is 2,000 at a time. Try like 100 or something. It will take longer but you may have the memory to support it.

I then ran 'rebuild forum information' in general tools, it seemed to do the rebuild but this displays on my general tools page between 'fix broken user profiles' and ''rebuild search index':
.../packages/vbforum/item/socialgroupmessage.php line 261 reads:
.../packages/vbforum/item/socialgroupdiscussion.php line 337 reads:

This is what works best for me though there are a few ways to fix

includes/class_core.php

Find

and add

As found here

http://www.vbulletin.com/forum/forum...81#post4000681

tried this, still getting the error page when I try to run maintenance>general update tools> rebuild thread information =S

That fixes the depreciation issue. Not the issue with being out of memory. For that you need to configure your server or talk to your host.

Are you still seeing

Warning: Declaration of vBForum_Item_SocialGroupMessage::getLoadQuery() should be compatible with that of vB_Model::getLoadQuery() in ..../packages/vbforum/item/socialgroupmessage.php on line 261

Warning: Declaration of vBForum_Item_SocialGroupDiscussion::getLoadQuery() should be compatible with that of vB_Model::getLoadQuery() in ..../packages/vbforum/item/socialgroupdiscussion.php on line 337

1. - GetLoadQuery function edit the files "socialgroupmessage.php" and "socialgroupdiscussion.php" found in "packages/vbforum/item/"

2. - The original function reads:


3. - Change the function to this:

Yeah, that is another way to fix it but the class_core should also do it. I think he is now referring to the database error he gets when rebuilding the post cache but not sure.

just looked at the class_core.php agin should mine, after adding that bit read like this?

if he downloaded a new 4.2.2 the fix in the class_core should already be in there

Made changes, get this when I run rebuild thread info:
error page with:
Warning: mysql_query() [function.mysql-query]: Unable to save result set in ..../includes/class_core.php on line 417

and the out of memory stuff

when I run rebuild forum info it 'runs' but on the tools page this is displayed:
Parse error: syntax error, unexpected ')', expecting ';' or '{' in /home/******/public_html/****/forum/packages/vbforum/item/socialgroupdiscussion.php on line 129


--------------- Added [DATE]1392234956[/DATE] at [TIME]1392234956[/TIME] ---------------

Yes I downloaded vB4.2.2 this morning

Like this I believe

case E_NOTICE:
case E_STRICT;
case E_DEPRECATED;
// Just ignore these completely //
break;

--------------- Added [DATE]1392235055[/DATE] at [TIME]1392235055[/TIME] ---------------

Yeah I thought that too but have installed a couple new sites since and have still had to fix.

--------------- Added [DATE]1392235121[/DATE] at [TIME]1392235121[/TIME] ---------------

Did you make the changes to the socialgroup files too?

I had sent in a ticket to my host and their reply was to optimize my d/b (which I had been doing approx. 10/hour for several hours) and advised to use specific vB 'optimiztion plugins' (which were for vB3.x and I'm running 4.2.2)
I followed the suggestions HERE and made the appropriate changes, saved, cleared cache, tried running general update tools again, and still having issues.

the natives are getting restless as I've had the forum disabled all morning. I'm afraid they may burn me out LOL

What are you using for a host? A shared hosting account? is this a new server you are on or something?

You are using vb3 plug ins on a vb4.2.2 site?

Don't use Yahoo yui. Use Google or nothing in that setting.

As for the rest they are not going to really impact this issue much that happens when rebuilding a database table.

Did you try rebuilding thread/post cache using a smaller amount of posts at a time?

just checked ur right not in there was sure i seen it

it needs to be like this

case E_NOTICE:
case E_STRICT:
case E_DEPRECATED:
// Just ignore these completely //
break;

--------------- Added [DATE]1392235673[/DATE] at [TIME]1392235673[/TIME] ---------------

if you want to send me the 3 files i will make the changes for you but going to bed in 5 mins so be quick

Yes, sir ;)

I'm submitting ticket to host. Same host I've used the past 10 years with only 1 issue as problematic as this one seems to be, so don't suggest changing hosts - these guys have excellent customer service and response times avg. 15 minutes.

--------------- Added [DATE]1392235819[/DATE] at [TIME]1392235819[/TIME] ---------------

Are you still up? I can send the files but where do I send them? Can do so quickly once I know where to send

I think that is what I posted? lol i was scratching my head to see what I messed up.

I think the single class_core should fix it but it will not fix his memory error. only the depreciation warning he is seeing in the maintenance page.

--------------- Added 12 Feb 2014 at 15:11 ---------------


So the only change you made was upgrading to Vbulletin 4.2.2? Are you sure you uploaded all the files correctly and have permissions set?

You can also optimize the database using phpmyadmin and then try to run the counter. The memory issue is not being caused by the depreciation warnings. The issue is that some of your posts are very, very large and this is causing you to go over your memory allocation.

you had ; after
case E_STRICT;
case E_DEPRECATED;

should be
case E_STRICT:
case E_DEPRECATED:

Ahh, I see now. :eek: Thanks, I thought I was losing my mind. I just may have been right too. lol

I have always done it that way seems to fix the problem. Maybe a good coder could answer that

yeah, actually I am looking at the post where i got that from and it appears it is the way I was using it. This is the way I have been doing it on at least 7 or 8 sites and it has resolved the warnings. I have done the social group file edits as well at times. That is probably the better way to fix it as it is stopping the issue causing the warnings where the clas_core is just ignoring them. I am not sure if it matters though in any noticeable way.

http://www.vbulletin.com/forum/forum...81#post4000681

seen that, have no idea where i got my one from but it does work

All is well that ends well :) . Apparently they both work. Now we need an expert coder to come in and explain why. :D

Shared server, been with host for 10 years............ on save server for last 5 or more, host recently did all kinds of upgrades too.
no I am NOT using vB3 plugins on my vB4.2.2 site - that is what tech support pointed me to - certain optimization tools that I can't use
I have it set to Google, it WAS the Yahell but I changed it earlier today.

Did you run the repair/optimization using phpmyadmin?

Yup and Yup to your first questions
And yes, I've been optimizing via vB admincp AND phpMyAdmin.
there are some very large posts, I may have to go in and split them into several if this is the case. Just never had a problem until this upgrade. =S

Then again you probably have not had to rebuild the post/thread cache often either. I am not sure how to resolve the error problem if you are getting it even when updating a small amount of posts per time.

I think you need to upgrade your hosting package.

I would not use the nix setting.

I don't use the nix setting
I've rebuilt thread and forum info after every upgrade, last one was October(? i think) (and there was NO posting after October - place is more or less private for me and a few friends, we just started posting again the last 2 or 3 days) before the one I did yesterday and then repeated today.

--------------- Added [DATE]1392240735[/DATE] at [TIME]1392240735[/TIME] ---------------

my 'other' vB4 site (same host but a different shared server) has none of these problems

It appears that your account does not have enough memory allocated to allow to run this process. On a dedicated server I would tweak my.cnf and php.ini but on a shared host I am not sure how you can solve this.

It looks like your host has you limited to 8 mb of memory and you need at least 16. Even 16 is very, very low for a vbulletin site. Perhaps this was something the host changed with the server updates. See if they will change it to 64 at least.

--------------- Added [DATE]1392243031[/DATE] at [TIME]1392243031[/TIME] ---------------

You can also go into maintenance and phpinfo and see what your memory limits are.

Thanks, Richie, I'll go check that... my plan is supposed to be 'unlimited' =S

--------------- Added 12 Feb 2014 at 19:26 ---------------

from maintenance>phpinfo:
PHP Version 5.3.28
Directive | Local Value | Master Value
memory_limit | 128M |128M

Your memory is fine in terms of php but your host needs to tweak your mysql configuration(my.cnf) if is maxing out so low and then restart mysql.

I don't think any shared host could give you unlimited memory though many offer free bandwith and storage.

Your host needs to tweak these in my.cnf

sort_buffer_size
read_buffer_size
read_rnd_buffer_size
join_buffer_size
max_connections

I sent them that message, Richie. LOL. They better love me ;)
Anyway from cPanel I garnered these numbers:

CPU Usage 0 / 100 %
Virtual Memory Usage 0 / 1024 MB
Physical Memory Usage 10.6 / 1024 MB
Entry Processes 0 / 15
Number of Processes 0 / 100
I/O Usage 0 / 1 MB/s
Disk Space Usage 10,039.21 / ∞
Monthly Bandwidth Transfer 535.45 / ∞

Do they tell you anything?

I was just looking for an idea of your server specs. This info doesn't show your mysql settings but it looks like they treat you decently in terms of memory. Hopefully they will tweak the database too.

Well they've been doing *something* to it, it's acting crazier than ever, not allowing 90% of the posts attempted - about 1 in 20 actually posts now; they did escalate my ticket but I'm not holding my breath.

The fixes I gave you did they help

I guess not =S this is what I get when I click 'submit post':
https://vborg.vbsupport.ru/external/2014/02/19.png