neofs-lens storage commands don't work #1327

New issue

Closed

opened 2025-12-28 17:22:36 +00:00 by sami · 2 comments

sami commented

2025-12-28 17:22:36 +00:00

Owner

Originally created by @evgeniiz321 on GitHub (Feb 9, 2025).

neofs-lens storage set of commands result in errors related to boltDB database, maybe related to https://github.com/nspcc-dev/neofs-node/issues/3076

(.venv) ➜  neofs-testcases git:(master) ✗ ./neofs-lens storage list --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-02-09-16-00-49-657338/env_files/neofs-env-2025-02-09-16-00-50/sn_1_hvseigtife/sn_1_config_iydpaetpnc.yml
could not create a shard: could not update shard ID: can't open boltDB database: timeout

(.venv) ➜  neofs-testcases git:(master) ✗ ./neofs-lens storage sanity --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-02-09-16-00-49-657338/env_files/neofs-env-2025-02-09-16-00-50/sn_1_hvseigtife/sn_1_config_iydpaetpnc.yml
reading config: open metabase: can't open boltDB database: timeout

Originally created by @evgeniiz321 on GitHub (Feb 9, 2025). `neofs-lens storage` set of commands result in errors related to boltDB database, maybe related to https://github.com/nspcc-dev/neofs-node/issues/3076 ``` (.venv) ➜ neofs-testcases git:(master) ✗ ./neofs-lens storage list --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-02-09-16-00-49-657338/env_files/neofs-env-2025-02-09-16-00-50/sn_1_hvseigtife/sn_1_config_iydpaetpnc.yml could not create a shard: could not update shard ID: can't open boltDB database: timeout ``` ``` (.venv) ➜ neofs-testcases git:(master) ✗ ./neofs-lens storage sanity --config /Users/evgeniiz/Projects/neofs-testcases-nspcc/neofs-testcases/test-run-2025-02-09-16-00-49-657338/env_files/neofs-env-2025-02-09-16-00-50/sn_1_hvseigtife/sn_1_config_iydpaetpnc.yml reading config: open metabase: can't open boltDB database: timeout ```

sami

2025-12-28 17:22:36 +00:00

closed this issue
added the
bug

S4

neofs-lens

I4

U1
labels

sami commented

2025-12-28 17:22:36 +00:00

Author

Owner

@evgeniiz321 commented on GitHub (Feb 10, 2025):

@roman-khimov the problem is that neofs-lens is intended to be run on a dead node. While in my test I expect it to be active. Is it ok for the write-cache test, to turn off the node to check that data is in a blobstore? Seems a little bit strange for me. Maybe there is a better way to check that data is in a blobstore and not in a write cache.

@End-rey suggested to use neofs-cli control object status to check where object is located. Is it ok to use it?

@evgeniiz321 commented on GitHub (Feb 10, 2025): @roman-khimov the problem is that neofs-lens is intended to be run on a dead node. While in my test I expect it to be active. Is it ok for the write-cache test, to turn off the node to check that data is in a blobstore? Seems a little bit strange for me. Maybe there is a better way to check that data is in a blobstore and not in a write cache. @End-rey suggested to use `neofs-cli control object status` to check where object is located. Is it ok to use it?

sami commented

2025-12-28 17:22:36 +00:00

Author

Owner

@roman-khimov commented on GitHub (Feb 10, 2025):

control is OK, stopping the node is acceptable too (btw, this is exactly the way to check it in future with blobstor failing to accept the object, it will end up in write cache only and this could be checked).

@roman-khimov commented on GitHub (Feb 10, 2025): `control` is OK, stopping the node is acceptable too (btw, this is exactly the way to check it in future with blobstor failing to accept the object, it _will_ end up in write cache only and this could be checked).