hokan
Dabbler
- Joined
- Feb 10, 2017
- Messages
- 42
Using the new UI to delete several hundred snapshots caused the UI to become unresponsive. After some hours, the UI becomes responsive again.
Messages like this appear in the log:
Apr 2 19:06:15 enet-rascal-1 kernel: sonewconn: pcb 0xfffff80b3e782a50: Listen queue overflow: 193 already in queue awaiting acceptance (45 occurrences)
This give two clues: the pcb number and the overflow number.
# netstat -Lan | egrep "(Proto|193)"
Proto Listen Local Address
unix 193/0/128 /var/run/middlewared.sock
and
# netstat -a | grep fffff80b3e782a50
fffff80b3e782a50 stream 0 0 fffff80919987938 0 0 0 /var/run/middlewared.sock
So something associated with middlewared.sock is having trouble keeping up.
I will make a bug report once my UI becomes responsive again after my last test, but I know that others have had trouble with exploring "Listen queue overflow" problems and so I thought it worthwhile to post here my experience.
Messages like this appear in the log:
Apr 2 19:06:15 enet-rascal-1 kernel: sonewconn: pcb 0xfffff80b3e782a50: Listen queue overflow: 193 already in queue awaiting acceptance (45 occurrences)
This give two clues: the pcb number and the overflow number.
# netstat -Lan | egrep "(Proto|193)"
Proto Listen Local Address
unix 193/0/128 /var/run/middlewared.sock
and
# netstat -a | grep fffff80b3e782a50
fffff80b3e782a50 stream 0 0 fffff80919987938 0 0 0 /var/run/middlewared.sock
So something associated with middlewared.sock is having trouble keeping up.
I will make a bug report once my UI becomes responsive again after my last test, but I know that others have had trouble with exploring "Listen queue overflow" problems and so I thought it worthwhile to post here my experience.