EVO: Problems

22.06.11: Аllegedly "аlone" at a meeting, but hearing others

report to EvoSupport

email to evosupport@vrvsNOSPAMPLEASE.org  :    More... Close

Date: Thu, 23 Jun 2011 03:06:42 +0200 (CEST)
From: Alexander Fedotov <fedotov@...>
To: evosupport@vrvsNOSPAMPLEASE.org
Subject: A bad experience with EVO observed 22.06.11

Dear Support Team,

I would like to report a malfunctioning of EVO I observed on June 22.

There was a meeting in the (LHC) CMS community, called "Forward Calibration", booked for ~14:00 CET, actually lasted 14:30-16:00.

I participated from Moscow which was usual for me (a laptop running Window Vista, starting EVO from http://evo.vrvs.org/evoGate/ web page with a firefox).

From the very beginning and until almost the end of the meeting:

  • EVO showed myself to me as the only participant, though there were few other persons as well (I saw: 0 persons for the meeting in the meeting list, 1 person after my entering)
  • I could hear the audio, and this was the only working channel/direction (though the audio quality was veeeeeeery bad...) :
    • I did not get video (I was missing at least a desktop transmission)
    • I saw nothing from EVO / other parties in the message field -- I could see there only what I typed.
    • Other parties did not hear me, and most probably did not see my typed messages .

Couple of times I quit meeting and entered back. Nothing changed. Once I restarted koala -- this did not help.
After quiting koala the second time I changed to EVO version 2.7 -- did not help too.

auto-reply with a trouble ticket: More... Close

Date: Thu, 23 Jun 2011 03:06:56 +0200
From: support for EVO via RT <evosupport@vrvs.org>
To: fedotov...
Subject: [vrvs.org #16136] AutoReply: A bad experience with EVO observed 22.06.11


This message has been automatically generated in response to the creation of a trouble ticket regarding:

  • "A bad experience with EVO observed 22.06.11",
a summary of which appears below.

There is no need to reply to this message right now. Your ticket has been assigned an ID of [vrvs.org #16136].

Please include the string:

  • [vrvs.org #16136]

in the subject line of all future correspondence about this issue. To do so, you may reply to this message.

Thank you,


The answers by Vladimir Litvin via RT <evosupport@vrvs.org> are shown in "navy" colour .

first options

It's hard to tell what was the reason. Most probable cause was bad network somewhere on your side, because we have had ~250 meetings today alone and everything was pretty much Ok.

There are couple of things to do next time when you will experience similar thing

  1. make sure that you are not using wireless connection, only wired connection can deliver the best quality EVO experience ,
  2. if you are not using wireless, check the packet loss rate.
    • To do that go to Koala->Koala Monitoring and check the CPU usage, and packet loss rate.
    • Ideally, CPU usage should be ~30% and packet loss rate =0 (< 10-15 %) .
      If it is more than 10-15 % you will experience something very similar to what you had today,
  3. check the total network bandwidth available to you.
  4. If everything is Ok, and you still have issues, please
    • use "Report problem" button at the bottom of the Koala
    • and send us a report. This will include the full java console output from your machine and we can make better guess what might be the problem.

more options

> By the way, would a "LOOP-BACK" TEST (not sure I call it correctly, I mean
> the mode when panda just echoes to me and only to me what I say) help to set a
> diagnosis in this situation?

It depends. Usually you are correct, but in case if network was cut off in nonstandard situation, and you see Loopback Ok, while Koala cannot transmit or receive anything, it means that Koala itself was stuck, please restart Koala in this case.

> > One of the options here - CHANGE THE PANDA SERVER. Just click on green
> > line "Connected to panda ..." at the bottom left corner and manually
> > select either one of the three best pandas or any panda from the list.
> > After that click on "Connect to selected panda".
> And how to understand that one panda is better than another?

Usually you can try two-three nearest pandas in geographical sense. If you are in Russia, try something beyond the Russia, because network in Russia might not be very stable.


In summary - if you have this situation in a future:

  • check the network first,
if it is Ok,
  • change the panda
(because you might not measure the bandwidth of the connection to the panda server, you will measure it to one of the servers on the web, or just measure your last mile bandwidth , while network problem could be near panda or in the middle),
  • restart Koala
and if nothing will happen,
  • send us a report.

Koala log files

More... Close

> There is probably a chance to get more info about your today's session.
> Could you please try to find Koala.log file on your system and send it to
> us together with information about your CPU model, how much RAM did you
> have and what OS do you have on the machine.
> Usually we are keeping Koala logs of the last 10 sessions with names
> Koala.log (most recent), Koala.log.1 Koala.log.2, etc . You can find it
> and send us the one which is from today's experience.

here is the list I found from the linux half of my laptop:

[dom2] ~/tm/koala_logs $ ll -rt \

109984 2011-05-11 13:55 .../Koala.log.5
 50167 2011-05-11 15:40 .../Koala.log.6
 65792 2011-05-19 18:45 .../Koala.log.7
121019 2011-05-25 15:41 .../Koala.log.8
 49331 2011-06-02 18:07 .../Koala.log.9
 56930 2011-06-06 16:52 .../Koala.log.1
126147 2011-06-08 14:33 .../Koala.log.2
 93733 2011-06-22 16:52 .../Koala.log.3
241325 2011-06-22 17:03 .../Koala.log.4
 67229 2011-06-22 18:03 .../Koala.log
The last three from yesterday have been made public on the web at:

This is one of the problems:

https://twiki.cern.ch/twiki/pub/Main/AVFedotovHowTo/110622_1703.Koala.log.4 :

java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(Unknown Source)
        at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
        at java.net.PlainSocketImpl.connect(Unknown Source)
        at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at sun.net.NetworkClient.doConnect(Unknown Source)
        at sun.net.www.http.HttpClient.openServer(Unknown Source)
        at sun.net.www.http.HttpClient.openServer(Unknown Source)
        at sun.net.www.http.HttpClient.<init>(Unknown Source)
        at sun.net.www.http.HttpClient.New(Unknown Source)
        at sun.net.www.http.HttpClient.New(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
        at java.net.HttpURLConnection.getResponseCode(Unknown Source)
        at evo_bd.a(Unknown Source)
        at evo_b1$3.construct(Unknown Source)
        at evo_b3$2.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
This is the network loss between ripn-vrvs.rbnet.ru and your Koala.

I suspect that this is the time when you had no presence in Koala.

One of the options here - change the panda server. ...

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2021-02-04 - AlexanderFedotov
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback