Latest posts for the topic "SNMP Bind Exception and IPV6"

SNMP Bind Exception and IPV6

craig — GMT

This is an FYI

I transferred a mango installation to a new host (and from windows to linux) and found that none of the SNMP Data sources would work.

[code]'SNMP Datasource Name': java.net.BindException: Permission denied[/code]
editing /etc/modprobe.d/aliases so that
[code]alias net-pf-10 ipv6[/code]
becomes
[code]alias net-pf-10 off[/code]
disabled IPV6 and fixed the problem

Re:SNMP Bind Exception and IPV6

mlohbihler — GMT

Did you try setting the preferred Java stack? I believe this is the option:

[code]-Djava.net.preferIPv4Stack=false[/code]

Re:SNMP Bind Exception and IPV6

craig — GMT

Ah nope, didn't know the option existed.

Re:SNMP Bind Exception and IPV6

narenblr — GMT

Also remember < 1024 ports on UNIX/Linux are privilidged ports and can be run only as root or by Xinetd. Hence, you should run mango as root and not as an ordinary user.

Re:SNMP Bind Exception and IPV6

craig — GMT

[quote=narenblr]Also remember < 1024 ports on UNIX/Linux are privilidged ports and can be run only as root or by Xinetd. Hence, you should run mango as root and not as an ordinary user.[/quote]

Yep upon further investigation I still seem to be getting the error. I think before it gave that error because it couldn't bind to the port and SNMP poll didn't work because of the IPV6 issue.

Now mango can poll the SNMP data sources since I've disabled IPV6 but is still giving the BindException because it can't listen. I'm not using SNMP traps, just poll, so mango shouldn't need to bind to any low port numbers.

I won't be running any webapp as root

Re:SNMP Bind Exception and IPV6

mlohbihler — GMT

[quote] I'm not using SNMP traps, just poll, so mango shouldn't need to bind to any low port numbers. [/quote]

SNMP is UDP, so you'll always be listener binding even if you're not using traps.

Re:SNMP Bind Exception and IPV6

craig — GMT

gotcha. but shouldn't need to bind to port 162 if not using traps right?

Re:SNMP Bind Exception and IPV6

mlohbihler — GMT

Not to 162, no. But 161 is the default port for other SNMP traffic, and since the data source is UDP it needs to bind to a port as a listener to get responses. If you didn't change from the default of 161 and you're not running as root, this would explain why you get a permission exception on Linux when you didn't get one under Windows.

Re:SNMP Bind Exception and IPV6

craig — GMT

netstat -anutp reveals one listening UDP port per SNMP data source, but not port 161

If I disable an SNMP data source and re-enable it, I get the BindException. If I reboot the server I get the BindException but the data source still seems to update.

None of this is critical for me, I'll let you know how it pans out.

[code]udp 0 0 0.0.0.0:36751 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:33301 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:39594 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:60990 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:34119 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:39881 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:34009 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:48879 0.0.0.0:* 10106/java
udp 0 0 0.0.0.0:42866 0.0.0.0:* 10106/java [/code]

Re:SNMP Bind Exception and IPV6

craig — GMT

Since I'm not using traps I changed the trap port in SNMP datasource settings to a large port number and no longer get the BindException.

If I were using traps I think I'd do some port translation on the firewall so that incoming UDP port 162 packets were sent to a higher port on the mango instance

Re:SNMP Bind Exception and IPV6

mlohbihler — GMT

Ah, right. The data source will listen for traps in any case. You can always just change the port number from 162 to, say 50162.