Hi Christian,

that would require a serious debugging strategy: replace the database version, try out using some kind of stresstest, and if no problems found, we are still not sure of the problem will not re-appear in some specific situation. Before we engage in such a process, we'd like to know what could be the reason that this happens. Any ideas beforehand?

Arjan

2018-06-29 10:12 GMT+02:00 Christian GrĂ¼n <christian.gruen@gmail.com>:
Hi Arjan,

Can you reproduce the problem with BaseX 9.x?

Thanks in advance,
Christian




On Thu, Jun 28, 2018 at 10:35 AM Arjan Loeffen
<arjan.loeffen@armatiek.nl> wrote:
>
> Dear BaseX people,
>
> We create a backup of a BaseX 8.6.4 database using a windows scheduled process:
>
> call basexclient -V -Uadmin -Padmin -c "CREATE BACKUP imvertor-*"
>
> We have a server process that interacts with the databases, all called Imvertor-*. In accessing the database at certain moments the backup process seems to conflict with the update process.
> This is visible in the log:
>
> [...]
> 11:59:12.012 127.0.0.1:60319 admin REQUEST [GET] http://localhost:8984/rest/imvertor-jobs
> 11:59:12.106 127.0.0.1:60319 admin 200 95.65 ms
> 11:59:12.121 127.0.0.1:60319 admin REQUEST [DELETE] http://localhost:8984/rest/imvertor-jobs/2018-06-14-11-58-17-450.xml
> 11:59:12.137 127.0.0.1:60319 admin 200 5.08 ms
> 11:59:12.137 127.0.0.1:60322 admin REQUEST [POST] http://localhost:8984/rest/imvertor-jobs
> 11:59:12.200 127.0.0.1:60322 admin 200 73.59 ms
> 11:59:12.215 127.0.0.1:60322 admin REQUEST [POST] http://localhost:8984/rest/imvertor-jobs
> 11:59:21.075 127.0.0.1:60323 admin REQUEST SET QUERYINFO 0.13 ms
> 11:59:21.075 127.0.0.1:60323 admin OK QUERYINFO: true 0.1 ms
> 11:59:21.184 127.0.0.1:60323 admin REQUEST CREATE BACKUP imvertor-* 0.21 ms
> 11:59:22.372 127.0.0.1:60322 admin 400 Database 'imvertor-jobs_665091421' could not be renamed. 10166.92 ms
> 11:59:22.372 127.0.0.1:60322 admin REQUEST [POST] http://localhost:8984/rest/imvertor-jobs
> 11:59:27.309 127.0.0.1:60323 admin ERROR Database 'imvertor-jobs' is being updated, or update was not completed. Backup for 'imvertor-jobs-regression' was created in 53.29 ms. Backup for 'imvertor-jobs_665091421' was created in 1262.1 ms. Backup for 'imvertor-models' was created in 4760.92 ms. Backup for 'imvertor-models-regression' was created in 51.58 ms. 6128.15 ms
> 11:59:27.309 127.0.0.1:60322 admin 404 Database 'imvertor-jobs' was not found. 4932.96 ms
> 12:01:03.465 127.0.0.1:60325 admin REQUEST [GET] http://localhost:8984/rest/?command=list
> 12:01:03.481 127.0.0.1:60325 admin 200 3.24 ms
> 12:01:03.543 127.0.0.1:60325 admin REQUEST [GET] http://localhost:8984/rest/imvertor-jobs
> 12:01:03.543 127.0.0.1:60325 admin 404 Database 'imvertor-jobs' was not found. 0.36 ms
> 12:01:03.543 127.0.0.1:60325 admin REQUEST [PUT] http://localhost:8984/rest/imvertor-jobs
> 12:01:03.575 127.0.0.1:60325 admin 201 Database 'imvertor-jobs' created in 13.47 ms. 22.83 ms
> [...]
>
> This is rather a serious problem; the whole database is lost. Our software is set up such that the database is created when it is not found. Hence the last log...
>
> Do you recognize the problem, and can you specify how to avoid it?
> Hope this gives you enough info.
>
> Thanks in advance!
>
>
> --
> Arjan Loeffen, Armatiek BV
> 06-12918997



--
Arjan Loeffen, Armatiek BV
06-12918997