Hide Forgot
Description of problem: When working on Bug 1650260 we saw a BindException indicating that ODL failed to bind to a port, however it's not stating which address:port combination was used, so it's a guessing game to figure out which port wasn't bound. Also there's a stack trace but it's not pointing to any ODL code (probably since it's using netty IO stack). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Look at logs from Bug 1650260 2. Shortcut to logs: http://rhos-release.virt.bos.redhat.com/log/bz1650260/ 3. Actual results: 2018-11-15T14:12:00,444 | ERROR | SystemReadyService-0 | SystemReadyImpl | 278 - org.opendaylight.infrautils.ready-impl - 1.3.4.redhat-6 | Thread terminated due to uncaught exception: SystemReadyService-0 java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) ~[?:?] at sun.nio.ch.Net.bind(Net.java:433) [?:?] at sun.nio.ch.Net.bind(Net.java:425) [?:?] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) [?:?] at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:128) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:558) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1338) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:501) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:486) [65:io.netty.transport:4.1.22.Final] at io.netty.handler.logging.LoggingHandler.bind(LoggingHandler.java:191) [63:io.netty.handler:4.1.22.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:501) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:486) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:999) [65:io.netty.transport:4.1.22.Final] at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:254) [65:io.netty.transport:4.1.22.Final] at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:366) [65:io.netty.transport:4.1.22.Final] at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [62:io.netty.common:4.1.22.Final] at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [62:io.netty.common:4.1.22.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) [65:io.netty.transport:4.1.22.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [62:io.netty.common:4.1.22.Final] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [62:io.netty.common:4.1.22.Final] at java.lang.Thread.run(Thread.java:748) [?:?] Expected results: Probably some log message with the address and port that failed would be nice, also if it's possible to avoid the stack trace that would be nice to have Additional info:
I'm wondering if some of these files also need to be handled since they also seem to be binding to ports: https://github.com/search?q=org%3Aopendaylight+io.netty.bootstrap.ServerBootstrap&type=Code
As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality