Sorry for the long delay (holidays, work, etc.). I just started over this evening, this time with 4.5.9. Same problem.
The log shows the following:
[2019-01-24 05:53:14] production.ERROR: Illuminate\Database\QueryException [42S02] : /home/FULL_PATH_REDACTED/Accounting/InvoiceNinja/vendor/laravel/framework/src/Illuminate/Database/Connection.php [Line 647] => SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘InvoiceNinja.countries’ doesn’t exist (SQL: select * from countries where country_code = 004 limit 1) {“context”:“PHP”,“user_id”:0,“account_id”:0,“user_name”:"",“method”:“POST”,“user_agent”:“Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0”,“locale”:“en”,“ip”:“192.168.0.1”,“count”:1,“is_console”:“no”,“is_api”:“no”,“db_server”:“mysql”,“url”:“setup”} []
You’ll note I am running IN from a folder different than the “normal” folder. This arrangement allows for easier backups and other maintenance of the various “non-standard” PHP and other applications we use . . . [ I doubt this is the problem, though – surely install location is not hard-coded and the error is a DB error anyway. ]
Is the IN setup supposed to create the tables in the DB or is this done manually (with some SQL script or otherwise)?
The IN database has only 2 tables and 4 indexes:
Name Type Rows Fields
account_email_settings Table (InnoDB) 0 29
account_gateway_settings Table (InnoDB) 0 13
account_email_settings_account_id_index Index Index 1
account_gateway_settings_account_id_foreign Index Index 1
account_gateway_settings_user_id_foreign Index Index 1
account_gateway_settings_gateway_type_id_foreign Index Index 1
I noted from some of Hilel’s other posts that loading /update will often yield information.
Indeed, this provided a new error, namely that a certain tablespace already existed (even though the table was not visible in MariaDB)!
A number of years ago this machine had an earlier version of IN I played with. I had dropped all tables and indexes from the IN DB when I was “done” but left the (ostensibly empty) DB in place for future use. … Well, apparently the tables were not dropped properly and a bunch of .ibd files (InnoDB tables) remained.
I cleared everything out and re-ran setup.
Now I am getting “504 Gateway Time-out” – so, progress, SORT OF!