Porter stops at specific point during comments table, gives Database Connection not configured error #22
Replies: 1 comment 1 reply
-
You're on the right track. The Porter optimizes performance by batching inserts, usually 1000 at a time. The issue is the problematic record could be anywhere in that thousand (20,000 - 21,000) not in the 21,001 record. Open the file
Change it to this:
It will take longer to run, but you can narrow it down to 10 records that way and then see what the problem is. If you can't tell, export those 10 rows and I'll take a look for you. It's almost certainly the |
Beta Was this translation helpful? Give feedback.
-
I'm attempting to port Vanilla 3.x to Flarum.
I've tried both the web and CLI version and they both fail in the same way.
Fatal error: Uncaught InvalidArgumentException: Database connection [flarum_clean] not configured. in D:\xampp\htdocs\nitro-porter\vendor\illuminate\database\DatabaseManager.php ...
Naturally I've double checked my config.php file and I can't see anything wrong regarding connections, plus I've noticed that the process does seem to start, and some data is copied from the source to the target. In the CLI and log I can see it copies the Category table OK,
[2022-12-27T16:37:59.889425+01:00] porter.INFO: export: Category — 14 rows, 00.50s (5.5mb) [] []
Then the error appears midway through copying the comments table, and interestingly always at the same point every time - I have a
port_comment
table in my target with exactly 21,000 rows. Which suggests to me a limit is being hit somewhere, but I'm not sure what? Running in a local XAMPP with 256M memory allocated and the error happens after only about 10 seconds so well below any timeouts.I also looked at row 21001 just to be sure there is nothing unusual going on there, looks fine.
Beta Was this translation helpful? Give feedback.
All reactions