Fix the issue with failing pbm commands by starting logging later after the collection is created

Description

pbm config --force-resync --wait

pbm logs -f

Environment

None

is triggered by

Activity

Dmytro Zghoba 
September 18, 2024 at 8:33 AM

the implementation details were changed. no convertToCapped is invoked. just logging starts later after the collection is created. such code was merged and tested

Dmytro Zghoba 
September 9, 2024 at 3:53 PM

the root cause is the warning message WARNING: Unsupported MongoDB version. PBM works with v4.4, v5.0, v6.0, v7.0 is put into admin.pbmLog collection before the collection is created as capped. PBM inserts this message into the logging collection which makes the collection regular. then tries to create the collection again as capped but it fails (NamespaceExists).

the fix does convertToCapped if the collection is created but it is not capped.

Done

Details

Assignee

Reporter

Needs QA

Components

Sprint

Fix versions

Priority

Created July 30, 2024 at 11:47 AM
Updated March 24, 2025 at 11:59 AM
Resolved September 17, 2024 at 10:08 AM