Author Topic: New Backup Error  (Read 3139 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
New Backup Error
« on: February 09, 2023, 07:02:59 PM »
Hello all,

I keep getting the same error message (E-Mail) with New backup cronjob.

Does anyone have an explanation for this, or is it like this for everyone or just me?

Mail title

Code: [Select]
Cron <root@node> /usr/local/cwp/php71/bin/php-cgi -d max_execution_time=100000000 -q /usr/local/cwpsrv/htdocs/resources/admin/include/cron_newbackup.php
Mail content

Code: [Select]
tar: .: file changed as we read it
tar: .: file changed as we read it
PHP Warning:  SQLite3::exec(): database is locked in /usr/local/cwpsrv/htdocs/resources/admin/include/cron_newbackup.php on line 0

Best regards

Offline
*
Re: New Backup Error
« Reply #1 on: February 11, 2023, 01:29:41 PM »
If you have a record lock, it would seem that it would time out until the lock is cleared
Maybe you should look how to clear record locks (contention?)

Offline
*****
Re: New Backup Error
« Reply #2 on: February 13, 2023, 09:46:17 AM »
Not to be snarky, but the New Backup is labeled as "beta" for a reason... I would expect to encounter some bugs along the way until it is fully shaken out!

Offline
*
Re: New Backup Error
« Reply #3 on: February 14, 2023, 02:04:45 AM »
I know what you mean, but the whole point of the beta phase is to discover the bugs and give feedback so that developers can improve it.

Offline
*****
Re: New Backup Error
« Reply #4 on: February 14, 2023, 01:33:41 PM »
Thank you for your comments, we will review what happens

Offline
*
Re: New Backup Error
« Reply #5 on: May 06, 2023, 07:44:09 AM »
same cron mail


Cron <root@test> /usr/local/cwp/php71/bin/php-cgi -d max_execution_time=100000000 -q /usr/local/cwpsrv/htdocs/resources/admin/include/cron_newbackup.php

tar: .: file changed as we read it
tar: .: file changed as we read it

Offline
*
Re: New Backup Error
« Reply #6 on: January 13, 2024, 06:07:16 PM »
I know what you mean, but the whole point of the beta phase is to discover the bugs and give feedback so that developers can improve it.

Now I understand why it is still beta for 5+ years.