WordPress.org

Ready to get started?Download WordPress

Forums

P3 (Plugin Performance Profiler)
[resolved] installed P3 now I can not access dashboard (9 posts)

  1. khunjohn
    Member
    Posted 1 year ago #

    I had just uploaded your plug in and selected the activate option. After clicking on activate the page received a http 500 error and I am now locked out of my dashboard.

    My site is currently on maintenance and I can view the website when logged in as admin, I can see the black admin bar but if I select any of the options on the bar, I receive the server error.

    Server error
    The website encountered an error while retrieving http://website.com/wp-admin/index.php. It may be down for maintenance or configured incorrectly.
    Here are some suggestions:
    Reload this web page later.
    HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfil the request.

    http://wordpress.org/extend/plugins/p3-profiler/

  2. Kurt Payne
    Member
    Plugin Contributor

    Posted 1 year ago #

    First, get your site back up! There are two ways to do this. Try the emergency shutoff switch first. If that doesn't work, delete the plugin files.

    Emergency Shutoff Switch

    Visit yoursite.com/wordpress/index.php?P3_SHUTOFF=1

    Delete the Plugin Files

    Delete wp-content/plugins/p3-profiler (the whole folder)
    Delete wp-content/mu-plugins/p3-profiler.php (if it exists)
    This can happen if P3 hits the memory limit on your server while it's running. This happens most often on sites with many active plugins or a complex theme. Consider switching to the Twenty Eleven theme or deactivating a few plugins before re-running P3.

  3. khunjohn
    Member
    Posted 1 year ago #

    Thank you Kurt,

    The Emergency shutoff didnt work but I was able to delete the files via ftp.

    Thank you for your help!

  4. cplummer4
    Member
    Posted 1 year ago #

    FYI, I tried to get this plugin working on three separate occasions. I'd have to immediately deactivate it due to 500 internal server errors. I finally got around to cloning my production machine to another server. After much tinkering I was able to figure out that the www pool for php-fpm was crashing:

    tail -f /var/log/php-fpm.log
    WARNING: [pool www] child 2895 exited with code 1 after 34.515471 seconds from start

    My solution was to disable APC during profiling:
    vi /etc/php.d/apc.ini
    apc.enabled=0
    service php-fpm restart

    After that I was able to run the profiler without it crashing, albeit slower. However I was able to obtain accurate results which I then used to make changes on my production server that I had cloned.

  5. Kurt Payne
    Member
    Plugin Contributor

    Posted 1 year ago #

    Did you try profiling with APC enabled, but without "disable opcode optimizers"? This may give you skewed results (e.g. a pie chart that only shows P3 and no other plugins) but I'm curious if it stops the 500 error you're seeing.

  6. cplummer4
    Member
    Posted 1 year ago #

    Yes that did work. I re-enabled APC, and for the profiler I unchecked the option "Attempt to disable opcode optimizers (recommended)" under Advanced Settings. I did not get any strangely skewed pie chart, however the chart results were slightly different.

    Question, when P3 profiler is first activated, does it automatically start a scan if one does not already exist? If so, I would turn off that feature and let the user trigger when to scan. I say this because my first several experiences with this plugin was that after activating the plugin my site immediately went down.

    I would also recommend only install this plugin on a non-production server.

  7. Kurt Payne
    Member
    Plugin Contributor

    Posted 1 year ago #

    Question, when P3 profiler is first activated, does it automatically start a scan if one does not already exist? If so, I would turn off that feature and let the user trigger when to scan. I say this because my first several experiences with this plugin was that after activating the plugin my site immediately went down.

    P3 does not run until you click "Scan Now" then "Auto Scan" or "Manual Scan."

    If APC + P3 was problematic, then it appears the conflict is in this code:

    @ini_set( 'apc.optimization', 0 );
    apc_clear_cache();

    Can you supply your versions of php and APC? I'll see if I can recreate it.

  8. Dr Kin
    Member
    Posted 1 year ago #

    Hi,
    I think there is a conflict between P3 Plugin profiler and code canyon's 3c Calendar. When the later is activated, the scan button disappear and it is impossible to complete a scan.
    Love your plugin!
    Thanks for adressing this issue.
    Maxime

  9. Kurt Payne
    Member
    Plugin Contributor

    Posted 1 year ago #

    Hi Dr Kin,

    This is most likely a jQuery UI conflict. Please see this post for more information about a jQuery UI conflict in another plugin.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.