-
Bug
-
Resolution: Done
-
None
-
unspecified
-
None
-
Operating System: Linux
Platform: PC
-
1175
This is a third of CONTROLLER-530 which I was told by Devin Avery to split.
Steps to recreate:
- Starting with a fresh Fedora 20 Cloud VM on an OpenStack deployment with an IP I can reach
sudo yum update -y
sudo yum install -y java-1.7.0-openjdk unzip wget which
wget -P /home/fedora 'https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/artifact/distributions/base/target/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip'
unzip distributions-base-0.1.2-SNAPSHOT-osgipackage.zip
cd /home/fedora/opendaylight
./run.sh
- From another machine, in my case a second fresh Fedora 20 VM on an OpenStack deployment
sudo yum update -y
sudo yum install -y nmap
nmap -Pn -p 6640 172.18.14.10 # IP of first VM
That nmap scan of port 6640 results in the following exception on the first VM (running ODL):
osgi> 2014-06-09 21:39:21.228 UTC [nioEventLoopGroup-9-2] WARN i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[na:1.7.0_55]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[na:1.7.0_55]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[na:1.7.0_55]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[na:1.7.0_55]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) ~[na:1.7.0_55]
at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:446) ~[bundlefile:4.0.19.Final]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:871) ~[bundlefile:4.0.19.Final]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:225) ~[bundlefile:4.0.19.Final]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:115) ~[bundlefile:4.0.19.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507) [bundlefile:4.0.19.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464) [bundlefile:4.0.19.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378) [bundlefile:4.0.19.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350) [bundlefile:4.0.19.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [bundlefile:4.0.19.Final]
at java.lang.Thread.run(Thread.java:744) [na:1.7.0_55]
2014-06-09 21:39:21.231 UTC [nioEventLoopGroup-9-2] INFO o.o.ovsdb.plugin.ConnectionService - Connection to Node : OVS|172.18.14.12:43906 closed
osgi>
Here's the nmap output from the scan:
[fedora@dfarrell-opendaylight-bug1124-2 ~]$ nmap -Pn -p 6640 172.18.14.10
Starting Nmap 6.45 ( http://nmap.org ) at 2014-06-09 21:39 UTC
Nmap scan report for 172.18.14.10
Host is up (0.0022s latency).
PORT STATE SERVICE
6640/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds
I filed this under OVSDB because the log message (last line printed) comes from ovsdb/ovsdb/src/main/java/org/opendaylight/ovsdb/plugin/ConnectionService.java:296. I'm not confident about this classification. If it should be moved, please let me know and forgive my ignorance.