I’m running the latest EP Lite/Participad/WP and they all run fine independently, but once you enable the Participad plugin with EP lite running WP just hangs indefinitely. No errors are shown, but the PHP process runs at 100% for the entirety of the page load. I’d love to be able to get you something to be able to replicate it but it’s a brand new bog standard set up – WordPress Multisite 3.5.1, BuddyPress + Participad. Do you have any ideas where I could check what’s going on? EP, nginx and php-fpm don’t show anything in their logs regarding a problem.
Check your error logs. Are you getting a huge number of requests to the EPL endpoint?
Unfortunately there’s nothing in either the nginx or EPL access logs. EPL just shows the flushed values and nginx shows nothing until the timeout hits. CPU usage is at 100% whilst this is happening.
What’s the very last thing that happens before the hang? Is clicking the Activate button on the plugins page? If you’re not currently logging all nginx requests, temporarily turn them on, to see what the very last HTTP request is before the system hangs. That’ll at least help to narrow it down.
I already have it enabled, but I’m starting and stopping the EPL instance as and when. The logs below are from visiting /wp-admin/post-new.php
Here’s the full debug error log from nginx if it’s any use – http://c.ed.gs/OeG6/nginx-error.log
Here’s a sample of the EPL log, it is just flushing values and collecting garbage though:
[2013-04-29 17:16:21.198] [INFO] ueberDB - Flushed 57 values [2013-04-29 17:16:21.298] [INFO] ueberDB - Flushed 55 values [2013-04-29 17:16:21.880] [INFO] ueberDB - Flushed 65 values [2013-04-29 17:16:21.890] [INFO] ueberDB - garbage collected 500 values [2013-04-29 17:16:24.940] [INFO] ueberDB - Flushed 26 values [2013-04-29 17:16:26.441] [INFO] ueberDB - Flushed 15 values [2013-04-29 17:16:26.951] [INFO] ueberDB - Flushed 10 values [2013-04-29 17:16:28.455] [INFO] ueberDB - Flushed 18 values [2013-04-29 17:16:29.951] [INFO] ueberDB - Flushed 17 values [2013-04-29 17:16:31.453] [INFO] ueberDB - Flushed 17 values [2013-04-29 17:16:32.441] [INFO] ueberDB - Flushed 18 values [2013-04-29 17:16:34.452] [INFO] ueberDB - Flushed 35 values [2013-04-29 17:16:35.956] [INFO] ueberDB - Flushed 7 values [2013-04-29 17:16:36.464] [INFO] ueberDB - Flushed 16 values [2013-04-29 17:16:37.965] [INFO] ueberDB - Flushed 10 values [2013-04-29 17:16:39.468] [INFO] ueberDB - Flushed 17 values [2013-04-29 17:16:40.964] [INFO] ueberDB - Flushed 18 values [2013-04-29 17:16:43.455] [INFO] ueberDB - Flushed 25 values [2013-04-29 17:16:44.954] [INFO] ueberDB - Flushed 17 values [2013-04-29 17:16:46.457] [INFO] ueberDB - Flushed 16 values [2013-04-29 17:16:47.955] [INFO] ueberDB - Flushed 11 values [2013-04-29 17:16:49.470] [INFO] ueberDB - Flushed 18 values
Hi, I have something similar. Will try and see if I can get the info on our end.
Thanks, Ed. It looks like the page you’re attempting to load is the Add New Post page (wp-admin/post-new.php). Is that correct? Does the page ever begin to render?
Can you try opening a JS console while loading the Add New Post page to see if Participad is successfully launching any AJAX queries against the EPL installation?
Have you been able to configure Participad on its settings page? Do you get Participad-related errors in your Dashboard when visiting pages other than Add New Post?
Yeah, that’s right. The page never renders, it gives a 324 no data received when it finally gives in, so unfortunately nothing in the console. I can get to the configuration page when it’s all set up and running, but trying to get to any page where the participad install is taking over the editor box results in this.
I am getting a couple of display_error warnings/notices if I enable wp_debug mode, the initial one is related to BuddyPress as far as I know:
Notice: wpdb::prepare was called incorrectly. wpdb::prepare() requires at least two arguments. Please see Debugging in WordPress for more information. (This message was added in version 3.5.) in /var/www/wp-includes/functions.php on line 2959 Notice: Trying to get property of non-object in /var/www/wp-includes/post-template.php on line 29 Warning: setcookie() expects parameter 2 to be string, object given in /var/www/wp-content/plugins/participad/includes/class-participad-user.php on line 69
The above is from the Notepads page. There are no errors bar the initial wpdb::prepare one as above on the participad settings page.
Thanks for the additional details. I’m pretty sure that the php notices have nothing to do with your issue.
Without error data showing up in your logs, I’m not sure where to go next in terms of debugging. Given that it’s your PHP process that’s maxing out the CPU, it’s possible that there’s an infinite processing loop somewhere in Participad, but I don’t have a clear idea of where to start looking.
The starkness of your nginx log makes me think that it’s *not* an issue with a huge number of HTTP requests being sent and crashing EPL. However, given that I don’t have any other ideas, we could go down this path a bit more. Are you running the latest 1.0.1 of Participad? Since that version was released, I added an additional check that prevents Participad from overloading EPL when it gets back a bad result. Would you mind replacing your plugin files with the 1.0.x branch version? https://github.com/boonebgorges/participad/tree/1.0.x
Yeah, didn’t think there was anything going on there.
I was on the latest WordPress repo version, but I’ve replaced the files with your github repo’s and it’s still doing the same thing.
You can have access to the server if you want, it’s just a micro EC2 instance.
Sure, if you would like to send me WP and server creds, my email is boone at gorg dot es.
Hi all. Ed was kind enough to send credentials for his system, and I managed to locate the issues that were causing his particular set of problems. I’ve released version 1.0.2 of Participad, with fixes for those issue. Hopefully it helps others as well.
Hi Boone, we have Etherpad lite installed on our server on port 9001, that works. we’ve retried with the new version of participad, and it still crashes when participad is activated, immediately without a hang, like last time. So this might be a different error. It doesn’t even seem to generate an error log at the server level…
The message displayed on the site dashboard:
“The plugin participad/participad.php has been deactivated due to an error: Plugin file does not exist.”
- The topic ‘WP Hanging’ is closed to new replies.