vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.8 Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=235)
-   -   Board Optimization - [DBTech] vB Optimise 2.0.1 (Lite) (https://vborg.vbsupport.ru/showthread.php?t=199207)

thcf 06-28-2009 10:03 AM

very sad to see the author of this script has vanished

i was the biggest donator for this mod, and i wont ever be making a donationa again!

yeshoward 07-01-2009 12:46 AM

We are using APC method with PHP5.2.9
We also find that template is NOT updated after changes

DID click "flush cache" on Vbadmin
DID go to apc.php to flush APC cache
DID re-install module

none of this is working....

btks1995 07-23-2009 04:05 AM

Everytime I add new user infraction levels, they go blank?? Any ideas.. thanks

Deceptor 07-23-2009 05:38 AM

It'll be to-do with phrases. Ideally the phrase cache here is unfortunately not solid so I'd recommend disabling it if you come across errors/issues/etc. The other caches available should be no problem though :)

Sephirot 07-23-2009 03:25 PM

I recently got the following error
Code:

[Thu Jul 23 17:45:00 2009] [error] [client XXXX] PHP Fatal error:  Maximum execution time of 240 seconds exceeded in /srv/www/htdocs/vbulletin/includes/class_activecache_methods.php on line 355, referer: XXXX
PHP Code:

    function set($title$item)
    {
        if (!
$this->connect())
        {
            return 
false;
        }

        
$this->set_title($title);

        if (
trim($item) == '')
        {
            
$item '{_______VB_ACTIVE_CACHE_BLANK_______}';
        }

        
eaccelerator_rm($title); // this is the line from the error log
        
eaccelerator_put($title$item);
    } 

Any ideas about the cause?

Deceptor 07-23-2009 08:20 PM

eaccelerator_rm() attempts to remove the item from the shared memory, I've never seen it fail before. Is the error still occuring? I can't seem to find any where else this has happened with eAccelerator.

Artes_Marciales 07-24-2009 12:41 PM

Thanks for the mod!!

kmike 07-24-2009 03:33 PM

There is no need for calling eaccelerator_rm() there, eaccelerator_set() takes care of replacing the older value with a new one. That being sad, it's extremely strange that PHP timed out on that call, it simply shouldn't happen.

The only possible cause I could think of is that maybe eAccelerator is set to cache everything on disk, and the disk I/O was blocked for some reason, and thus eAccelerator couldn't remove the old value.

Deceptor 07-24-2009 04:07 PM

Quote:

Originally Posted by kmike (Post 1854702)
There is no need for calling eaccelerator_rm() there, eaccelerator_set() takes care of replacing the older value with a new one. That being sad, it's extremely strange that PHP timed out on that call, it simply shouldn't happen.

The only possible cause I could think of is that maybe eAccelerator is set to cache everything on disk, and the disk I/O was blocked for some reason, and thus eAccelerator couldn't remove the old value.

It seemed like a best practice at the time really, and with the API on eAccelerator being fairly vague and the function appearing to do no harm (until this odd situation) I figured better to be safe than sorry. If it keeps happening for the user they can comment the line out, but honestly that may just be ignoring the problem as it seems to be a lot deeper.

Sephirot 07-24-2009 09:23 PM

Quote:

Originally Posted by Deceptor (Post 1854328)
eaccelerator_rm() attempts to remove the item from the shared memory, I've never seen it fail before. Is the error still occuring? I can't seem to find any where else this has happened with eAccelerator.

No it did not happend again after that day. It seems to be a very rare case.
I reduced the shm_prune_period and shm_ttl from 3600s to 1800s.

Quote:

Originally Posted by kmike (Post 1854702)
There is no need for calling eaccelerator_rm() there, eaccelerator_set() takes care of replacing the older value with a new one. That being sad, it's extremely strange that PHP timed out on that call, it simply shouldn't happen.

The only possible cause I could think of is that maybe eAccelerator is set to cache everything on disk, and the disk I/O was blocked for some reason, and thus eAccelerator couldn't remove the old value.

eAccelerator is set to use both, shared memory and disk (default). Maybe I should set it to "shm", which causes eAccelerator to use the disk only if the shared mem is full?


All times are GMT. The time now is 08:31 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02094 seconds
  • Memory Usage 1,747KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_code_printable
  • (1)bbcode_php_printable
  • (3)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (4)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete