https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/INTDIST-22 integration-distribution <p>After installing odl-nsf-all, odl-openflowplugin-all, odl-adsal-compatibility-all, and odl-vtn-manager-all executing a "log:tail" in the karaf cli yields to an error message/automatic disconnect from the karaf cli. A workaround is to add the Grep option and the error/disconnect will not occur "log:tail |grep vtn"</p> <p>i.e.<br/> opendaylight-user@root&gt;log:tail<br/> 2014-11-07 11:13:18,049 | INFO | e ssh user karaf | FeaturesServiceImpl | 24 - org.apache.karaf.features.core - 3.0.1 | Installing feature odl-adsal-all 0.8.1-Helium<br/> 2014-11-07 11:13:18,049 | INFO | e ssh user karaf | FeaturesServiceImpl | 24 - org.apache.karaf.features.core - 3.0.1 | Installing feature odl-adsal-core 0.8.1-Helium<br/> 2014-11-07 11:13:18,049 | INFO | e ssh user karaf | FeaturesServiceImpl | 24 - org.apache.karaf.features.core - 3.0.1 | Installing feature odl-base-felix-dm 3.1.0<br/> 2014-11-07 11:13:18,054 | INFO | e ssh user karaf | FeaturesServiceImpl | 24 - org.apache.karaf.features.core - 3.0.1 | Installing feature odl-base-dummy-console 1.1.0-Helium<br/> 2014-11-07 11:13:18,055 | INFO | e ssh user karaf | FeaturesServiceImpl | 24 - org.apache.karaf.features.core - 3.0.1 | Installing feature odl-adsal-thirdparty 0.8.1-Helium</p> <p>&lt;-----truncated output -------&gt;</p> <p>tionTask.call(DOMDataCommitCoordinatorImpl.java:127)<span class="error">&#91;222:org.opendaylight.controller.sal-broker-impl:1.1.0.Helium&#93;</span><br/> at org.opendaylight.yangtools.util.concurrent.DeadlockDetectingListeningExecutorService$2.call(DeadlockDetectingListeningExecutorService.java:192)<span class="error">&#91;143:org.opendaylight.yangtools.util:0.6.2.Helium&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:262)<span class="error">&#91;:1.7.0_67&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)<span class="error">&#91;:1.7.0_67&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)<span class="error">&#91;:1.7.0_67&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.7.0_67&#93;</span><br/> Disconnecting: Corrupted MAC on input.<br/> admin@turtleOC.extremenetworks.com:~$</p> <p>Operating System: All<br/> Platform: All</p> INTDIST-22

Key input issue on Karaf Console after log:tail command

Bug Resolved Done Unassigned Kuldip Fri, 19 Dec 2014 18:40:30 +0000 Fri, 20 Oct 2017 10:07:46 +0000 Sat, 19 Nov 2016 00:49:03 +0000 Helium Karaf 0 9 <p>After I execute "log:tail" command on Karaf Console, key input on Karaf Console gets weird.<br/> After that, I have to type my character multiple times for the keyboard input keys to show.</p> <p>For example, to input "bundle:list" on Karaf Console, I have to type "bbuunnddllee::lliisstt" on my keyboard.</p> <p>It happens even when I don't install any features.</p> <p>I've observed that it happens on Helium-SR1.<br/> And, I've faced this issue since September 21st.</p> <p>I just tried this on master by:</p> <p>1) Building the integration/distributions/extra/karaf<br/> 2) cd target/assembly/bin<br/> 3) ./karaf<br/> 4) feature:install odl-nsf-all odl-openflowplugin-all odl-adsal-compatibility-all odl-vtn-manager-all<br/> 5) log:tail<br/> 6) ^C<br/> 7) start typing feature:install</p> <p>I don't see any character repeat or lag. Is this only seen on Helium-SR1?</p> <p>(In reply to Ed Warnicke from comment #2)<br/> &gt; I just tried this on master by:<br/> &gt; <br/> &gt; 1) Building the integration/distributions/extra/karaf<br/> &gt; 2) cd target/assembly/bin<br/> &gt; 3) ./karaf<br/> &gt; 4) feature:install odl-nsf-all odl-openflowplugin-all<br/> &gt; odl-adsal-compatibility-all odl-vtn-manager-all<br/> &gt; 5) log:tail<br/> &gt; 6) ^C<br/> &gt; 7) start typing feature:install<br/> &gt; <br/> &gt; I don't see any character repeat or lag. Is this only seen on Helium-SR1?</p> <p>I've faced this issue since September 21st.<br/> I can see this issue on both Helium and Helium-SR1.</p> <p>I have had the same issue after interrupting log:tail too.</p> <p>Dave.</p> <p>After I execute "log:tail" command, it occurs with a probability of about 40%.<br/> Therefore, I think if you execute the "log"tail" command three times, you may face the issue.</p> <p>I tried the following three kinds of terminals.<br/> But, the result doesn't change.</p> <p>1. GNOME Terminal (3.8.4)<br/> 2. PuTTY<br/> 3. TeraTerm</p> <p>Here is the output of "stty -a" on my CentOS7 in which I run ODL controller.</p> <p>$ stty -a<br/> speed 9600 baud; rows 53; columns 207; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = &lt;undef&gt;; eol2 = &lt;undef&gt;; swtch = &lt;undef&gt;; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -ixon -ixoff -iuclc -ixany imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke</p> <p>Is it possible to have more information about the environments? At least Shell being used and JVM version? I also tried it and it works fine but it might be environment specific.</p> <p>Moreover, can you try logging in via SSH ( ssh -p 8101 karaf@localhost ) and see if it is terminal related or not?</p> <p>Thanks!</p> <p>For me:</p> <ul> <li>CentOS 7, running in a VM</li> <li>bash - whatever comes with CentOS 7</li> <li>SSHing into the instance</li> </ul> <p>Dave.</p> <p>This seems like a karaf issue. Is this still happening Hideyuki?</p> <p>(In reply to Luis Gomez from comment #8)<br/> &gt; This seems like a karaf issue. Is this still happening Hideyuki?</p> <p>No, it does not happen now.</p> <p>I tried to reproduce the issue with Beryllium SNAPSHOT artifacts which were built from the source code today, but the issue didn't occur.</p> <p>I'm on +1 to close the bug.</p> Development External issue ID 2530 External issue URL Rank 0|i01lfr: