Support

September 28, 2023 at 7:56 pm

Can you send us all the stack trace please.

also, did you try to disconnect the paypal, then connect it again?
https://monosnap.com/file/pO6RvWHM99z8YPocZ0bqQcQYHwacl0

Can you tell us how to reproduce the problem? do we need to be in specific page? or we need to try to purchase?

thanks

Thanks

September 29, 2023 at 7:00 am

I already checked with our webhost and we are fine on capacity, although they did increase some memory for us just in case.

It’s not a memory issue, is a DB issue.

Did you give them the above error? Just curious as to what they said about it if so.

Do you keep regular database backups?

We do have almost 2000 events (most have passed). Could that be a factor?

That will have an impact on the size of your DB but if you have space, its fine. Its not the cause of the above issue in itself.

September 29, 2023 at 7:42 am

I gave them the same information that I gave you above. They also looked at the files themselves and nothing really jumped out at them. They told me to come over to you.

I don’t want to put you in the middle here, but this actually has very little to do with Event Espresso’s files. Event Espresso is ‘causing’ the error by trying to create a database table… but the Database has the issue, not EE itself.

Sorry, and yes, we keep regular backups. I do delete old backups regularly so we don’t eat up space.

Can you send me a copy of the database from before this happened so I can take a look?

Here’s a thought… the person who manages our workshops/events has been uploading huge image files. They live on our regular media space, but EE has to “read” them. Could that be the culprit?

No and I’ll explain.

The reason I asked about running out of space is because if you are close to running out of space and there’s a change which then takes you over the limit… then a DB command runs with no space to do what it wants and it throws the tables out of sync.

This isn’t a ‘you have stuff that is too big to load’ issue, something has gone wrong with the DB and a quick Google search shows it’s common when running low on space, e.g.:

https://stackoverflow.com/questions/15694168/error-tablespace-for-table-xxx-exists-please-discard-the-tablespace-before-imp

The database itself needs to be fixed to stop this error.

As this is on the server side I would expect your host would be able to fix it for you by dropping the .idb file for that table (details in the link above).

If you have a database base backup from before this happened I can check the tables within that and see if there is an issue there beforehand.

September 29, 2023 at 7:59 am

How do you currently save your backups?

October 2, 2023 at 2:52 pm

Ok, so as I suspected would happen here, there isn’t enough access to fix this with the credentials provided, in my experience it’s rare you would get the level of access required to the DB to be able to fix this.

If InMotion support can point out where the database files (specifically the .idb files) are accessible from within your account, I’ll happily copy that file to a backup and remove it (which should fix the problem) but as mentioned generally this is something the host would do themselves…. they don’t just hand out file level DB access and afaict you don’t have that level of access (which is expected).

The only command I could run from this end would be to attempt to get the MySQL to drop the table, using something like:

DROP TABLE wp_esp_currency_payment_method;
ALTER TABLE wp_esp_currency_payment_method DISCARD TABLESPACE;

From within the database itself.

However, considering that the check for the table is returning that it doesn’t exist (otherwise EE wouldn’t try to create it) I’m 99.99% that would fail anyway.

This is something your host needs to fix, each time I’ve seen this on a share server, it’s the host who has fixed it, not the end user (you) or the plugin dev (us).

If I’m wrong about the above I’m more than open to discussing how so and how it is that we (or any dev) would go about deleting an orphaned .idb file (which is what this looks like this issue is) on share hosting without full access.