Default database instead of external database called when starting scheduler task via CLI

[h-e-l-l-o-w-o-r-l-d]

Hi there,

actually I wanted to open an issue on TYPO3-Forge but as it's external_import related I want to make sure it's really a core issue.

I have an environment with 2 configured external databases. All is fine, fetching data from these databases work as expected. Additionally there's EXT:external_import installed where in one of the custom steps I fetch data from an external database via Doctrine-Queries. The associated scheduler task fetches the data and it works if I manually run the task via backend scheduler.

Now the problem: This doesn't work if the task automatically starts via CLI/cronjob. Then the external database is not called but the default one, which of course can't work. In that case the following log message is stored in tx_externalimport_domain_model_log:

SELECT command denied to user 'username'@'localhost' for table 'pages' [0]

The current workaround is to bypass doctrine and directly connect to the database via pdo methods -> this works (with the same database configuration parameters). Is the behaviour a core bug or can I do anything about it?

Cheers

TYPO3 10.4.17 external_import 5.1.1

[fsuter]

Hi,

I would say that it's a Core bug, but it's not a certainty, more of an elimination process: I do nothing special with the database in external_import, I always use the Core API. Furthermore, external_import's scheduler task does nothing special either (I mean nothing really different from any other scheduler task).

Have you tried running the import directly from the command line (not using the task)? I'm curious if the same error happens.

[h-e-l-l-o-w-o-r-l-d]

Hi,

thanks for your fast response. I tried what you asked for and the error is the same when I manually start externalimport:sync from the command line.

So opening a core-issue is the best bet, right?

[fsuter]

Yes, I would say so.

[h-e-l-l-o-w-o-r-l-d]

Issue opened: https://forge.typo3.org/issues/94586