Container Crashes on Startup with "Bloom Filter" error

[alejandroalffer]

When starting the container with Docker, it crashes displaying the error:

panic: failed to create bloom: m (number of bits in the Bloom filter) must be >= 2

This issue happens with the current version on the master branch, and a direct install following the public guide.

Further investigation is needed to resolve the crash during initialization.

[alejandroalffer]

We are in the process of setting up a Sandbox environment without containers to replicate the error. During this process, we plan to propose some cache values adjustments during the initialization phase to see if that stabilizes the container.

Additionally, we will be testing with different versions of GoQuorum to help with the debugging and to identify if the issue is version-specific.

We’ll update the issue with findings and potential solutions as we progress

[alejandroalffer]

It seems that with this configuration, the node fetches peers from DigitelTS and Izertis, and starts syncing

• export VER="v21.1.0"
• --cache 2048

Otherwire the Bloom Filter error appears

[alejandroalffer]

Testing https://github.com/alastria/alastria-node-quorum/tree/issue-49-bloom-filter-error branch... and also making a cold backup of the LevelDB

[alejandroalffer]

The node was successfully synchronized using version 21.1.0 for a period of 5 days. After that, it was necessary to upgrade to version 21.10.0, and the node has remained stable since the update.

Additionally, a backup of the DLT was created to facilitate synchronization for partners and ensure a smoother process moving forward.

I'm also repeating the process from Docker, using the branch issue-49-bloom-filter-error, to validate the solution.

[alejandro-nieto-git]

Amazing, good job!