Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

handle bad SNMP ranges gracefully

Description

It seems that after the update from 1.8.11 to 1.8.13 it ist not possible to set snmp information. I tried /opennms/admin/snmpConfig.jsp but that had no effect.
I tried "/opt/opennms/bin/provision.pl snmp set xx.xx.xx.xx public version=v2c port=8161"
but there is neither a status change nor "provision.pl snmp xx.xx.xx.xx" gives me the new information.

provision.pl returns the following error:
500 Internal Server Error at /opt/opennms/bin/provision.pl line 620
main::put(xx.xx.xx.xx, 'community=public&version=v2c&port=8161', '/snmpConfig') called at /opt/opennms/bin/provision.pl line 548
main::cmd_snmp('set', xx.xx.xx.xx, 'public', 'version=v2c', 'port=8161') called at /opt/opennms/bin/provision.pl line 110
but there is no error in the logs (webapp + daemon)

Environment

SLES11 SP1 Java Version: 1.6.0_26 Sun Microsystems Inc. Java Virtual Machine: 20.1-b02 Sun Microsystems Inc. Operating System: Linux 2.6.32.12-0.7-default (amd64)

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Benjamin Reed May 2, 2012 at 2:11 PM

fixed in 1.10.2

Daniel Hammon November 4, 2011 at 8:46 AM

Oh I discovered an error in jetty.log.
There was a misconfigured range parameter. It wasn´t starting with the lowest number it was defined as:
127.0.0.10 - 127.0.0.1 which is invalid.

Ok I´d like to change the bug to an enhancement catching this error. Is that possible or do I have to create a new one?

Seth Leger November 3, 2011 at 11:46 AM

We need more information about the error. If the UI is malfunctioning, then there should be an exception stack trace in the jetty log. If you are experiencing a behavior problem in the UI, please take a screenshot of the screen with the problem and attach it to this bug. Thanks!

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created September 21, 2011 at 4:19 AM
Updated January 27, 2017 at 4:20 PM
Resolved May 2, 2012 at 2:11 PM

Flag notifications