Re: Exception reported in a new install

David Poole <[email protected]>
Newsgroups gmane.network.opennms.general
Message-ID <CAKYmnOn1VineB=RzbuOuaRgdVA9aCSMvVFwK3s-bYTT7=O-ryA@mail.gmail.com>
I wouldn't ignore it - it's apparently triggering other issues (
https://issues.opennms.org/browse/NMS-9873)... new nodes are not
recognizing snmp
can you roll back your version of ONMS to something prior to 21.0.3?

On Wed, Mar 7, 2018 at 7:31 AM Ronny Trommer <[email protected]> wrote:

> Hi Thomas,
>
> you can ignore this message in a first place, it is a known issue
> described here: https://issues.opennms.org/browse/NMS-9667
>
>
> On 7. Mar 2018, at 16:12, Thomas Tam <[email protected]> wrote:
>
> I’ve recently installed a new opennms server with a new install of CentOS
> Linux release 7.4.1708 (Core). I followed the installation instruction at
> the opennms website. Everything seemed fine during the installation, but
> can’t open http://opennmserver:8980/opennms/. In the eventd.log, it shows
> the following exception. Would anyone have any suggestion of where I should
> look?
>
> Thanks,
> -Thomas
>
> *** Eventd.log ***
> 2018-03-07 09:51:07,982 WARN  [Camel Thread #21 - NettyServerTCPWorker]
> i.n.c.AbstractChannelHandlerContext: Failed to mark a promise as failure
> because it has failed already: DefaultChannelPromise@4fe48617(failure:
> java.nio.channels.ClosedChannelException), unnotified cause:
> java.nio.channels.ClosedChannelException
>             at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(...)(Unknown Source)
>
> io.netty.util.IllegalReferenceCountException: refCnt: 0, decrement: 1
>             at
> io.netty.buffer.AbstractReferenceCountedByteBuf.release0(AbstractReferenceCountedByteBuf.java:101)
> ~[netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.buffer.AbstractReferenceCountedByteBuf.release(AbstractReferenceCountedByteBuf.java:89)
> ~[netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.util.ReferenceCountUtil.release(ReferenceCountUtil.java:84)
> ~[netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:793)
> ~[netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1291)
> ~[netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:738)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:730)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannelHandlerContext.access$1900(AbstractChannelHandlerContext.java:38)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.write(AbstractChannelHandlerContext.java:1089)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannelHandlerContext$WriteAndFlushTask.write(AbstractChannelHandlerContext.java:1136)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.run(AbstractChannelHandlerContext.java:1078)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:442)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at
> io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
>             at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org <http://slashdot.org/>!
> http://sdm.link/slashdot_______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.