signal error (*amqp091.Error)(nil)

[parsibox]

hi
RabbitMQ 3.13.2Erlang 26.2.5
go 1.22
os : linux 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
package : github.com/rabbitmq/amqp091-go v1.10.0

in our code we got signal with error nil
what should we do at this time?is this error fake?

golang code :

errNotifyClose := <-conn.NotifyClose(make(chan *amqp.Error))
		if !StopApp {
			myerrror := fmt.Sprintf("CunsumerStart disconnect signal error %#v", errNotifyClose)
		}

error code :

 signal error (*amqp091.Error)(nil)

[lukebakken]

What does RabbitMQ log at the time of the error?

[parsibox]

this is my error time :

2024-07-22 14:49:32.753493+04:30 [info] <0.35874.0> closing AMQP connection <0.35874.0> (192.168.153.43:53594 -> 192.168.153.44:5672, vhost: '/', user: 'admin')
2024-07-22 14:49:32.759880+04:30 [warning] <0.35848.0> closing AMQP connection <0.35848.0> (192.168.153.43:53586 -> 192.168.153.44:5672, vhost: '/', user: 'admin'):
2024-07-22 14:49:32.759880+04:30 [warning] <0.35848.0> client unexpectedly closed TCP connection
2024-07-22 14:49:32.760282+04:30 [warning] <0.35861.0> closing AMQP connection <0.35861.0> (192.168.153.43:53588 -> 192.168.153.44:5672, vhost: '/', user: 'admin'):
2024-07-22 14:49:32.760282+04:30 [warning] <0.35861.0> client unexpectedly closed TCP connection
2024-07-22 14:49:36.120021+04:30 [info] <0.37772.0> accepting AMQP connection <0.37772.0> (192.168.153.43:42548 -> 192.168.153.44:5672)
2024-07-22 14:49:36.125323+04:30 [info] <0.37772.0> connection <0.37772.0> (192.168.153.43:42548 -> 192.168.153.44:5672): user 'admin' authenticated and granted access to vhost '/'
2024-07-22 14:49:36.127986+04:30 [info] <0.37785.0> accepting AMQP connection <0.37785.0> (192.168.153.43:42550 -> 192.168.153.44:5672)
2024-07-22 14:49:36.132125+04:30 [info] <0.37785.0> connection <0.37785.0> (192.168.153.43:42550 -> 192.168.153.44:5672): user 'admin' authenticated and granted access to vhost '/'
2024-07-22 14:49:36.137348+04:30 [info] <0.37798.0> accepting AMQP connection <0.37798.0> (192.168.153.43:42554 -> 192.168.153.44:5672)
2024-07-22 14:49:36.141626+04:30 [info] <0.37798.0> connection <0.37798.0> (192.168.153.43:42554 -> 192.168.153.44:5672): user 'admin' authenticated and granted access to vhost '/'
2024-07-22 14:50:08.294151+04:30 [info] <0.31623.0> closing AMQP connection <0.31623.0> (192.168.153.43:40636 -> 192.168.153.44:5672, vhost: '/', user: 'admin')
2024-07-22 14:50:08.296261+04:30 [info] <0.37815.0> accepting AMQP connection <0.37815.0> (192.168.153.43:51082 -> 192.168.153.44:5672)
2024-07-22 14:50:08.300929+04:30 [info] <0.37815.0> connection <0.37815.0> (192.168.153.43:51082 -> 192.168.153.44:5672): user 'admin' authenticated and granted access to vhost '/'
2024-07-22 14:50:08.317725+04:30 [warning] <0.37815.0> closing AMQP connection <0.37815.0> (192.168.153.43:51082 -> 192.168.153.44:5672, vhost: '/', user: 'admin'):
2024-07-22 14:50:08.317725+04:30 [warning] <0.37815.0> client unexpectedly closed TCP connection
2024-07-22 14:50:08.317780+04:30 [warning] <0.31597.0> closing AMQP connection <0.31597.0> (192.168.153.43:40630 -> 192.168.153.44:5672, vhost: '/', user: 'admin'):
2024-07-22 14:50:08.317780+04:30 [warning] <0.31597.0> client unexpectedly closed TCP connection
2024-07-22 14:50:08.317810+04:30 [warning] <0.31610.0> closing AMQP connection <0.31610.0> (192.168.153.43:40632 -> 192.168.153.44:5672, vhost: '/', user: 'admin'):
2024-07-22 14:50:08.317810+04:30 [warning] <0.31610.0> client unexpectedly closed TCP connection

[parsibox]

we have this error on certain queues
and another services and connection is work correctly

[lukebakken]

2024-07-22 14:50:08.317725+04:30 [warning] <0.37815.0> closing AMQP connection <0.37815.0> (192.168.153.43:51082 -> 192.168.153.44:5672, vhost: '/', user: 'admin'):
2024-07-22 14:50:08.317725+04:30 [warning] <0.37815.0> client unexpectedly closed TCP connection

This means that your application shut down without closing the connection correctly. Is there an unhandled error or panic happening?

I'm not sure why you are getting nil in your case. You can probably ignore it.

We can investigate if there is a reliable way to reproduce this issue.