One plausible fix would be to have 'juju create-backup --no-logs", as they
aren't usually super relevant to restore and usually consume a
significant amount of data.
On Tue, Apr 20, 2021 at 1:55 AM Soumya <email address hidden> wrote:
> I have a periodic juju backup script which sometimes fails with a
> similar error. Pasting it here for reference.
>
> ----------------------------
> ERROR while creating backup archive: while dumping juju state database:
> error dumping databases: error executing "/usr/bin/mongodump":
> 2021-04-19T07:05:31.665+0000 writing admin.system.users to ;
> 2021-04-19T07:05:31.667+0000 done dumping admin.system.users (2
> documents); 2021-04-19T07:05:31.667+0000 writing admin.system.version
> to ; 2021-04-19T07:05:31.668+0000 done dumping admin.system.version (2
> documents); 2021-04-19T07:05:31.669+0000 writing
> logs.logs.bac50024-0ebc-4409-8261-2cf17197e703 to ;
> 2021-04-19T07:05:31.669+0000 writing
> logs.logs.f11ecb98-49f4-4bbe-8990-b9ad8fcbf316 to ;
> 2021-04-19T07:05:31.669+0000 writing juju.txns.log to ;
> 2021-04-19T07:05:31.670+0000 writing juju.statuseshistory to ;
> 2021-04-19T07:05:31.828+0000 done dumping juju.statuseshistory (21524
> documents); 2021-04-19T07:05:31.828+0000 writing juju.actions to ;
> 2021-04-19T07:05:31.832+0000 Failed: error writing data for collection
> `logs.logs.bac50024-0ebc-4409-8261-2cf17197e703` to disk: error reading
> collection: Executor error during find command: CappedPositionLost:
> CollectionScan died due to position in capped collection being deleted.
> Last seen record id: RecordId(95589716);
> ----------------------------
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1852502
>
> Title:
> Juju backups failing Executor error: CappedPositionLost:
> CollectionScan died due to position in capped collection being
> deleted.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1852502/+subscriptions
>
One plausible fix would be to have 'juju create-backup --no-logs", as they
aren't usually super relevant to restore and usually consume a
significant amount of data.
On Tue, Apr 20, 2021 at 1:55 AM Soumya <email address hidden> wrote:
> I have a periodic juju backup script which sometimes fails with a ------- ------- ------- mongodump" : 19T07:05: 31.665+ 0000 writing admin.system.users to ; 19T07:05: 31.667+ 0000 done dumping admin.system.users (2 19T07:05: 31.667+ 0000 writing admin.system. version 19T07:05: 31.668+ 0000 done dumping admin.system. version (2 19T07:05: 31.669+ 0000 writing bac50024- 0ebc-4409- 8261-2cf17197e7 03 to ; 19T07:05: 31.669+ 0000 writing f11ecb98- 49f4-4bbe- 8990-b9ad8fcbf3 16 to ; 19T07:05: 31.669+ 0000 writing juju.txns.log to ; 19T07:05: 31.670+ 0000 writing juju.statuseshi story to ; 19T07:05: 31.828+ 0000 done dumping juju.statuseshi story (21524 19T07:05: 31.828+ 0000 writing juju.actions to ; 19T07:05: 31.832+ 0000 Failed: error writing data for collection bac50024- 0ebc-4409- 8261-2cf17197e7 03` to disk: error reading ------- ------- ------- /bugs.launchpad .net/bugs/ 1852502 /bugs.launchpad .net/juju/ +bug/1852502/ +subscriptions
> similar error. Pasting it here for reference.
>
> -------
> ERROR while creating backup archive: while dumping juju state database:
> error dumping databases: error executing "/usr/bin/
> 2021-04-
> 2021-04-
> documents); 2021-04-
> to ; 2021-04-
> documents); 2021-04-
> logs.logs.
> 2021-04-
> logs.logs.
> 2021-04-
> 2021-04-
> 2021-04-
> documents); 2021-04-
> 2021-04-
> `logs.logs.
> collection: Executor error during find command: CappedPositionLost:
> CollectionScan died due to position in capped collection being deleted.
> Last seen record id: RecordId(95589716);
> -------
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Juju backups failing Executor error: CappedPositionLost:
> CollectionScan died due to position in capped collection being
> deleted.
>
> To manage notifications about this bug go to:
> https:/
>