ERROR – KILLED QUERY geodirectory/geodirectory_hooks_actions.php:1011
This topic contains 9 replies, has 5 voices, and was last updated by AlexCam 11 years, 4 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
June 18, 2014 at 6:49 pm #4832
I tried to update my site today and got multiple errors as follows:
I have now tried deactivating all plugins including Geodirectory from a new staging area.
I can update the core plugin which I did, I then updated permalinks and tried to activate just the core Geodirectory plugin without any other plugin running and still got the 502 bad gateway error…
I got the following error in my log:
ERROR – KILLED QUERY geodirectory/geodirectory_hooks_actions.php:1011
?
I have opened this new thread as requested and look forward to your updates.
Thanks
Dave
June 18, 2014 at 6:52 pm #4833Thanks, moved it to GD core bugs and assigned to developers.
I’ve sent them the error log via email and they will let you know asap.
Just FYI, we can’t recreate this on our server at the moment (at least I couldn’t) so it may be something specific to your provider and they may request you to give them FTP access.
Thanks
June 18, 2014 at 6:59 pm #4836I am doing some testing from this side as well.
I’m wondering if its anything to do with object caching… I am switching off all caching and other wpengine tools to see if that helps.
Will update as I go.
Cheers
June 19, 2014 at 1:42 am #4952Getting 500 error with only 3000 places in DEV area.
Did update to Geodirectory only. Other plugins installed and activated, but did not update them.
“500 Server Error
A misconfiguration on the server caused a hiccup. Check the server logs, fix the problem, then try again.
Not seeing error in wp-admin or root folder error log. What error log did you find the error in?
Hosting provider heavy throttling on server from this action. This is what is still running.
988 7.1 0.2 356992 70776 ? S 19:36 0:08 | _ /ramdisk/php/54/bin/php54 /public_html/dev/wp-cron.php
963 7.0 0.2 357020 71100 ? S 19:36 0:08 | _ /ramdisk/php/54/bin/php54 /public_html/dev/index.php
4441 0.8 0.0 316232 30796 ? S 19:37 0:00 | _ /ramdisk/php/54/bin/php54 /public_html/dev/wp-admin/index.phpJune 19, 2014 at 10:49 am #5019I had the same problem, the error log showed nothing on the server side at first and also when I set up a new domain to test I also had nothing.
I then went to my original install and found that it showed error logs for my staging site, that’s where this info comes from.
I am 90% certain that it has something to do with the amount of places we have, I had the same error when importing a csv file – I could only do 250-500 at a time.
If I could export the places I would try a brand new install.
June 19, 2014 at 4:47 pm #5103OK i think i see the problem, we will be releasing an update in a few hours, hopefully this will fix it for you.
Thanks,
Stiofan
June 19, 2014 at 11:03 pm #5159We released the update, I’m going to release a new version of Multilocation and GDF framework too in the next few minutes.
V1.1.3 should fix all bugs reported overnight including the timeout on updating website with many listings.
Error was due to a function that was settings the 1st image of each place also as wordpress featured image so that it could be used with other plugins.
We removed this function and we will add it to GD Tools addon that we will start developing soon.
Thx
June 19, 2014 at 11:52 pm #5172Paolo,
Could not even get into backend WP admin. So just uploaded V1.1.3 ZIP into plugins folder and exploded it and all appears to be working again. Have not done exhaustive testing but looks much better.
@stroudsco (Dave). Did not have to re-install WP just explode the new version in the plugins directory. Everything came back like a champ.
Thanks, Howard
June 19, 2014 at 11:54 pm #5173Goo to hear… 🙂
June 20, 2014 at 2:17 am #5202I was able to update the core plugin as well as all of the add on’s without any issue other than deactivating some widgets. Thanks guys! Now get some rest, yes?
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket