Export fails in CLI, Never finishes in GUI #368
Comments
|
Hello @jahknem Sadly you are hitting a known bug in Could you try applying the following patch and then run the command again: diff --git a/lib/Command/Export.php b/lib/Command/Export.php
index 55458d65..9777b6b7 100644
--- a/lib/Command/Export.php
+++ b/lib/Command/Export.php
@@ -212,9 +212,10 @@ protected function execute(InputInterface $input, OutputInterface $output): int
$io->writeln("Export saved in $folder/$exportName.zip");
} catch (\Exception $e) {
if ($io->isDebug()) {
- $io->error($e->getTraceAsString());
+ $io->error("$e");
+ } else {
+ $io->error($e->getMessage());
}
- $io->error($e->getMessage());
return $e->getCode() !== 0 ? (int)$e->getCode() : 1;
}
diff --git a/lib/Command/Import.php b/lib/Command/Import.php
index cf35f123..af145031 100644
--- a/lib/Command/Import.php
+++ b/lib/Command/Import.php
@@ -94,9 +94,10 @@ protected function execute(InputInterface $input, OutputInterface $output): int
$io->writeln("Successfully imported from ${path}");
} catch (\Exception $e) {
if ($io->isDebug()) {
- $io->error($e->getTrace());
+ $io->error("$e");
+ } else {
+ $io->error($e->getMessage());
}
- $io->error($e->getMessage());
return $e->getCode() !== 0 ? (int)$e->getCode() : 1;
}You will still get an error but this time with the actual error encountered. |
|
Hi @come-nc sorry for taking so long to respond, covid has me in its grips. Interesting, since that patch it works when calling the export function from the command line, even though that should not have done anything. Attached is the log from nextcloud.log, which seems to show something relevant if I am not mistaken? |
|
There is no reason why you should get a different error in cli on in the web UI, are you certain you are exporting the same user with the same migrators? The error trace is quite clear, there are more than 1000 files and that creates a too big query in the systemTagMapper. It needs to split it in chunk, but that will have to be fixed on server side. In the mean time the only work-around I can offer you is to export without files, and migrate files through another way. |
|
Yes I'm sure. It is however difficult for me to see if anything happens on the Webinterface as there is no progress marker or anything similar. Given that the profiles each have multiple 100 GB of files it is difficult to say if anything is happening. It's just that htop shows it not to do anything and the log entry from nextcloud.log I'm currently uploading the export made by cli to the new server and will see if I can import it. On that note, the Web UI exports the backup as user.nextcloud_export (tested on the new server) and only accepts a file with that name, even though it is just a zip file which contains the same thing as the export by cli, which has a much more comprehensible name. But that's probably a new issue. |
Error when exporting any user.
When trying to export on the GUI, the export never finishes, even after days. When using the CLI, it fails on trying to export files.
Below is the output with max verbosity when trying via CLI:
And below the respective Log entries from nextcloud.log
I'm not sure how to proceed, the error message is greek to me.
The text was updated successfully, but these errors were encountered: