Policer error for REP 1 CBF 1 container #1218

New issue

Closed

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

sami commented

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

Owner

Originally created by @roman-khimov on GitHub (Apr 28, 2024).

Expected Behavior

No errors.

Current Behavior

Apr 28 08:23:37 titan2 neofs-node[3297]: 2024-04-28T08:23:37.751Z        error        policer/check.go:284        receive object header to check policy compliance        {"component": "Object Policer", "object": "E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt/8LxHSV5J9zfoKKHB8AuyLu5Evftkp2hDQAVQkYcm1sMm", "error": "(*headsvc.RemoteHeader) could not head object in [/dns4/st4.t5.fs.neo.org/tcp/8080]: read object header from NeoFS: status: code = 2048 message = access to object operation denied"}
Apr 28 08:23:37 titan2 neofs-node[3297]: 2024-04-28T08:23:37.752Z        info        policer/check.go:164        node outside the container, but nobody stores the object, holding the replica...        {"component": "Object Policer", "object": "E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt/8LxHSV5J9zfoKKHB8AuyLu5Evftkp2hDQAVQkYcm1sMm"}

Container is REP 1 CBF 1:

container ID: E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt
owner ID: NfFA5g92e32YvraVmipA9oY8AjvbdgFdjY
basic ACL: 1c8c8ccc (private)
       RangeHASH    Range      Search     Delete     Put        Head       Get
0 1    1 1 0 0      1 0 0 0    1 1 0 0    1 0 0 0    1 1 0 0    1 1 0 0    1 1 0 0
X F    U S O B      U S O B    U S O B    U S O B    U S O B    U S O B    U S O B
  X-Sticky F-Final U-User S-System O-Others B-Bearer
created: 2023-07-26 12:32:03 +0300 MSK
attributes:
        Timestamp=1690363923
placement policy:
REP 1
CBF 1

Possible Solution

To be determined. Object was uploaded with a different network map. Now some other node should store it, but it doesn't want to interact with the old one. And old one can't delete as well, it doesn't know if it's safe.

Context

Testnet.

Your Environment

Version used: 0.41.1

Originally created by @roman-khimov on GitHub (Apr 28, 2024). ## Expected Behavior No errors. ## Current Behavior ``` Apr 28 08:23:37 titan2 neofs-node[3297]: 2024-04-28T08:23:37.751Z error policer/check.go:284 receive object header to check policy compliance {"component": "Object Policer", "object": "E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt/8LxHSV5J9zfoKKHB8AuyLu5Evftkp2hDQAVQkYcm1sMm", "error": "(*headsvc.RemoteHeader) could not head object in [/dns4/st4.t5.fs.neo.org/tcp/8080]: read object header from NeoFS: status: code = 2048 message = access to object operation denied"} Apr 28 08:23:37 titan2 neofs-node[3297]: 2024-04-28T08:23:37.752Z info policer/check.go:164 node outside the container, but nobody stores the object, holding the replica... {"component": "Object Policer", "object": "E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt/8LxHSV5J9zfoKKHB8AuyLu5Evftkp2hDQAVQkYcm1sMm"} ``` Container is REP 1 CBF 1: ``` container ID: E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt owner ID: NfFA5g92e32YvraVmipA9oY8AjvbdgFdjY basic ACL: 1c8c8ccc (private) RangeHASH Range Search Delete Put Head Get 0 1 1 1 0 0 1 0 0 0 1 1 0 0 1 0 0 0 1 1 0 0 1 1 0 0 1 1 0 0 X F U S O B U S O B U S O B U S O B U S O B U S O B U S O B X-Sticky F-Final U-User S-System O-Others B-Bearer created: 2023-07-26 12:32:03 +0300 MSK attributes: Timestamp=1690363923 placement policy: REP 1 CBF 1 ``` ## Possible Solution To be determined. Object was uploaded with a different network map. Now some other node should store it, but it doesn't want to interact with the old one. And old one can't delete as well, it doesn't know if it's safe. ## Context Testnet. ## Your Environment * Version used: 0.41.1