Bug xcache.var_size is either 0 or too small

[MaxLiao]

I have installed vBulletin Optimize (Lite) in preparation to upgrade to the Pro version (once I get Lite working).

I have read through various forums here, which were helpful in allowing me to manage the configurations (either by myself or via my host), but I am still running into the following errors:

• Warning: xcache_get() [function.xcache-get]: xcache.var_size is either 0 or too small to enable var data caching in[path]/dbtech/vboptimise/includes/operators/xcache.php*on line*23
• Warning: xcache_set() [function.xcache-set]: xcache.var_size is either 0 or too small to enable var data caching in[path]/dbtech/vboptimise/includes/operators/xcache.php*on line*40

Here is my PHP info:


Lastly, I do have xcache.admin.enable_auth configured in my PHP.ini file as
xcache.admin.user = "removed"
; paste the output of md5("password") below
xcache.admin.pass = "MD5_hash_removed"

I verified that the username and password (in clear text, not MD5 hash) was applied in /dbtech/vboptimise/config.php, and that the XCache Authentification was turned on in the vB Optimize admin settings.

Thanks up front for your assistance.

 

[Fillip H.]

According to the second Google search result for "xcache.var_size is either 0 or too small to enable var data caching" ( php - Xcache var_size error - Stack Overflow ) the following could be a potential solution:

Running the php info showed that xcache was being loaded twice. Once from the php.ini and then an xcache.ini. I removed the xcache.ini (copied it to .old) and restarted apache and error went away.

 

[MaxLiao]

Okay, I'll look into that. Thank you!! :RpS_biggrin:

I'll post the result as soon as I have one.

---

However, I'm not going to try and use Google as my reference for troubleshooting - unless it directs me specifically to something that says 'vBulletin, xCache, and vB Optimize' all in the same area. I'm not strong in server administration and I'm not going to risk doing something that may work for Joomla!, a specialized server build, or for some other application at the risk of mine. I did a cursory Google search, but that's all I was comfortable doing.

On the other hand, I did spend a bit of time here, on the DragonByte Tech forums, and made various server/PHP.ini configuration changes based on the information given to other users in this forum. As always, the information posted on this site helped me tremendously - (thank you, again!!). If not for the information found here I'd have posted sooner, and would have had to work through other issues even before getting to this point. I find you guys responsive, accurate, and helpful - which is why I keep buying your mods - but pointing me to Google, even if it wasn't meant to be insulting or an attempt to call me lazy - really irks me.

Precisely because I am weak in server administration, that Stack Overflow page basically tells me nothing. Maybe I should be able to glean all of the issues and resolve them from that post, but I can't. Just as I can read enough French, Russian and Japanese to get a vague idea of what's going on, I'm not fluent in any of them and would never attempt to translate it if something could go wrong. The same holds true for me regarding server lingo.

Thank you for your understanding; and if *I* am misunderstanding the intent, you will receive an apology from me.

 

[Fillip H.]

I didn't mean to imply you're being lazy, I do apologise for it coming off that way

Generic PHP errors like that are system-independent - that is to say, it's possible the reason why an error varies by system (as that thread showed, there were multiple ways XCache could accidentally be loaded twice), but the actual error message will always mean the same thing on all systems.

The reason why I linked a thread and pointed out that I found it on Google is that if you had created a script like so:

<?php xcache_set('test', 'Test!');

you would have received the exact same error - I was meaning to illustrate that the issue was in fact not with vBOptimise, others have the same issue in entirely unrelated scripts.

You have absolutely nothing to apologise for, I completely see how it could have been taken as me saying "shoulda googled it, dumbdumb!" and I'm entirely at fault for wording it that way


Sometimes I wish I had your cautionary stance for trying to fix server issues myself, you would need to be a centipede to finger-count the number of fires I've caused by applying the first "fix" I found while searching

 

[MaxLiao]

As always, I appreciate your follow up. Whenever I can learn something I'm happy, and you did dun edjumakated me.

I will apologize anyway - this seems to be a simple misunderstanding and I may have take it a bit too personally. Typing on the Interwebs can be perilous. So, for this misunderstanding you have my apologies.

Now ... moving on ...

My host did make this change for me:

root@***** [~]# *****/***/***/*****/xcache-1.2.1/xcache.ini /***/*****/xcache-1.2.1/xcache.ini_OLD
root@***** [~]#

Please check and let us know if you need any further assistance.

And I still received the same errors when I turn the mod on. They have asked for admin access to my site to troubleshoot; however, if my host's troubleshooting efforts don't work, would you be willing to take a look? I know this is the free version, but I promise you that once this is working properly I am purchasing Pro.

 

[Fillip H.]

Did they restart Apache afterwards? I can't tell from their log entries if they did - that would be required.

I've attached some test scripts - if you upload them and run them in order, you'll know it's working when the second script says "Working!". That way, you don't have to crash your forum while you're testing it out and your host can be secure in the knowledge it's not an issue with vB/vBO

 

[MaxLiao]

LOL! They switched me to memcache.

See, I'm never allowed the good things in life, but memcache is better than nothing.

I have installed the another cache mechanisms memcache which worked fine. I have included screen shots for the same.

Please check and let us know if you need any further assistance.

Also the xcache and apc has been disabled on your server.

Everything seems to be working, so thank you for the help. If things are still good in a week or so I'll be grabbing the upgrade.

 

[MaxLiao]

This is just getting crazy. memcache wouldn't work - the Fetch Cache test continually failed - so the host switched to APC. They sent me a screenshot of APC working just fine; however, when *I* ran the test the Fetch Cache failed.

I am sooooo confused. I have changed nothing, in fact I did nothing more than their message then run the System Test, but my test failed. Is there a reason it would succeed once then fail thereafter?

The two website.jpg and website3.jpg are from the host, apc cache test.jpg is mine.

 

[Fillip H.]

What's the output of the test scripts linked to you in the error message?