nextbackup fails silently (on big table)

i've installed ownbackup on nextcloud-16.0.4 and over the last two nights, its cronjob failed silently. nothing in the logs, but the backups are incomplete. looks like it bailed out on a big table. it wrote the structure.xml, but no data.dump is available. also there should be more tables after this one.

Sep 19 '19 09:09 pille

Sounds like something like #22, out of memory or max. execution time of php.

Sep 19 '19 09:09 pbek

What happens if you increase the max execution time and memory limit (best to -1 for both) and run the cron.php on the command line?

Sep 19 '19 09:09 pbek

i'd expect to see an error message in the logs. this is all:

{"reqId":"LBrEebhvQ2bE7ljlsJqB","level":0,"time":"2019-09-19T09:45:02+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Run OCA\\OwnBackup\\Jobs\\BackupJob job with ID 5","userAgent":"--","version":"16.0.4.1"}

and doesn't look failed at all, when in fact it did.

when i run a backup manually, i can see it failing with "Allowed memory size of 536870912 bytes exhausted..." in the logs.

so does it pull each table completely into memory, before dumping?

Sep 19 '19 10:09 pille

If php is killing its process there is no way to log anything in the interpreted php-file.

so does it pull each table completely into memory, before dumping?

yes, it uses the internal (private) Nextcloud API to do the backup

Sep 19 '19 10:09 pbek