Comment 15 for bug 1787110

In ensured pre-upgrade the systems were affected and then:

B:
root@b:/usr/lib/nagios/plugins-rabbitmq# ./check_rabbitmq_server --node $(hostname -s) --hostname 127.0.0.1 --port=15672 -u "guest" -p "guest"
RABBITMQ_SERVER OK - Memory OK (0.45%) Process OK (0.03%) FD OK (0.04%) Sockets OK (0.00%) | Memory=0.45%;80;90 Process=0.03%;80;90 FD=0.04%;80;90 Sockets=0.00%;80;90

D:
root@d:/usr/lib/nagios/plugins-rabbitmq# ./check_rabbitmq_server --node $(hostname -s) --hostname 127.0.0.1 --port=15672 -u "guest" -p "guest"
RABBITMQ_SERVER OK - Memory OK (0.53%) Process OK (0.04%) FD OK (0.05%) Sockets OK (0.00%) | Memory=0.53%;80;90 Process=0.04%;80;90 FD=0.05%;80;90 Sockets=0.00%;80;90

X is and stays ok, but as outlined there I couldn't get the socket count down to zero (which would trigger the former bug). But I tested to probe a remote which now worked as well as not seeing other issues in the scripts provided by nagios-plugins-rabbitmq (we haven't touched the others, so that was expected)

Marking verified