Closed jisnardo closed 2 years ago
@alexvanin any suggestion? Thanks in advance.
@jisnardo can you please provide the configuration of booted storage node?
Here it is @cthulhu-rider :
node:
key: /private.key # path to a binary private key
addresses: # list of addresses announced by Storage node in the Network map
- ingress.jorisnalt.es:36512
attribute_0: User-Agent:NeoFS v0.27.5
attribute_1: UN-LOCODE:ES VLC
attribute_2: Capacity:1TB
attribute_3: Price:100
grpc:
num: 1 # total number of listener endpoints
0:
endpoint: 0.0.0.0:36512 # endpoint for gRPC server
tls:
enabled: false # use TLS for a gRPC connection
metrics:
address: 127.0.0.1:9090 # endpoint for Node metrics
shutdown_timeout: 15s # timeout for metrics HTTP server graceful shutdown
storage:
shard_num: 1 # total number of shards
shard:
0:
metabase:
path: /storage/metabase # metabase path
perm: 0644 # permissions for metabase files (directories: +x for current user and group)
blobstor:
path: /storage/blobstor # blobstor path
perm: 0644 # permissions for blobstor files (directories: +x for current user and group)
blobovnicza:
opened_cache_capacity: 32 # maximum number of opened database files
depth: 1 # max depth of object tree storage in key-value DB
width: 1 # max width of object tree storage in key-value DB
writecache: # use write-cache
enabled: false
gc:
remover_batch_size: 100 # number of objects to be removed by the garbage collector
remover_sleep_interval: 1m # frequency of the garbage collector invocation
object:
put:
pool_size_remote: 100 # number of async workers for remote PUT operations
pool_size_local: 100
morph:
rpc_endpoint: # side chain NEO RPC endpoints; are shuffled and used one by one until the first success
- https://rpc01.morph.testnet.fs.neo.org:51331
- https://rpc02.morph.testnet.fs.neo.org:51331
- https://rpc03.morph.testnet.fs.neo.org:51331
- https://rpc04.morph.testnet.fs.neo.org:51331
- https://rpc05.morph.testnet.fs.neo.org:51331
- https://rpc06.morph.testnet.fs.neo.org:51331
- https://rpc07.morph.testnet.fs.neo.org:51331
notification_endpoint: # side chain NEO RPC notification endpoints; are shuffled and used only the first non-error one
- wss://rpc01.morph.testnet.fs.neo.org:51331/ws
- wss://rpc02.morph.testnet.fs.neo.org:51331/ws
- wss://rpc03.morph.testnet.fs.neo.org:51331/ws
- wss://rpc04.morph.testnet.fs.neo.org:51331/ws
- wss://rpc05.morph.testnet.fs.neo.org:51331/ws
- wss://rpc06.morph.testnet.fs.neo.org:51331/ws
- wss://rpc07.morph.testnet.fs.neo.org:51331/ws
dial_timeout: 20s # timeout for side chain NEO RPC client connection
contracts: # side chain NEOFS contract script hashes; optional, override values retrieved from NNS contract
balance: e0420c216003747626670d1424569c17c79015bf
container: 9dbd2b5e67568ed285c3d6f96bac4edf5e1efba0
netmap: d4b331639799e2958d4bc5b711b469d79de94e01
reputation: 376c23a2ae1fad088c82046abb59984e3c4519d9
logger:
level: info # logger level: one of "debug", "info" (default), "warn", "error", "dpanic", "panic", "fatal"
control:
authorized_keys: # list of hex-encoded public keys that have rights to use the Control Service
grpc:
endpoint: 0.0.0.0:16512 # endpoint that is listened by the Control Service
Any idea @cthulhu-rider?
Hey @jisnardo sorry for the late reply!
I don't see any problem with your configuration. When was the last time you've tried to boot-up your node? Was Network status
other than STATUS_UNDEFINED
once upon a time?
The node was always running, I don't remember last Network status.
Still at the same point...
@jisnardo I suggest to upgrade to v0.28.3. Please don't forget to update your configuration as in the example.
About the problem with network entry: I noticed that capacity attribute is 1TB
which is incorrect - it must be unsigned interger number of bytes. Can I ask you to try to bootstrap your node again? Then we'll be able to see problems on Inner Ring side if necessary.
After fix now works.
Network status: ONLINE
Health status: READY
So the problem was related with misconfigured attributes.
The next step will be upgrade.
Thanks
Hi,
after upgrading from 0.27.4 to 0.27.5 logs complain about this:
Any suggestion will be appreciated.