That worked thanks.
Kevin
-Original Message-
From: Tarus Balog [mailto:ta...@opennms.org]
Sent: Tuesday, May 19, 2009 3:44 PM
To: OpenNMS Code Development and Bugs
Subject: Re: [opennms-devel] 1.7.4-0.13432.snapshot
On May 19, 2009, at 6:38 PM, Kevin Roberts wrote:
> daemon/queued.
On May 19, 2009, at 6:38 PM, Kevin Roberts wrote:
> daemon/queued.log.1:2009-05-19 15:08:15,916 DEBUG [Thread-11216]
> Queued: Error upading file
Not sure errors with data collection would affect service monitoring.
Try this:
stop opennms
psql -U opennms opennms
delete from outages where ifr
: [opennms-devel] 1.7.4-0.13432.snapshot
On May 19, 2009, at 2:44 PM, Kevin Roberts wrote:
> Is there a problem with 1.7.4-0.13432.snapshot? (as it is reporting
> lot's of down ICNP, HTTP, SMNP etc and they are not down.)
Check for OutOfMemory logs and make sure that there is enough
errorIndex = 0
All the node down have this.
-Original Message-
From: Tarus Balog [mailto:ta...@opennms.org]
Sent: Tuesday, May 19, 2009 1:39 PM
To: OpenNMS Code Development and Bugs
Subject: Re: [opennms-devel] 1.7.4-0.13432.snapshot
On May 19, 2009, at 2:44 PM, Kevin Roberts wrote:
>
On May 19, 2009, at 2:44 PM, Kevin Roberts wrote:
> Is there a problem with 1.7.4-0.13432.snapshot? (as it is reporting
> lot’s of down ICNP, HTTP, SMNP etc and they are not down.)
Check for OutOfMemory logs and make sure that there is enough disk
space. I just upgraded to 13432 from 13428
No Errors in the logs
-Original Message-
From: Benjamin Reed [mailto:ran...@opennms.org]
Sent: Tuesday, May 19, 2009 11:54 AM
To: OpenNMS Code Development and Bugs
Subject: Re: [opennms-devel] 1.7.4-0.13432.snapshot
On 5/19/09 2:44 PM, Kevin Roberts wrote:
> Is there a problem with 1.
On 5/19/09 2:44 PM, Kevin Roberts wrote:
> Is there a problem with 1.7.4-0.13432.snapshot? (as it is reporting
> lot’s of down ICNP, HTTP, SMNP etc and they are not down.)
I'm not aware of any known issue of that severity; do you have any
ERROR-level messages in the logs that might point to an is
