As your server is self hosted you should have no problem finding them.
That sounds like InnoDB tables being moved or emptied in an unorthodox way. Did you by any chance used to have MyISAM tables (which you could copy with your file manager) and then tried to duplicate a database by copying the files?threeonesix wrote: ↑Mon Jan 22, 2018 5:44 pm...
Next I restored the original 3.2.1 forum which was working fine before I attempted these upgrades. I received an error message about a missing phpbb_config_ext database table so I rebooted the server (if all else fails, reboot). When the site came back up I attempted to get to the forum again and this time the error message is that the table phpbb_ext doesn't exist. I can see that these tables exist via phpMyAdmin but when I click on them phpMyAdmin tells me they don't exist. I can physically see the tables in the database table list.
Nope, nothing like that has ever been done on this server. The server was rebooted earlier this month; when it came back up MySQL would not start due to logfile space being consumed. I fixed that issue, rebooted the server again and MySQL had no trouble starting. At the time the forum site worked fine after the second reboot. It was only last Friday that I was notified that the forum was down so we've been trying to fix that problem since. It's not a heavily used forum, only a handful of posts per day. To our knowledge nothing happened on the server between Thursday night (working) and Friday morning (not working). Believe me, I know how that sounds, I've been doing IT work for 25 years and servers and software don't often just break themselves. Very strange indeed.warmweer wrote: ↑Mon Jan 22, 2018 6:29 pmThat sounds like InnoDB tables being moved or emptied in an unorthodox way. Did you by any chance used to have MyISAM tables (which you could copy with your file manager) and then tried to duplicate a database by copying the files?
If that is what happened, then you can delete that database (use phpMyAdmin) and just restore a backup using phpMyAdmin.
Also, If your database has a mix of InnoDB and MyISAM tables, make sure your default database engine is set to InnoD and alter the engine for all the MyISAM tables (mixing engines had been known to cause problems)
If that be the case then you should report it in the bug tracker (if it has not already been reported)