Joshua Barreiro

I set up a minute cronjob to see if it made successful runs more likely. 

28 minutes ago, Linux-Is-Best said:

Continuously optimizing your database could be resource-intensive. The general clean-up task should naturally run itself after the preset time. I question if your shared host was somehow preventing this from happening since the limited plan may have had a cap on how much computing power you were allowed. As a result, it was not completed as necessary, and once you were moved to a container with the required resources, it was finally completed.

Thanks.

Interesting thought. Is there a job set up in the admin settings? I can't find one, if so. It would be good to know if there's a way to verify whether I have tasks that are being killed by my host.

My host doesn't offer any services like that, so after the db was read in, mysql optimized it. But is there a task that can be enabled that will continuously optimize the db so that I don't have to get kicked off my shared hosting in the future? 

I plan on migrating back to shared hosting since this tier of hosting is literally a waste of resources and money, but I don't want to run into this issue in 2 years when the tables need to be optimized again...so how does one get optimized tables?

OK, so I want to thank everyone for their time on this.

I ended up upgrading to business class, and they migrated my account. My db was 1.52gb pre-migration.

After migration, my db started shrinking. It went from 1.52gb down to 290mb. My db is fine. Everything is functioning. There are no errors, but I've spent a lot of time with the host trying to understand why my db shrank, and they have no answers.

Is there some sort of logging or other junk that once the db reads in that it decides can be discarded? Is there a periodic job I can enable in Invision that will help me reclaim this space that is clearly not actual data on my site?

So, I'm not a DBA and I don't really intend to become one. How can I whittle this DB down to size? It's fallen over again, and I'm working with the host, but for a low-traffic site, I can't justify putting more money into the hosting. VPS is just not going to happen.

Would splitting DBs work for IP.Board?

Yeah, I realized that when asked, and honestly I don't plan on putting that much effort into this site.

TBH, I went over my hosting agreement-standard linux GoDaddy-and it doesn't have a DB size limit listed. So they can pound sand.

I think my host realized my DB had gotten a little large and decided to move it, and then screwed up some settings when they moved it.

Are there some purge settings I can use to shrink my DB?

Since nobody but me has access to the hosting account, that shouldn't have happened.

As a precaution, I changed the password of the user to the value present in conf_global.php and it's still broken.

My site-after many years of just humming away-is now inoperable. It happened yesterday afternoon. The board URL just started throwing a generic 500 error:

~~~

An error occurred (500 Error)