Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panic during node sighup processing in case of problems with rpc node #3061

Closed
evgeniiz321 opened this issue Dec 21, 2024 · 0 comments · Fixed by #3073
Closed

panic during node sighup processing in case of problems with rpc node #3061

evgeniiz321 opened this issue Dec 21, 2024 · 0 comments · Fixed by #3073
Assignees
Labels
bug Something isn't working I4 No visible changes neofs-storage Storage node application issues S4 Routine U2 Seriously planned
Milestone

Comments

@evgeniiz321
Copy link

evgeniiz321 commented Dec 21, 2024

info	neofs-node/config.go:902	SIGHUP has been received, rereading configuration...
info	shard/control.go:315	trying to restore read-write mode	{"shard_id": "EgZdmowYzd4UqrK63zvAFg"}
info	shard/mode.go:28	setting shard mode	{"shard_id": "EgZdmowYzd4UqrK63zvAFg", "old_mode": "READ_WRITE", "new_mode": "READ_WRITE"}
info	shard/mode.go:69	shard mode set successfully	{"shard_id": "EgZdmowYzd4UqrK63zvAFg", "mode": "READ_WRITE"}
info	shard/control.go:315	trying to restore read-write mode	{"shard_id": "WQ1oGrsfXW2xe54Uy5jcKS"}
info	shard/mode.go:28	setting shard mode	{"shard_id": "WQ1oGrsfXW2xe54Uy5jcKS", "old_mode": "READ_WRITE", "new_mode": "READ_WRITE"}
info	shard/mode.go:69	shard mode set successfully	{"shard_id": "WQ1oGrsfXW2xe54Uy5jcKS", "mode": "READ_WRITE"}
info	client/notifications.go:228	RPC connection lost, attempting reconnect
info	neofs-node/config.go:960	configuration has been reloaded successfully
info	client/multi.go:53	connection to RPC node has been established	{"endpoint": "ws://localhost:58302/ws"}
info	neofs-node/main.go:207	restarting internal services because of RPC connection loss...
info	event/listener.go:221	stop event listener by context	{"reason": "context canceled"}
warn	neofs-node/main.go:181	internal application error	{"message": "restarting after morph connection was lost: getting network state: could not get current epoch number: could not perform test invocation (epoch): chain/client: contract execution finished with state FAULT; exception: at instruction 31 (SYSCALL): System.Contract.Call failed: called contract 4ea20d322984f445a4a737dbbd4bb1900cdee905 not found: key not found"}
info	neofs-node/grpc.go:138	stopping gRPC server...	{"name": "NeoFS Control API"}
error	client/notifications.go:267	could not restore block subscription	{"error": "connection lost: while waiting for the response"}
info	client/notifications.go:228	RPC connection lost, attempting reconnect
info	neofs-node/grpc.go:154	gRPC server stopped successfully	{"name": "NeoFS Control API"}
info	neofs-node/storage.go:65	closing components of the storage engine...
warn	client/multi.go:43	could not establish connection to RPC node	{"endpoint": "ws://localhost:58302/ws", "error": "WS client creation: dial tcp: lookup localhost: operation was canceled"}
debug	blobstor/control.go:44	closing...	{"shard_id": "EgZdmowYzd4UqrK63zvAFg"}
info	shard/gc.go:165	waiting for GC workers to stop...
debug	shard/gc.go:151	GC is stopped
warn	shard/gc.go:105	stop event listener by closed channel
debug	blobstor/control.go:44	closing...	{"shard_id": "WQ1oGrsfXW2xe54Uy5jcKS"}
info	shard/gc.go:165	waiting for GC workers to stop...
debug	shard/gc.go:151	GC is stopped
warn	shard/gc.go:105	stop event listener by closed channel
info	neofs-node/storage.go:73	all components of the storage engine closed successfully
info	neofs-node/grpc.go:138	stopping gRPC server...	{"name": "NeoFS Public API"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x1009fed98]

goroutine 70 [running]:
github.com/nspcc-dev/neofs-node/pkg/morph/client.(*Client).routeNotifications(0x140001be240)
	github.com/nspcc-dev/neofs-node/pkg/morph/client/notifications.go:236 +0xf8
created by github.com/nspcc-dev/neofs-node/pkg/morph/client.New in goroutine 1
	github.com/nspcc-dev/neofs-node/pkg/morph/client/constructor.go:172 +0x630
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x1009ff044]

goroutine 372 [running]:
github.com/nspcc-dev/neofs-node/pkg/morph/client.(*Client).restoreSubscriptions(0x140001be240, 0x0, 0x140001172c0)
	github.com/nspcc-dev/neofs-node/pkg/morph/client/notifications.go:265 +0xc4
created by github.com/nspcc-dev/neofs-node/pkg/morph/client.(*Client).routeNotifications in goroutine 70
	github.com/nspcc-dev/neofs-node/pkg/morph/client/notifications.go:230 +0xe4

See nspcc-dev/neofs-testcases#915

@roman-khimov roman-khimov added this to the v0.45.0 milestone Dec 21, 2024
@roman-khimov roman-khimov added bug Something isn't working U2 Seriously planned S4 Routine I4 No visible changes neofs-storage Storage node application issues labels Dec 21, 2024
End-rey added a commit that referenced this issue Dec 26, 2024
When the RPC connection is lost and a recovery attempt occurs, the variable
`conn` responsible for the connection may be nil and therefore additional
verification is needed.

Closes #3061.

Signed-off-by: Andrey Butusov <[email protected]>
End-rey added a commit that referenced this issue Dec 26, 2024
When the RPC connection is lost and a recovery attempt occurs, the variable
`conn` responsible for the connection may be nil and therefore additional
verification is needed.

Closes #3061.

Signed-off-by: Andrey Butusov <[email protected]>
End-rey added a commit that referenced this issue Dec 26, 2024
When the RPC connection is lost and a recovery attempt occurs, the variable
`conn` responsible for the connection may be nil and therefore additional
verification is needed.

Closes #3061.

Signed-off-by: Andrey Butusov <[email protected]>
End-rey added a commit that referenced this issue Dec 27, 2024
When the RPC connection is lost and a recovery attempt occurs, the variable
`conn` responsible for the connection may be nil and therefore additional
verification is needed.

Closes #3061.

Signed-off-by: Andrey Butusov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working I4 No visible changes neofs-storage Storage node application issues S4 Routine U2 Seriously planned
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants