[RADIATOR] SNMPAgent and FarmSize > 1

[Jan Tomasek]

Hello,

how to get SNMPAgent report correct statistic when using Radiator
FarmSize > 1 ? I've been collecting data about Radiator process using
SNMP, but after switching to FarmSize = 3 are graphs broken, looks about
1/3 when using 3 as size of farm:
http://tomasek.cz/stuff/radiator_medium.png

Logs:
> 
> root at radius1mng4:~# tail -f /mnt/ramdisk/radiator.2019_11_10_11.log |grep SNMP
> 2 00000000 Sun Nov 10 11:51:36 2019 347729: DEBUG: Creating SNMPAgent listen socket port 161 address 195.113.187.22
> 1 00000000 Sun Nov 10 11:51:36 2019 352864: ERR: Could not open SNMP Agent port 161 on 195.113.187.22: Address already in use
> 3 00000000 Sun Nov 10 11:51:36 2019 457157: ERR: Could not open SNMP Agent port 161 on 195.113.187.22: Address already in use

> 1 00000000 Sun Nov 10 11:51:47 2019 165012: DEBUG: Creating SNMPAgent listen socket port 161 address 195.113.187.22
> 2 00000000 Sun Nov 10 11:51:47 2019 180531: ERR: Could not open SNMP Agent port 161 on 195.113.187.22: Address already in use
> 3 00000000 Sun Nov 10 11:51:47 2019 289138: ERR: Could not open SNMP Agent port 161 on 195.113.187.22: Address already in use

> 1 00000000 Sun Nov 10 11:51:56 2019 145273: DEBUG: Creating SNMPAgent listen socket port 161 address 195.113.187.22
> 3 00000000 Sun Nov 10 11:51:56 2019 194276: ERR: Could not open SNMP Agent port 161 on 195.113.187.22: Address already in use
> 2 00000000 Sun Nov 10 11:51:56 2019 292481: ERR: Could not open SNMP Agent port 161 on 195.113.187.22: Address already in use

Looks like it is random which farm worker grab SNMP port.

I've found note in change log:
> Radiator revision 4.23-15 (2019-06-13)
> SNMPAgent and Monitor with FarmSize configuration no longer require a FarmChildHook to re-open their listen sockets. Their listen sockets are now created after forking the instances. FarmChildHook sample in hooks.txt goodies file was updated to point to an example in farmchildhook.txt goodies file. Updated Ldap.pm and SNMPAgent to better log and refuse incorrect Port configuration values. Minor fix to SNMPAgent to also return SNMPv2-MIB system group values when queried with snmpwalk.

I'm running Radiator 4.23-43 on Debian stretch.

How to resolve this?

<SNMPAgent>
        BindAddress 195.113.187.22
        Port 16%O

> 1 00000000 Sun Nov 10 12:29:12 2019 424719: DEBUG: Creating SNMPAgent listen socket port 161 address 195.113.187.22
> 2 00000000 Sun Nov 10 12:29:12 2019 475763: DEBUG: Creating SNMPAgent listen socket port 162 address 195.113.187.22
> 3 00000000 Sun Nov 10 12:29:12 2019 554067: DEBUG: Creating SNMPAgent listen socket port 163 address 195.113.187.22

Seems to work... but it means I need query all workers and sum output?
No very nice :(

I hope there is a better way.

Thanks
-- 
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/