|
Foundry Photo Workshop
|
May 8, 2016 at 8:26 am
Help! All of my tickets have disappeared from all my events, despite a history of transactions. It shows that events have no associated dates or tickets.
I discovered this while trying to change the email template and seeing a preview but it gave me the message that there were no active events. I thought, “that’s strange” and went to check the events. And sure enough, they were wiped clean, with just the default Free Ticket.
The only changes I’ve made recently were to turn off CloudFlare, from Dreamhost and disabling the Cloudflare plugin. And of course the recent WP 4.5.2 upgrade. I’ve tried disabling all plugins (excluding EE): no change. I’ve reinstalled EE: nothing. I’ve saved Permalinks again (this has often fixed EE problems for me) and nothing.
I don’t know what could be wrong. HELP!
|
|
Lorenzo Orlando Caum
|
May 9, 2016 at 6:14 am
Hello,
I’ve seen that happen when the database has crashed. However, I’m not sure if that has happened here.
This may be your events listing page:
http://www.foundryphotoworkshop.org/events/
It usually has events listed there.
What happens if you create a new event with a name and description of test and immediately publish it? Does it appear as upcoming or does it show as inactive for the status (see top right area of event editor)?
—
Lorenzo
|
|
Foundry Photo Workshop
|
May 9, 2016 at 6:33 am
I tried to add a test event, but it won’t show up at all. Still shows as inactive and the page won’t save with an event date. Dreamhost says everything looks fine to them except for this:
“However, I did notice another issue with your site hitting the shared
server memory limit on the server, that can result in intermittent
timeouts with the site, though the error you were getting looks to have
been with some sort of connection issue with the database server:
Sun May 8 19:49:04 2016 procwatch3 INFO: PID 18720 (php56.cgi)
foundryphoto:pg224313 – 72.6MB ram, 1.48 sec cpu: killed for gid ram
Sun May 8 19:50:05 2016 procwatch3 INFO: PID 20153 (php56.cgi)
foundryphoto:pg224313 – 72.4MB ram, 1.56 sec cpu: killed for gid ram
Sun May 8 19:51:36 2016 procwatch3 INFO: PID 21507 (php56.cgi)
foundryphoto:pg224313 – 75.6MB ram, 5.78 sec cpu: killed for gid ram
Sun May 8 19:51:36 2016 procwatch3 INFO: PID 21520 (php56.cgi)
foundryphoto:pg224313 – 73.7MB ram, 0.77 sec cpu: killed for gid ram
Sun May 8 19:51:46 2016 procwatch3 INFO: PID 21560 (php56.cgi)
foundryphoto:pg224313 – 72.4MB ram, 0.93 sec cpu: killed for gid ram
“
|
|
Foundry Photo Workshop
|
May 9, 2016 at 7:20 am
I think I’m getting somewhere. I had the MYSQL database details tucked away in a config.php at the root directory using a php include in the standard wp-config.php… as a security measure. Now I’ve taken out the include function and restored the original wp-config file.
The test event is now saving the dates. Will I need to recreate the events? Or can I still recover the originals?
|
|
Josh
|
May 9, 2016 at 8:10 am
Can you check in the _esp_ticket table in the database to see if there are tickets there?
-
This reply was modified 8 years ago by
 Josh. Reason: corrected table name
|
|
Foundry Photo Workshop
|
May 9, 2016 at 9:10 am
Yes, I have quite a number of tickets, including all the modifications on single tickets.
|
|
Josh
|
May 9, 2016 at 9:57 am
Were the database prefixes for some of those tables changed at any point?
|
|
Foundry Photo Workshop
|
May 9, 2016 at 10:01 am
The prefixes have been “fp” (rather than “wp”) since before I ever installed EE. 
Dreamhost notified me they restarted the MYSQL server, but I’m still getting the errors, only on EE-related pages like /register/ where I have a shortcode for our main event.
|
|
Foundry Photo Workshop
|
May 9, 2016 at 10:03 am
I meant to add:
|
|
Foundry Photo Workshop
|
May 9, 2016 at 10:47 am
Dreamhost has responded:
“Thanks for responding with an update. Unfortunately, our logs show that
your user’s processes are being killed for reaching the memory limit.
The error log also show entries that are related to the issue.
[Mon May 09 09:24:53 2016] [crit] [client 192.0.101.226] (9)Bad file
descriptor:
/home/foundryphoto/foundryphotoworkshop.org/wp-content/cache/page_enhanced/www.foundryphotoworkshop.org/.htaccess
pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon May 09 09:25:01 2016] [error] [client 162.228.76.135] Premature end
of script headers: index.php
[Mon May 09 09:25:21 2016] [error] [client 162.228.76.135] Premature end
of script headers: index.php
I’ve gone ahead and increased the PHP memory_limit along with the
max_execution_time for you to help. ”
|
|
Foundry Photo Workshop
|
May 9, 2016 at 1:10 pm
Now as I try to update the events, I’m getting the following:
`A database error has occurred. Turn on WP_DEBUG for more information.
…which I did, but it doesn’t give me any error (other than the latest one about the deprecated tag that came with 4.5)
|
|
Foundry Photo Workshop
|
May 9, 2016 at 1:16 pm
Now something even stranger happened.
I used WP-DB Manager to Repair all the tables in the database and then went to an event from last year that was showing up as active and updated it as a Draft. For some reason, this brought back all the tickets ever created in the database.
So I tried updating the current event for this year to Draft and it gave me this error, all blank screen with this:
Warning: mysqli_query(): MySQL server has gone away in /home/foundryphoto/foundryphotoworkshop.org/wp-includes/wp-db.php on line 1811
Warning: mysqli_query(): Error reading result set’s header in /home/foundryphoto/foundryphotoworkshop.org/wp-includes/wp-db.php on line 1811
Notice: WPDB Error “Duplicate entry ‘1’ for key ‘PRIMARY'” while running wpdb method “insert” with arguments [“fpesp_datetime”,{“EVT_ID”:0,”DTT_name”:””,”DTT_description”:””,”DTT_EVT_start”:”2016-06-08 08:00:00″,”DTT_EVT_end”:”2016-06-08 17:00:00″,”DTT_reg_limit”:-1,”DTT_sold”:0,”DTT_is_primary”:false,”DTT_order”:1,”DTT_parent”:0,”DTT_deleted”:false},[“%d”,”%s”,”%s”,”%s”,”%s”,”%d”,”%d”,”%d”,”%d”,”%d”,”%d”]]. Automatically attempting to fix EE Core DB in /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 1899
Notice: WPDB AGAIN: Error “Duplicate entry ‘2’ for key ‘PRIMARY'” while running the same method and arguments as before. Automatically attempting to fix EE Addons DB in /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 1899
Warning: mysqli_query(): MySQL server has gone away in /home/foundryphoto/foundryphotoworkshop.org/wp-includes/wp-db.php on line 1811
Warning: mysqli_query(): Error reading result set’s header in /home/foundryphoto/foundryphotoworkshop.org/wp-includes/wp-db.php on line 1811
Fatal error: Uncaught exception ‘EE_Error’ with message ‘WPDB Error: “Duplicate entry ‘1’ for key ‘PRIMARY'”‘ in /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:1849 Stack trace: #0 /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2361): EEM_Base->_do_wpdb_query(‘insert’, Array) #1 /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2222): EEM_Base->_insert_into_specific_table(Object(EE_Primary_Table), Array, false) #2 /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_classes/EE_Base_Class.class.php(1404): EEM_Base->insert(Array, true) #3 /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php(254): EE_Base_Class->save() #4 /home/foundryphoto/foundryphotoworkshop.org/w in /home/foundryphoto/foundryphotoworkshop.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 1849
|
|
Josh
|
May 9, 2016 at 8:25 pm
It sounds like when the processes were killed, some of the writes to the database didn’t finish. Do you have a backup of the database from the pout before this happened, that you can restore to?
|
|
Foundry Photo Workshop
|
May 11, 2016 at 7:52 pm
Yup, that did it. Restored from a backup from last week. Odd thing was that out of the last 10 backups, 8 were 1.6mb and the last 2 were 136kb! I don’t know what happened but I’m sure I would’ve needed to restore the database anyhow.
Thanks!
|
|
Josh
|
May 11, 2016 at 8:26 pm
You’re welcome.
|
