tauruslib-devel — taurus development mailing list

[tauruslib-devel] TEP14 passing to CANDIDATE

[Carlos P. <cpa...@ce...>]

Hi all, 

I just finished some large modifications on the TEP14 wiki and moved it 
from DRAFT to CANDIDATE.

Please read it and comment (I wrote in a hurry, so I expect some typos!)

cheers!

Carlos

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] fix ordered dict import

[Carlos P. <cpa...@ce...>]

I agree with all you say.

I just prefer not to force a hotfix for this because with the transition 
to Taurus4 we already have too much work.

PS: in order not to forget this, I created this ticket:
https://sourceforge.net/p/tauruslib/tickets/271/


On Wed 9 March 2016 14:47:09 PICCA Frederic-Emmanuel wrote:
> > What do you think?
> 
> I think that I applyed the patch in the debian package n order to fix
> the package for now.
> 
> I think that the right fix is to remove the python <2.7 support :) and
> use the "official" collections source for OrderedDict. (Ps pyton2 is
> leggacy the best would be to support python 3.5 and type hinting ;)
> 
> What I think also is that I prefer (from a packager point of view)
> peoples to install dependencies instead of embeding third party
> libraries :)
> 
> My  problem is that continuous integration did not catch this problem
> because upstream and packager usally do not follow the same policy.
> 
> - packaged hate embeded third_party library and remove them.
> - upstream usually embed third-party code because it is easier from
> them to distribut there code.
> 
> This is more a faillure of the python distribution module, that the
> fault of pythonistas :).
> 
> Nevertheless, I think that with pip is is better, and we should let
> peoples install all dependencies via pip instead of embeding code.
> 
> So to summarise
> 
> I thik that collections should be used and fall back to the embeded
> solution for python 2.6 until it get's removed.
> 
> 
> Cheers
> 
> Fred

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] fix ordered dict import

[PICCA Frederic-E. <fre...@sy...>]

> What do you think?


I think that I applyed the patch in the debian package n order to fix the package for now.

I think that the right fix is to remove the python <2.7 support :) and use the "official" collections source for OrderedDict.
(Ps pyton2 is leggacy the best would be to support python 3.5 and type hinting ;)

What I think also is that I prefer (from a packager point of view) peoples to install dependencies instead of embeding third party libraries :)

My  problem is that continuous integration did not catch this problem because upstream and packager usally do not follow the same policy.

- packaged hate embeded third_party library and remove them.
- upstream usually embed third-party code because it is easier from them to distribut there code.

This is more a faillure of the python distribution module, that the fault of pythonistas :).

Nevertheless, I think that with pip is is better, and we should let peoples install all dependencies via pip instead of embeding code.

So to summarise

I thik that collections should be used and fall back to the embeded solution for python 2.6 until it get's removed.


Cheers

Fred

Re: [tauruslib-devel] fix ordered dict import

[Carlos P. <cpa...@ce...>]

Hi, 

I have an objection against this patch:

We have 3 cases here:

a) python<2.7 and ordereddict module installed (e.g. from pypi)
b) python<2.7 and ordereddict module not installed ==> use local copy
c) python==2.7 (ordereddict comes from collections)

The original code worked for a) and b) but not for c)  (which it treated 
as if it was b)

With your patch, it would work for b) and c) but not for a) (which it 
would be treated as b) )

The proper solution should try the collections.ordereddict, then 
ordereddict and only then revert to the local copy.

BUT: I understand that this is only a problem if the local copy of 
ordereddict is removed (as done for the debian packages) but not if 
installed from the "official" sources (since in practice, falling back to 
the local copy is ok).

So I wonder if it may make more sense to just apply your patch as part 
of the packaging of taurus3.7 **for debian** instead of forcing a hotfix 
in the official package (which is not affected in practice). Specially 
considering that it would be a temporary workaround because with 
taurus4, python 2.6 is no longer supported so the 
taurus.external.ordereddict package can be deprecated


What do you think?

Carlos


On Wed 9 March 2016 10:55:10 Picca Frédéric-Emmanuel wrote:
> ---
>  lib/taurus/external/ordereddict/__init__.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/taurus/external/ordereddict/__init__.py
> b/lib/taurus/external/ordereddict/__init__.py index caf0c37..d38bdce
> 100644
> --- a/lib/taurus/external/ordereddict/__init__.py
> +++ b/lib/taurus/external/ordereddict/__init__.py
> @@ -27,7 +27,7 @@ from __future__ import absolute_import
> 
>  try:
>      # ordereddict from python 2.7 or from ordereddict installed
> package? -    from ordereddict import *
> +    from collections import OrderedDict
>  except ImportError:
>      # ordereddict from local import
>      import os
> 
> ----------------------------------------------------------------------
> -------- Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] fix ordered dict import

[Picca Frédéric-E. <pi...@de...>]

---
 lib/taurus/external/ordereddict/__init__.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/taurus/external/ordereddict/__init__.py b/lib/taurus/external/ordereddict/__init__.py
index caf0c37..d38bdce 100644
--- a/lib/taurus/external/ordereddict/__init__.py
+++ b/lib/taurus/external/ordereddict/__init__.py
@@ -27,7 +27,7 @@ from __future__ import absolute_import
 
 try:
     # ordereddict from python 2.7 or from ordereddict installed package?
-    from ordereddict import *
+    from collections import OrderedDict
 except ImportError:
     # ordereddict from local import
     import os

Re: [tauruslib-devel] client dependent memory leak

[Zbigniew R. <zre...@ce...>]

Hello Roberto,

I've repeated the tests, and concluded the following:

The device server memleak that I have observed is related with the 
client reading DevString SPECTRUM attribute. It was already reported by 
Jan to the Tango community:
https://sourceforge.net/p/tango-cs/bugs/758/

I'm not able to reproduce the memleak that you've initially described - 
using the taurusform with the model set to TangoTest device and with the 
"Show device" panel opened. As you have observed it was fixed in the 
latest Tango&PyTango 8 patched packages and these are the ones that we 
use at Alba.

Many thanks!
Zibi



On 02/10/2016 04:00 PM, Zbigniew Reszela wrote:
> HI Roberto,
>
> Sorry for the late answer, but this week I could only dedicate some 
> spare gaps of time to this problem.
>
> First of all, good that the re-installation of Tango made your memleak 
> disappear.
>
> Then, what is strange to me are the results of my tests. I've done 
> them at our beamline, which in theory is using the same version 
> (latest 8.1.2 patched) in which you have seen the leak to disappear. 
> But let me crosscheck it with my colleagues.
>
> Since I had no access to the beamline anymore, I had continued tests 
> at my development environment.
> And I'm sure that I'm using the latest 8.1.2 patched version. I have 
> not observer any memleak in TangoTest.
> I have also prepared a dummy DS (C++) with 10 attributes (5 scalar 
> shorts and 5 scalar booleans) and I have checked them both on latest 
> 8.1.2 patched version and on the 9.1.0. No leak was observed.
> I have it pending to check it with PyTango...
>
> But maybe as you said the latest 8.1.2 patched version solves it, and 
> we do not use it in production...
> I will get back to you when I have more information.
>
> Cheers,
> Zibi
>
> On 02/10/2016 10:10 AM, Roberto Borghes wrote:
>> Hi Zibi,
>> the problem seems to be solved by installing the patched version of 
>> Tango 8.1.2 available on http://www.tango-controls.org.
>> Yesterday I've compiled it and everything seems ok!
>>
>> Ciao,
>>     Roberto
>>
>>
>>
>> On 02/02/2016 16:40, Zbigniew Reszela wrote:
>>> Hi Roberto,
>>>
>>> Thanks for this information.
>>> I will try to reproduce it with Tango 9 and TangoTest with the final 
>>> objective to consult it on the Tango Forum.
>>>
>>> I will get back to you,
>>> Zibi
>>>
>>>
>>> On 02/02/2016 11:24 AM, Roberto Borghes wrote:
>>>> Hi Zibi,
>>>> in both cases I use taurusform from the command line with the 
>>>> device name as argument, then I click the button "Show Device".
>>>> In this modality all the attributes are showed (also State and Status).
>>>> Currently we're not using events, so Taurus is polling the readings.
>>>>
>>>> Ciao,
>>>>     Roberto
>>>>
>>>>
>>>> On 02/02/2016 10:42, Zbigniew Reszela wrote:
>>>>> Hi Roberto,
>>>>>
>>>>> So you start directly a taurusform with these 18 DevShort and 18 
>>>>> DevBoolean attributes, don't you?
>>>>> There is nothing else in the form? (no State, Status?).
>>>>> Do these attributes emit events? or it is Taurus who polls them?
>>>>>
>>>>> Good that you have reproduced it with TangoTest. Which attributes 
>>>>> do you monitor in this case? All of the attributes of TangoTest?
>>>>> I will move to Tango 9 to check if the problem also exist there.
>>>>>
>>>>> Cheers,
>>>>> Zibi
>>>>>
>>>>> On 02/02/2016 10:00 AM, Roberto Borghes wrote:
>>>>>> Hi Zibi,
>>>>>> thank you for your analysis. I don't have any graph to show you 
>>>>>> but I can confirm that the memory consumption is slow and constant.
>>>>>> Obviously the ratio depends on the number of attributes. The 
>>>>>> device we're monitoring has 18 DevShort attributes and 18 
>>>>>> DevBoolean attributes.
>>>>>> Since yesterday, this device gained approximately 30 MB of memory 
>>>>>> in 18 hours.
>>>>>>
>>>>>> But I've another information for you: the TangoTest device seems 
>>>>>> to have the same problem. The memory consumption is slower but 
>>>>>> does exists.
>>>>>>
>>>>>> Ciao,
>>>>>>     Roberto
>>>>>>
>>>>>>
>>>>>> On 02/02/2016 09:26, Zbigniew Reszela wrote:
>>>>>>> Good morning!
>>>>>>>
>>>>>>> I have also observed slight increase in the memory - approx. 2 
>>>>>>> Mb per 14 hours.
>>>>>>> I explain you the setup which I used to monitor that.
>>>>>>> I simultaneously restarted two Python device servers (each of 
>>>>>>> them exporting just one device), and their baseline memory 
>>>>>>> footprint was:
>>>>>>>
>>>>>>> 24071 sicilia   20   0  178m  30m  16m S    1  1.2 0:03.13 
>>>>>>> python PyAlbaEm.py BL22_DI_EMET-01
>>>>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2 0:03.23 
>>>>>>> python PyAlbaEm.py BL22_DI_EMET-02
>>>>>>>
>>>>>>> Then I have started a taurusform monitoring some models from the 
>>>>>>> BL22_DI_EMET-01 instance. The other instance was not monitored 
>>>>>>> by any GUI.
>>>>>>> These models were (in total 11):
>>>>>>> * the device itself
>>>>>>> * SCALAR DevDouble (for this one I have started polling every 3 
>>>>>>> seconds, with a very demanding absolute change threshold, making 
>>>>>>> it emitting events almost every polling period)
>>>>>>> * 2 x SCALAR DevString attribute
>>>>>>> * SCALAR DevBoolean attribute
>>>>>>> * SCALAR DevLong attribute
>>>>>>> * 2 x SPECTRUM DevString attribute
>>>>>>> * SPECTRUM DevDouble attribute
>>>>>>> * State
>>>>>>> * Status
>>>>>>>
>>>>>>> After 14 hours the memory footprint was:
>>>>>>>
>>>>>>> 24071 sicilia   20   0  172m  32m  16m S    1  1.3 6:56.07 
>>>>>>> python PyAlbaEm.py BL22_DI_EMET-01
>>>>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2 6:18.53 
>>>>>>> python PyAlbaEm.py BL22_DI_EMET-02
>>>>>>>
>>>>>>> See the attached plot with the memory consumption evolution.
>>>>>>>
>>>>>>> What is exactly your setup? Do you see similar leak?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Zibi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>>>>>>>> Hi Roberto!
>>>>>>>>
>>>>>>>> I'll move this discussion to the taurus-devel mailing list 
>>>>>>>> (recently the Sardana and Taurus had separated their 
>>>>>>>> SourceForge infrastructure)
>>>>>>>>
>>>>>>>> Here at Alba we use the following versions of the software:
>>>>>>>>
>>>>>>>> * server side:
>>>>>>>> ** OpenSUSE 11.3 32 bits
>>>>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>>>>> ** PyTango 8.1.4
>>>>>>>>
>>>>>>>> * client side:
>>>>>>>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>>>>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>>>>> ** PyTango 8.1.4
>>>>>>>> ** we try to follow the develop branch of Taurus (it is at 
>>>>>>>> least 3.6.0)
>>>>>>>>
>>>>>>>> AFAIK we do not observe the memory leaks. But just in case I 
>>>>>>>> will leave a taurusform with few attributes and devices running 
>>>>>>>> overnight.
>>>>>>>> Tomorrow I will get back to you with the results.
>>>>>>>>
>>>>>>>> Meanwhile could you provide us more information:
>>>>>>>> * how many attributes / devices (models) do you have in your form.
>>>>>>>> * what type of attributes do you use? SPECTRUM, SCALAR, 
>>>>>>>> DevFloat, DevLong, etc...
>>>>>>>> * do the attributes emit events? are they polled by the server?
>>>>>>>> * are your models coming from the default TANGO_HOST of the 
>>>>>>>> client machine? or you specify the model names with the 
>>>>>>>> explicit tango database and port?
>>>>>>>> * how do you choose them? specifying the models as the 
>>>>>>>> execution parameters? or from the model chooser? or with the 
>>>>>>>> drag&drop mechanism? or maybe you programmed taurusform GUI 
>>>>>>>> with the hardcoded models?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Zibi
>>>>>>>>
>>>>>>>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>>>>>>>> Hi everybody,
>>>>>>>>> here at Elettra we're facing a mysterious memory leak with some python
>>>>>>>>> device servers.
>>>>>>>>> The strangefact is that the memory leaks do appear only using taurus
>>>>>>>>> clients (like taurusform)
>>>>>>>>> , using atkpanel there is no memory increasing...
>>>>>>>>>
>>>>>>>>> If nobody faced this problem till now probably we've something wrong
>>>>>>>>> with our installation:
>>>>>>>>>
>>>>>>>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>>>>>>>
>>>>>>>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>>>>>>>
>>>>>>>>> Any information will be helpful.
>>>>>>>>> Thank you in advance,
>>>>>>>>>
>>>>>>>>>       Roberto
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>>>>>>> Monitor end-to-end web transactions and take corrective actions now
>>>>>>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>>>>>>>> _______________________________________________
>>>>>>>>> Sardana-devel mailing list
>>>>>>>>> Sar...@li...
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>>>>>>>
>>>>>>>> -- 
>>>>>>>>
>>>>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>>>>
>>>>>>>> 	Zbigniew Reszela
>>>>>>>> Controls Section - Computing Division
>>>>>>>>
>>>>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| 
>>>>>>>> Barcelona | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>>>>> (+34) 93 592 4407
>>>>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>>>>
>>>>>>>> **Please, do not print this e-mail unless it is absolutely 
>>>>>>>> necessary.
>>>>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>>>>> contenir informació confidencial i privada i que està prohibit 
>>>>>>>> el seu ús. Us agrairíem que ho comuniqueu al remitent i 
>>>>>>>> l'elimineu. Gràcies.
>>>>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>>>>> contener información confidencial y privada y que está 
>>>>>>>> prohibido su uso. Le agradeceré que lo comunique a su remitente 
>>>>>>>> y lo elimine. Gracias.
>>>>>>>> If you have received this e-mail in error, please note that it 
>>>>>>>> may contain confidential and private information, therefore, 
>>>>>>>> the use of this information is strictly forbidden. Please 
>>>>>>>> inform the sender of the error and delete the information 
>>>>>>>> received. Thank you.
>>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>>
>>>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>>>
>>>>>>> 	Zbigniew Reszela
>>>>>>> Controls Section - Computing Division
>>>>>>>
>>>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| 
>>>>>>> Barcelona | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>>>> (+34) 93 592 4407
>>>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>>>
>>>>>>> **Please, do not print this e-mail unless it is absolutely 
>>>>>>> necessary.
>>>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>>>> contenir informació confidencial i privada i que està prohibit 
>>>>>>> el seu ús. Us agrairíem que ho comuniqueu al remitent i 
>>>>>>> l'elimineu. Gràcies.
>>>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>>>> contener información confidencial y privada y que está prohibido 
>>>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>>>> elimine. Gracias.
>>>>>>> If you have received this e-mail in error, please note that it 
>>>>>>> may contain confidential and private information, therefore, the 
>>>>>>> use of this information is strictly forbidden. Please inform the 
>>>>>>> sender of the error and delete the information received. Thank you.
>>>>>>>
>>>>>>
>>>>>
>>>>> -- 
>>>>>
>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>
>>>>> 	Zbigniew Reszela
>>>>> Controls Section - Computing Division
>>>>>
>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona 
>>>>> | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>> (+34) 93 592 4407
>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>
>>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>> contenir informació confidencial i privada i que està prohibit el 
>>>>> seu ús. Us agrairíem que ho comuniqueu al remitent i l'elimineu. 
>>>>> Gràcies.
>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>> contener información confidencial y privada y que está prohibido 
>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>> elimine. Gracias.
>>>>> If you have received this e-mail in error, please note that it may 
>>>>> contain confidential and private information, therefore, the use 
>>>>> of this information is strictly forbidden. Please inform the 
>>>>> sender of the error and delete the information received. Thank you.
>>>>>
>>>>
>>>
>>> -- 
>>>
>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>
>>> 	Zbigniew Reszela
>>> Controls Section - Computing Division
>>>
>>> ALBA SYNCHROTRON LIGHT SOURCE
>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>> (+34) 93 592 4407
>>> www.albasynchrotron.es| zre...@ce...
>>>
>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>> Si ha recibido este correo por error, le informo de que puede 
>>> contener información confidencial y privada y que está prohibido su 
>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>> Gracias.
>>> If you have received this e-mail in error, please note that it may 
>>> contain confidential and private information, therefore, the use of 
>>> this information is strictly forbidden. Please inform the sender of 
>>> the error and delete the information received. Thank you.
>>>
>>
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

[tauruslib-devel] IMPORTANT: merge taurus4-preview into develop is coming!

[Carlos P. <cpa...@ce...>]

Hi all, 

As already mentioned in [1] and [2], our intention was to merge the 
taurus4 into the develop branch right after the Jan16 release.

The time has come, and I would like to ask all of you a bit of your time 
to do a detailed test and revision of the code currently in the 
taurus4-preview branch [3] so that we can proceed with the merge. 

Our intention is to do the merge ASAP (because in the meanwhile we are 
blocking other integrations to develop. So unless someone complains, I 
will schedule it for Tuesday 15th of March (or sooner if I get the ok of 
the reviewers before that).

Cheers

Notes:
----------

Note 1: merging taurus4-preview into develop basically implies 
accepting both TEP3 and TEP14. TEP3 document is already in CANDIDATE, 
but TEP14 is still in DRAFT. While you are busy reviewing the code, I 
will try to complete the TEP14 doc to reflect the proposed code in the 
taurus4-preview branch and promote it to CANDIDATE before the merge 
date. Then, if the merge is accepted, we will pas TEP3 and TEP14  to 
ACCEPTED

Note 2: you can find a list of specific taurus4 release-critical bugs [4].

Note 3: I will also proceed to fix ticket 234 [5] before the merge.

Note 4: taurus4-preview is currently passing all automated tests [6]


Links:
---------

[1] http://sf.net/p/tauruslib/taurus-devel/message/34641275/
[2] http://sf.net/p/tauruslib/taurus-devel/message/34643400/
[3] http://sf.net/p/tauruslib/taurus.git/ci/taurus4-preview/tree/
[4] http://sf.net/p/tauruslib/tickets/milestone/taurus4/
[5] http://sf.net/p/tauruslib/tickets/234/
[6] https://travis-ci.org/cpascual/taurus/builds/112601736

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] New release of Taurus 3.7.0 (Jan16)

[PICCA Frederic-E. <fre...@sy...>]

Hello carlos.

Thanks a lot

Do you have a script which can be run in order to test taurus during the build process or in the debian ci integration system ?

Cheers

Fred

[tauruslib-devel] New release of Taurus 3.7.0 (Jan16)

[Carlos P. <cpa...@ce...>]

Hi all,

The new Taurus release 3.7.0 (corresponding to the Jan16 milestone) is 
now available to download from PyPI  (source and windows installer):
    
    http://pypi.python.org/pypi/taurus/3.7.0

To install using pip, run:

    pip install taurus --egg

To install from source, download the tar.gz from pypi, untar and run:
    
    python setup.py install 


The documentation is available at:

    http://www.taurus-scada.org

The main improvements since taurus 3.6.0 (aka Jul15) are:
    
    - Added support for sqlite DB in Tango (ticket #148)
    - Fixed many usability bugs in TaurusTrend2D and other
      guiqwt-based widgets (#238, #240, #244, #247, #251, #258)
    - Fixed issues with "export to ASCII" feature of plots
    - Fixed issues with PLY optimization (#262)
    - "taurus-polling-period" argument works for evaluation
      attributes now too (#249)
    - many other bugs fixed
    
For a detailed list of solved issues, see:

      http://sf.net/p/tauruslib/tickets/milestone/Jan16/
    
or, for a full log of commits, run (in your git repo):

      git log 3.6.0..3.7.0

If you encounter problems installing or running this release, please
report them back to the taurus mailing list:

    tau...@li...

or put a ticket in the taurus project:

    http://sourceforge.net/p/tauruslib/tickets/

Cheers!

Carlos (on behalf of the taurus developers)


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] client dependent memory leak

[Zbigniew R. <zre...@ce...>]

HI Roberto,

Sorry for the late answer, but this week I could only dedicate some 
spare gaps of time to this problem.

First of all, good that the re-installation of Tango made your memleak 
disappear.

Then, what is strange to me are the results of my tests. I've done them 
at our beamline, which in theory is using the same version (latest 8.1.2 
patched) in which you have seen the leak to disappear. But let me 
crosscheck it with my colleagues.

Since I had no access to the beamline anymore, I had continued tests at 
my development environment.
And I'm sure that I'm using the latest 8.1.2 patched version. I have not 
observer any memleak in TangoTest.
I have also prepared a dummy DS (C++) with 10 attributes (5 scalar 
shorts and 5 scalar booleans) and I have checked them both on latest 
8.1.2 patched version and on the 9.1.0. No leak was observed.
I have it pending to check it with PyTango...

But maybe as you said the latest 8.1.2 patched version solves it, and we 
do not use it in production...
I will get back to you when I have more information.

Cheers,
Zibi

On 02/10/2016 10:10 AM, Roberto Borghes wrote:
> Hi Zibi,
> the problem seems to be solved by installing the patched version of 
> Tango 8.1.2 available on http://www.tango-controls.org.
> Yesterday I've compiled it and everything seems ok!
>
> Ciao,
>     Roberto
>
>
>
> On 02/02/2016 16:40, Zbigniew Reszela wrote:
>> Hi Roberto,
>>
>> Thanks for this information.
>> I will try to reproduce it with Tango 9 and TangoTest with the final 
>> objective to consult it on the Tango Forum.
>>
>> I will get back to you,
>> Zibi
>>
>>
>> On 02/02/2016 11:24 AM, Roberto Borghes wrote:
>>> Hi Zibi,
>>> in both cases I use taurusform from the command line with the device 
>>> name as argument, then I click the button "Show Device".
>>> In this modality all the attributes are showed (also State and Status).
>>> Currently we're not using events, so Taurus is polling the readings.
>>>
>>> Ciao,
>>>     Roberto
>>>
>>>
>>> On 02/02/2016 10:42, Zbigniew Reszela wrote:
>>>> Hi Roberto,
>>>>
>>>> So you start directly a taurusform with these 18 DevShort and 18 
>>>> DevBoolean attributes, don't you?
>>>> There is nothing else in the form? (no State, Status?).
>>>> Do these attributes emit events? or it is Taurus who polls them?
>>>>
>>>> Good that you have reproduced it with TangoTest. Which attributes 
>>>> do you monitor in this case? All of the attributes of TangoTest?
>>>> I will move to Tango 9 to check if the problem also exist there.
>>>>
>>>> Cheers,
>>>> Zibi
>>>>
>>>> On 02/02/2016 10:00 AM, Roberto Borghes wrote:
>>>>> Hi Zibi,
>>>>> thank you for your analysis. I don't have any graph to show you 
>>>>> but I can confirm that the memory consumption is slow and constant.
>>>>> Obviously the ratio depends on the number of attributes. The 
>>>>> device we're monitoring has 18 DevShort attributes and 18 
>>>>> DevBoolean attributes.
>>>>> Since yesterday, this device gained approximately 30 MB of memory 
>>>>> in 18 hours.
>>>>>
>>>>> But I've another information for you: the TangoTest device seems 
>>>>> to have the same problem. The memory consumption is slower but 
>>>>> does exists.
>>>>>
>>>>> Ciao,
>>>>>     Roberto
>>>>>
>>>>>
>>>>> On 02/02/2016 09:26, Zbigniew Reszela wrote:
>>>>>> Good morning!
>>>>>>
>>>>>> I have also observed slight increase in the memory - approx. 2 Mb 
>>>>>> per 14 hours.
>>>>>> I explain you the setup which I used to monitor that.
>>>>>> I simultaneously restarted two Python device servers (each of 
>>>>>> them exporting just one device), and their baseline memory 
>>>>>> footprint was:
>>>>>>
>>>>>> 24071 sicilia   20   0  178m  30m  16m S    1  1.2 0:03.13 python 
>>>>>> PyAlbaEm.py BL22_DI_EMET-01
>>>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2 0:03.23 python 
>>>>>> PyAlbaEm.py BL22_DI_EMET-02
>>>>>>
>>>>>> Then I have started a taurusform monitoring some models from the 
>>>>>> BL22_DI_EMET-01 instance. The other instance was not monitored by 
>>>>>> any GUI.
>>>>>> These models were (in total 11):
>>>>>> * the device itself
>>>>>> * SCALAR DevDouble (for this one I have started polling every 3 
>>>>>> seconds, with a very demanding absolute change threshold, making 
>>>>>> it emitting events almost every polling period)
>>>>>> * 2 x SCALAR DevString attribute
>>>>>> * SCALAR DevBoolean attribute
>>>>>> * SCALAR DevLong attribute
>>>>>> * 2 x SPECTRUM DevString attribute
>>>>>> * SPECTRUM DevDouble attribute
>>>>>> * State
>>>>>> * Status
>>>>>>
>>>>>> After 14 hours the memory footprint was:
>>>>>>
>>>>>> 24071 sicilia   20   0  172m  32m  16m S    1  1.3 6:56.07 python 
>>>>>> PyAlbaEm.py BL22_DI_EMET-01
>>>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2 6:18.53 python 
>>>>>> PyAlbaEm.py BL22_DI_EMET-02
>>>>>>
>>>>>> See the attached plot with the memory consumption evolution.
>>>>>>
>>>>>> What is exactly your setup? Do you see similar leak?
>>>>>>
>>>>>> Thanks,
>>>>>> Zibi
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>>>>>>> Hi Roberto!
>>>>>>>
>>>>>>> I'll move this discussion to the taurus-devel mailing list 
>>>>>>> (recently the Sardana and Taurus had separated their SourceForge 
>>>>>>> infrastructure)
>>>>>>>
>>>>>>> Here at Alba we use the following versions of the software:
>>>>>>>
>>>>>>> * server side:
>>>>>>> ** OpenSUSE 11.3 32 bits
>>>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>>>> ** PyTango 8.1.4
>>>>>>>
>>>>>>> * client side:
>>>>>>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>>>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>>>> ** PyTango 8.1.4
>>>>>>> ** we try to follow the develop branch of Taurus (it is at least 
>>>>>>> 3.6.0)
>>>>>>>
>>>>>>> AFAIK we do not observe the memory leaks. But just in case I 
>>>>>>> will leave a taurusform with few attributes and devices running 
>>>>>>> overnight.
>>>>>>> Tomorrow I will get back to you with the results.
>>>>>>>
>>>>>>> Meanwhile could you provide us more information:
>>>>>>> * how many attributes / devices (models) do you have in your form.
>>>>>>> * what type of attributes do you use? SPECTRUM, SCALAR, 
>>>>>>> DevFloat, DevLong, etc...
>>>>>>> * do the attributes emit events? are they polled by the server?
>>>>>>> * are your models coming from the default TANGO_HOST of the 
>>>>>>> client machine? or you specify the model names with the explicit 
>>>>>>> tango database and port?
>>>>>>> * how do you choose them? specifying the models as the execution 
>>>>>>> parameters? or from the model chooser? or with the drag&drop 
>>>>>>> mechanism? or maybe you programmed taurusform GUI with the 
>>>>>>> hardcoded models?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Zibi
>>>>>>>
>>>>>>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>>>>>>> Hi everybody,
>>>>>>>> here at Elettra we're facing a mysterious memory leak with some python
>>>>>>>> device servers.
>>>>>>>> The strangefact is that the memory leaks do appear only using taurus
>>>>>>>> clients (like taurusform)
>>>>>>>> , using atkpanel there is no memory increasing...
>>>>>>>>
>>>>>>>> If nobody faced this problem till now probably we've something wrong
>>>>>>>> with our installation:
>>>>>>>>
>>>>>>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>>>>>>
>>>>>>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>>>>>>
>>>>>>>> Any information will be helpful.
>>>>>>>> Thank you in advance,
>>>>>>>>
>>>>>>>>       Roberto
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>>>>>> Monitor end-to-end web transactions and take corrective actions now
>>>>>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>>>>>>> _______________________________________________
>>>>>>>> Sardana-devel mailing list
>>>>>>>> Sar...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>>>>>>
>>>>>>> -- 
>>>>>>>
>>>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>>>
>>>>>>> 	Zbigniew Reszela
>>>>>>> Controls Section - Computing Division
>>>>>>>
>>>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| 
>>>>>>> Barcelona | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>>>> (+34) 93 592 4407
>>>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>>>
>>>>>>> **Please, do not print this e-mail unless it is absolutely 
>>>>>>> necessary.
>>>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>>>> contenir informació confidencial i privada i que està prohibit 
>>>>>>> el seu ús. Us agrairíem que ho comuniqueu al remitent i 
>>>>>>> l'elimineu. Gràcies.
>>>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>>>> contener información confidencial y privada y que está prohibido 
>>>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>>>> elimine. Gracias.
>>>>>>> If you have received this e-mail in error, please note that it 
>>>>>>> may contain confidential and private information, therefore, the 
>>>>>>> use of this information is strictly forbidden. Please inform the 
>>>>>>> sender of the error and delete the information received. Thank you.
>>>>>>>
>>>>>>
>>>>>> -- 
>>>>>>
>>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>>
>>>>>> 	Zbigniew Reszela
>>>>>> Controls Section - Computing Division
>>>>>>
>>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona 
>>>>>> | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>>> (+34) 93 592 4407
>>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>>
>>>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>>> contenir informació confidencial i privada i que està prohibit el 
>>>>>> seu ús. Us agrairíem que ho comuniqueu al remitent i l'elimineu. 
>>>>>> Gràcies.
>>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>>> contener información confidencial y privada y que está prohibido 
>>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>>> elimine. Gracias.
>>>>>> If you have received this e-mail in error, please note that it 
>>>>>> may contain confidential and private information, therefore, the 
>>>>>> use of this information is strictly forbidden. Please inform the 
>>>>>> sender of the error and delete the information received. Thank you.
>>>>>>
>>>>>
>>>>
>>>> -- 
>>>>
>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>
>>>> 	Zbigniew Reszela
>>>> Controls Section - Computing Division
>>>>
>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>> (+34) 93 592 4407
>>>> www.albasynchrotron.es| zre...@ce...
>>>>
>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>>> Si ha recibido este correo por error, le informo de que puede 
>>>> contener información confidencial y privada y que está prohibido su 
>>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>>> Gracias.
>>>> If you have received this e-mail in error, please note that it may 
>>>> contain confidential and private information, therefore, the use of 
>>>> this information is strictly forbidden. Please inform the sender of 
>>>> the error and delete the information received. Thank you.
>>>>
>>>
>>
>> -- 
>>
>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>
>> 	Zbigniew Reszela
>> Controls Section - Computing Division
>>
>> ALBA SYNCHROTRON LIGHT SOURCE
>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>> (+34) 93 592 4407
>> www.albasynchrotron.es| zre...@ce...
>>
>> **Please, do not print this e-mail unless it is absolutely necessary.
>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>> informació confidencial i privada i que està prohibit el seu ús. Us 
>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>> Si ha recibido este correo por error, le informo de que puede 
>> contener información confidencial y privada y que está prohibido su 
>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. Gracias.
>> If you have received this e-mail in error, please note that it may 
>> contain confidential and private information, therefore, the use of 
>> this information is strictly forbidden. Please inform the sender of 
>> the error and delete the information received. Thank you.
>>
>

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

Re: [tauruslib-devel] [tauruslib:tickets] #262 Set PLY optimization in build time

[Sergi R. <sr...@ce...>]

I'm in favour of this last solution, having yacctab/lextab generated on 
runtime at user's home. Many of the portability problems we had with 
these files would have been avoided if they were user-specific.

Thanks,

Sergi Rubio


On 02/10/2016 10:12 AM, Carlos Pascual wrote:
>
> I had a look, and this one is tricky...
>
> If you avoid generating the lex/yacc tab files during build time, you 
> end up with an installation that lacks those files in the installation 
> dir. The problem with this is that if the user running a GUI that uses 
> jdraw (i.e. containing a synoptic) does not have write permissions to 
> the installation dir (which is a quite standard situation), she will 
> get the following WARNING:
>
> JDraw Parser: Couldn't create 'taurus.qt.qtgui.graphic.jdraw.jdraw_yacctab'. [Errno 13] Permission denied
>
> This happens *even if the PLY_OPTIMIZE is set to 0 in the 
> tauruscustomsettings* (and if PLY_OPTIMIZE is set to 1, an additional 
> complain occurs for jdraw_lextab)
>
> Proposal: we can change so that the lex/yacc tab files are created 
> only at run time, and only in the home dir (e.g. as 
> ~/.taurus/lextab.py and ~/.taurus/yacctab.py)
>
> ------------------------------------------------------------------------
>
> *[tickets:#262] <http://sourceforge.net/p/tauruslib/tickets/262/> Set 
> PLY optimization in build time*
>
> *Status:* waiting
> *Milestone:* unassigned
> *Labels:* setup PLY
> *Created:* Wed Feb 10, 2016 07:22 AM UTC by Carlos Falcon
> *Last Updated:* Wed Feb 10, 2016 07:22 AM UTC
> *Owner:* nobody
>
> Hi,
> I would like to setup the PLY (lex/tacc) optimization in "build time" 
> . So, Could be possible to add this option in the setup?.
>
> Meanwhile, Could be changed the default mode in the 
> tauruscustomsettings ? Move from Active to disabled.
>
> Thanks,
> C.Falcon
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because 
> tau...@li... is subscribed to 
> https://sourceforge.net/p/tauruslib/tickets/
>
> To unsubscribe from further messages, a project admin can change 
> settings at https://sourceforge.net/p/tauruslib/admin/tickets/options. 
> Or, if this is a mailing list, you can unsubscribe from the mailing list.
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>
>
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

Re: [tauruslib-devel] client dependent memory leak

[Roberto B. <rob...@el...>]

Hi Zibi,
the problem seems to be solved by installing the patched version of 
Tango 8.1.2 available on http://www.tango-controls.org.
Yesterday I've compiled it and everything seems ok!

Ciao,
     Roberto



On 02/02/2016 16:40, Zbigniew Reszela wrote:
> Hi Roberto,
>
> Thanks for this information.
> I will try to reproduce it with Tango 9 and TangoTest with the final 
> objective to consult it on the Tango Forum.
>
> I will get back to you,
> Zibi
>
>
> On 02/02/2016 11:24 AM, Roberto Borghes wrote:
>> Hi Zibi,
>> in both cases I use taurusform from the command line with the device 
>> name as argument, then I click the button "Show Device".
>> In this modality all the attributes are showed (also State and Status).
>> Currently we're not using events, so Taurus is polling the readings.
>>
>> Ciao,
>>     Roberto
>>
>>
>> On 02/02/2016 10:42, Zbigniew Reszela wrote:
>>> Hi Roberto,
>>>
>>> So you start directly a taurusform with these 18 DevShort and 18 
>>> DevBoolean attributes, don't you?
>>> There is nothing else in the form? (no State, Status?).
>>> Do these attributes emit events? or it is Taurus who polls them?
>>>
>>> Good that you have reproduced it with TangoTest. Which attributes do 
>>> you monitor in this case? All of the attributes of TangoTest?
>>> I will move to Tango 9 to check if the problem also exist there.
>>>
>>> Cheers,
>>> Zibi
>>>
>>> On 02/02/2016 10:00 AM, Roberto Borghes wrote:
>>>> Hi Zibi,
>>>> thank you for your analysis. I don't have any graph to show you but 
>>>> I can confirm that the memory consumption is slow and constant.
>>>> Obviously the ratio depends on the number of attributes. The device 
>>>> we're monitoring has 18 DevShort attributes and 18 DevBoolean 
>>>> attributes.
>>>> Since yesterday, this device gained approximately 30 MB of memory 
>>>> in 18 hours.
>>>>
>>>> But I've another information for you: the TangoTest device seems to 
>>>> have the same problem. The memory consumption is slower but does 
>>>> exists.
>>>>
>>>> Ciao,
>>>>     Roberto
>>>>
>>>>
>>>> On 02/02/2016 09:26, Zbigniew Reszela wrote:
>>>>> Good morning!
>>>>>
>>>>> I have also observed slight increase in the memory - approx. 2 Mb 
>>>>> per 14 hours.
>>>>> I explain you the setup which I used to monitor that.
>>>>> I simultaneously restarted two Python device servers (each of them 
>>>>> exporting just one device), and their baseline memory footprint was:
>>>>>
>>>>> 24071 sicilia   20   0  178m  30m  16m S    1  1.2 0:03.13 python 
>>>>> PyAlbaEm.py BL22_DI_EMET-01
>>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2 0:03.23 python 
>>>>> PyAlbaEm.py BL22_DI_EMET-02
>>>>>
>>>>> Then I have started a taurusform monitoring some models from the 
>>>>> BL22_DI_EMET-01 instance. The other instance was not monitored by 
>>>>> any GUI.
>>>>> These models were (in total 11):
>>>>> * the device itself
>>>>> * SCALAR DevDouble (for this one I have started polling every 3 
>>>>> seconds, with a very demanding absolute change threshold, making 
>>>>> it emitting events almost every polling period)
>>>>> * 2 x SCALAR DevString attribute
>>>>> * SCALAR DevBoolean attribute
>>>>> * SCALAR DevLong attribute
>>>>> * 2 x SPECTRUM DevString attribute
>>>>> * SPECTRUM DevDouble attribute
>>>>> * State
>>>>> * Status
>>>>>
>>>>> After 14 hours the memory footprint was:
>>>>>
>>>>> 24071 sicilia   20   0  172m  32m  16m S    1  1.3 6:56.07 python 
>>>>> PyAlbaEm.py BL22_DI_EMET-01
>>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2 6:18.53 python 
>>>>> PyAlbaEm.py BL22_DI_EMET-02
>>>>>
>>>>> See the attached plot with the memory consumption evolution.
>>>>>
>>>>> What is exactly your setup? Do you see similar leak?
>>>>>
>>>>> Thanks,
>>>>> Zibi
>>>>>
>>>>>
>>>>>
>>>>> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>>>>>> Hi Roberto!
>>>>>>
>>>>>> I'll move this discussion to the taurus-devel mailing list 
>>>>>> (recently the Sardana and Taurus had separated their SourceForge 
>>>>>> infrastructure)
>>>>>>
>>>>>> Here at Alba we use the following versions of the software:
>>>>>>
>>>>>> * server side:
>>>>>> ** OpenSUSE 11.3 32 bits
>>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>>> ** PyTango 8.1.4
>>>>>>
>>>>>> * client side:
>>>>>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>>> ** PyTango 8.1.4
>>>>>> ** we try to follow the develop branch of Taurus (it is at least 
>>>>>> 3.6.0)
>>>>>>
>>>>>> AFAIK we do not observe the memory leaks. But just in case I will 
>>>>>> leave a taurusform with few attributes and devices running overnight.
>>>>>> Tomorrow I will get back to you with the results.
>>>>>>
>>>>>> Meanwhile could you provide us more information:
>>>>>> * how many attributes / devices (models) do you have in your form.
>>>>>> * what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
>>>>>> DevLong, etc...
>>>>>> * do the attributes emit events? are they polled by the server?
>>>>>> * are your models coming from the default TANGO_HOST of the 
>>>>>> client machine? or you specify the model names with the explicit 
>>>>>> tango database and port?
>>>>>> * how do you choose them? specifying the models as the execution 
>>>>>> parameters? or from the model chooser? or with the drag&drop 
>>>>>> mechanism? or maybe you programmed taurusform GUI with the 
>>>>>> hardcoded models?
>>>>>>
>>>>>> Cheers,
>>>>>> Zibi
>>>>>>
>>>>>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>>>>>> Hi everybody,
>>>>>>> here at Elettra we're facing a mysterious memory leak with some python
>>>>>>> device servers.
>>>>>>> The strangefact is that the memory leaks do appear only using taurus
>>>>>>> clients (like taurusform)
>>>>>>> , using atkpanel there is no memory increasing...
>>>>>>>
>>>>>>> If nobody faced this problem till now probably we've something wrong
>>>>>>> with our installation:
>>>>>>>
>>>>>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>>>>>
>>>>>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>>>>>
>>>>>>> Any information will be helpful.
>>>>>>> Thank you in advance,
>>>>>>>
>>>>>>>       Roberto
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>>>>> Monitor end-to-end web transactions and take corrective actions now
>>>>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>>>>>> _______________________________________________
>>>>>>> Sardana-devel mailing list
>>>>>>> Sar...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>>>>>
>>>>>> -- 
>>>>>>
>>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>>
>>>>>> 	Zbigniew Reszela
>>>>>> Controls Section - Computing Division
>>>>>>
>>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona 
>>>>>> | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>>> (+34) 93 592 4407
>>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>>
>>>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>>> contenir informació confidencial i privada i que està prohibit el 
>>>>>> seu ús. Us agrairíem que ho comuniqueu al remitent i l'elimineu. 
>>>>>> Gràcies.
>>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>>> contener información confidencial y privada y que está prohibido 
>>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>>> elimine. Gracias.
>>>>>> If you have received this e-mail in error, please note that it 
>>>>>> may contain confidential and private information, therefore, the 
>>>>>> use of this information is strictly forbidden. Please inform the 
>>>>>> sender of the error and delete the information received. Thank you.
>>>>>>
>>>>>
>>>>> -- 
>>>>>
>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>
>>>>> 	Zbigniew Reszela
>>>>> Controls Section - Computing Division
>>>>>
>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona 
>>>>> | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>> (+34) 93 592 4407
>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>
>>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>> contenir informació confidencial i privada i que està prohibit el 
>>>>> seu ús. Us agrairíem que ho comuniqueu al remitent i l'elimineu. 
>>>>> Gràcies.
>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>> contener información confidencial y privada y que está prohibido 
>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>> elimine. Gracias.
>>>>> If you have received this e-mail in error, please note that it may 
>>>>> contain confidential and private information, therefore, the use 
>>>>> of this information is strictly forbidden. Please inform the 
>>>>> sender of the error and delete the information received. Thank you.
>>>>>
>>>>
>>>
>>> -- 
>>>
>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>
>>> 	Zbigniew Reszela
>>> Controls Section - Computing Division
>>>
>>> ALBA SYNCHROTRON LIGHT SOURCE
>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>> (+34) 93 592 4407
>>> www.albasynchrotron.es| zre...@ce...
>>>
>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>> Si ha recibido este correo por error, le informo de que puede 
>>> contener información confidencial y privada y que está prohibido su 
>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>> Gracias.
>>> If you have received this e-mail in error, please note that it may 
>>> contain confidential and private information, therefore, the use of 
>>> this information is strictly forbidden. Please inform the sender of 
>>> the error and delete the information received. Thank you.
>>>
>>
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>

Re: [tauruslib-devel] client dependent memory leak

[Roberto B. <rob...@el...>]

03/02/2016 10:06
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104452348      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37073 (ESTABLISHED)
n03/02/2016 10:06
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104453167      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37077 (ESTABLISHED)
n03/02/2016 10:08
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104453167      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37077 (ESTABLISHED)
n03/02/2016 10:08
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104453972      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37078 (ESTABLISHED)
n03/02/2016 10:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104453972      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37078 (ESTABLISHED)
n03/02/2016 10:11
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104454785      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37081 (ESTABLISHED)
n03/02/2016 10:13
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104454785      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37081 (ESTABLISHED)
n03/02/2016 10:13
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104455554      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37082 (ESTABLISHED)
n03/02/2016 11:05
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104455554      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37082 (ESTABLISHED)
n03/02/2016 11:06
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104474612      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37103 (ESTABLISHED)
n03/02/2016 11:08
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104474612      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37103 (ESTABLISHED)
n03/02/2016 11:08
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104475440      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37105 (ESTABLISHED)
n03/02/2016 11:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104475440      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37105 (ESTABLISHED)
n03/02/2016 11:10
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104476232      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37107 (ESTABLISHED)
n03/02/2016 11:12
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104476232      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37107 (ESTABLISHED)
n03/02/2016 11:13
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104477013      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37110 (ESTABLISHED)
n03/02/2016 11:16
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104477013      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37110 (ESTABLISHED)
n03/02/2016 11:17
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104478440      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37112 (ESTABLISHED)
n03/02/2016 11:19
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104478440      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37112 (ESTABLISHED)
n03/02/2016 11:19
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104479226      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37113 (ESTABLISHED)
n03/02/2016 11:21
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104479226      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37113 (ESTABLISHED)
n03/02/2016 11:21
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104480030      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37115 (ESTABLISHED)
n03/02/2016 11:25
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104480030      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37115 (ESTABLISHED)
n03/02/2016 11:26
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104481444      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37134 (ESTABLISHED)
n03/02/2016 11:28
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104481444      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37134 (ESTABLISHED)
n03/02/2016 11:28
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104482942      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37135 (ESTABLISHED)
n03/02/2016 11:30
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104482942      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37135 (ESTABLISHED)
n03/02/2016 11:30
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104483747      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37137 (ESTABLISHED)
n03/02/2016 11:32
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104483747      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37137 (ESTABLISHED)
n03/02/2016 11:33
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104484544      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37141 (ESTABLISHED)
n03/02/2016 11:35
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104484544      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37141 (ESTABLISHED)
n03/02/2016 11:35
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104485294      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37146 (ESTABLISHED)
n03/02/2016 11:37
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104485294      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37146 (ESTABLISHED)
n03/02/2016 11:38
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104486085      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37148 (ESTABLISHED)
n03/02/2016 11:39
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104486085      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37148 (ESTABLISHED)
n03/02/2016 11:40
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104486893      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37151 (ESTABLISHED)
n03/02/2016 11:42
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104486893      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37151 (ESTABLISHED)
n03/02/2016 11:42
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104487671      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37152 (ESTABLISHED)
n03/02/2016 11:47
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104487671      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37152 (ESTABLISHED)
n03/02/2016 11:47
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104489241      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37156 (ESTABLISHED)
n03/02/2016 11:49
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104489241      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37156 (ESTABLISHED)
n03/02/2016 11:49
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104490024      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37159 (ESTABLISHED)
n03/02/2016 11:55
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104490024      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37159 (ESTABLISHED)
n03/02/2016 11:55
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104492036      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37162 (ESTABLISHED)
n03/02/2016 11:57
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104492036      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37162 (ESTABLISHED)
n03/02/2016 11:58
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104493551      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37177 (ESTABLISHED)
n03/02/2016 12:00
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104493551      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37177 (ESTABLISHED)
n03/02/2016 12:00
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104494360      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37178 (ESTABLISHED)
n03/02/2016 12:02
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104494360      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37178 (ESTABLISHED)
n03/02/2016 12:02
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104495170      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37180 (ESTABLISHED)
n03/02/2016 12:04
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104495170      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37180 (ESTABLISHED)
n03/02/2016 12:05
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104495923      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37182 (ESTABLISHED)
n03/02/2016 12:07
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104495923      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37182 (ESTABLISHED)
n03/02/2016 12:07
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104496743      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37198 (ESTABLISHED)
n03/02/2016 12:09
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104496743      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37198 (ESTABLISHED)
n03/02/2016 12:09
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104497509      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37201 (ESTABLISHED)
n03/02/2016 12:16
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104497509      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37201 (ESTABLISHED)
n03/02/2016 12:16
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104499740      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37206 (ESTABLISHED)
n03/02/2016 12:18
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104499740      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37206 (ESTABLISHED)
n03/02/2016 12:18
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104500527      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37210 (ESTABLISHED)
n03/02/2016 12:20
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104500527      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37210 (ESTABLISHED)
n03/02/2016 12:22
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104501939      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37212 (ESTABLISHED)
n03/02/2016 12:24
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104501939      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37212 (ESTABLISHED)
n03/02/2016 12:25
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104502679      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37246 (ESTABLISHED)
n03/02/2016 12:29
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104502679      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37246 (ESTABLISHED)
n03/02/2016 12:29
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104504865      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37251 (ESTABLISHED)
n03/02/2016 12:31
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104504865      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37251 (ESTABLISHED)
n03/02/2016 12:31
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104505676      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37252 (ESTABLISHED)
n03/02/2016 12:36
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104505676      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37252 (ESTABLISHED)
n03/02/2016 12:36
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104507228      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37256 (ESTABLISHED)
n03/02/2016 12:38
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104507228      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37256 (ESTABLISHED)
n03/02/2016 12:38
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104508029      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37258 (ESTABLISHED)
n03/02/2016 12:40
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104508029      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37258 (ESTABLISHED)
n03/02/2016 12:41
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104508815      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37261 (ESTABLISHED)
n03/02/2016 12:43
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104508815      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37261 (ESTABLISHED)
n03/02/2016 12:43
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104509623      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37265 (ESTABLISHED)
n03/02/2016 12:45
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104509623      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37265 (ESTABLISHED)
n03/02/2016 12:47
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104511009      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37268 (ESTABLISHED)
n03/02/2016 12:49
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104511009      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37268 (ESTABLISHED)
n03/02/2016 12:50
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104511829      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37271 (ESTABLISHED)
n03/02/2016 12:52
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104511829      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37271 (ESTABLISHED)
n03/02/2016 12:52
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104512638      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37274 (ESTABLISHED)
n03/02/2016 12:56
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104512638      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37274 (ESTABLISHED)
n03/02/2016 12:56
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104514029      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37279 (ESTABLISHED)
n03/02/2016 12:58
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104514029      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37279 (ESTABLISHED)
n03/02/2016 12:59
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104515539      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37281 (ESTABLISHED)
n03/02/2016 13:00
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104515539      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37281 (ESTABLISHED)
n03/02/2016 13:01
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104516372      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37283 (ESTABLISHED)
n03/02/2016 13:05
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104516372      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37283 (ESTABLISHED)
n03/02/2016 13:06
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104517916      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37288 (ESTABLISHED)
n03/02/2016 13:08
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104517916      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37288 (ESTABLISHED)
n03/02/2016 13:08
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104518742      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37290 (ESTABLISHED)
n03/02/2016 13:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104518742      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37290 (ESTABLISHED)
n03/02/2016 13:12
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104520146      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37292 (ESTABLISHED)
n03/02/2016 13:14
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104520146      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37292 (ESTABLISHED)
n03/02/2016 13:14
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104520909      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37294 (ESTABLISHED)
n03/02/2016 13:18
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104520909      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37294 (ESTABLISHED)
n03/02/2016 13:19
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104522503      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37298 (ESTABLISHED)
n03/02/2016 13:21
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104522503      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37298 (ESTABLISHED)
n03/02/2016 13:22
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104523311      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37300 (ESTABLISHED)
n03/02/2016 13:25
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104523311      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37300 (ESTABLISHED)
n03/02/2016 13:26
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104524676      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37304 (ESTABLISHED)
n03/02/2016 13:28
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104524676      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37304 (ESTABLISHED)
n03/02/2016 13:28
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104526234      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37306 (ESTABLISHED)
n03/02/2016 13:30
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104526234      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37306 (ESTABLISHED)
n03/02/2016 13:31
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104527039      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37308 (ESTABLISHED)
n03/02/2016 13:32
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104527039      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37308 (ESTABLISHED)
n03/02/2016 13:33
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104527770      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37311 (ESTABLISHED)
n03/02/2016 13:35
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104527770      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37311 (ESTABLISHED)
n03/02/2016 13:35
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104528579      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37315 (ESTABLISHED)
n03/02/2016 13:37
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104528579      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37315 (ESTABLISHED)
n03/02/2016 13:38
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104529375      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37317 (ESTABLISHED)
n03/02/2016 13:41
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104529375      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37317 (ESTABLISHED)
n03/02/2016 13:42
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104530806      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37320 (ESTABLISHED)
n03/02/2016 13:44
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104530806      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37320 (ESTABLISHED)
n03/02/2016 13:44
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104531569      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37322 (ESTABLISHED)
n03/02/2016 13:46
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104531569      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37322 (ESTABLISHED)
n03/02/2016 13:46
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104532341      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37324 (ESTABLISHED)
n03/02/2016 13:48
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104532341      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37324 (ESTABLISHED)
n03/02/2016 13:49
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104533140      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37325 (ESTABLISHED)
n03/02/2016 13:51
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104533140      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37325 (ESTABLISHED)
n03/02/2016 13:51
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104533959      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37341 (ESTABLISHED)
n03/02/2016 13:53
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104533959      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37341 (ESTABLISHED)
n03/02/2016 13:54
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104534768      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37355 (ESTABLISHED)
n03/02/2016 13:55
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104534768      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37355 (ESTABLISHED)
n03/02/2016 13:56
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104535531      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37369 (ESTABLISHED)
n03/02/2016 13:58
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104535531      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37369 (ESTABLISHED)
n03/02/2016 13:58
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104537064      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37371 (ESTABLISHED)
n03/02/2016 14:00
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104537064      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37371 (ESTABLISHED)
n03/02/2016 14:01
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104537862      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37387 (ESTABLISHED)
n03/02/2016 14:49
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104537862      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37387 (ESTABLISHED)
n03/02/2016 14:50
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104555229      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37461 (ESTABLISHED)
n03/02/2016 14:52
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104555229      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37461 (ESTABLISHED)
n03/02/2016 14:52
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104556005      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37464 (ESTABLISHED)
n03/02/2016 14:54
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104556005      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37464 (ESTABLISHED)
n03/02/2016 14:54
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104556780      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37466 (ESTABLISHED)
n03/02/2016 14:58
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104556780      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37466 (ESTABLISHED)
n03/02/2016 14:59
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104558942      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37468 (ESTABLISHED)
n03/02/2016 15:01
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104558942      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37468 (ESTABLISHED)
n03/02/2016 15:01
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104559750      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37470 (ESTABLISHED)
n03/02/2016 15:07
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104559750      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37470 (ESTABLISHED)
n03/02/2016 15:07
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104561772      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:neckar (ESTABLISHED)
n03/02/2016 15:11
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104561772      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:neckar (ESTABLISHED)
n03/02/2016 15:11
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104563233      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37477 (ESTABLISHED)
n03/02/2016 15:13
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104563233      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37477 (ESTABLISHED)
n03/02/2016 15:14
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104564021      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37479 (ESTABLISHED)
n03/02/2016 15:16
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104564021      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37479 (ESTABLISHED)
n03/02/2016 15:16
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104564782      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37481 (ESTABLISHED)
n03/02/2016 15:18
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104564782      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37481 (ESTABLISHED)
n03/02/2016 15:18
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104565603      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37483 (ESTABLISHED)
n03/02/2016 15:20
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104565603      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37483 (ESTABLISHED)
n03/02/2016 15:21
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104566415      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37487 (ESTABLISHED)
n03/02/2016 15:23
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104566415      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37487 (ESTABLISHED)
n03/02/2016 15:23
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104567171      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37493 (ESTABLISHED)
n03/02/2016 15:25
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104567171      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37493 (ESTABLISHED)
n03/02/2016 15:25
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104567968      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37497 (ESTABLISHED)
n03/02/2016 15:27
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104567968      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37497 (ESTABLISHED)
n03/02/2016 15:28
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104569464      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37502 (ESTABLISHED)
n03/02/2016 15:30
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104569464      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37502 (ESTABLISHED)
n03/02/2016 15:30
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104570228      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37503 (ESTABLISHED)
n03/02/2016 15:32
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104570228      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37503 (ESTABLISHED)
n03/02/2016 15:32
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104571051      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37507 (ESTABLISHED)
n03/02/2016 15:34
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104571051      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37507 (ESTABLISHED)
n03/02/2016 15:35
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104571806      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37509 (ESTABLISHED)
n03/02/2016 15:37
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104571806      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37509 (ESTABLISHED)
n03/02/2016 15:37
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104572593      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37511 (ESTABLISHED)
n03/02/2016 15:43
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104572593      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37511 (ESTABLISHED)
n03/02/2016 15:43
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104574644      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37517 (ESTABLISHED)
n03/02/2016 15:45
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104574644      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37517 (ESTABLISHED)
n03/02/2016 15:45
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104575431      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37518 (ESTABLISHED)
n03/02/2016 15:47
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104575431      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37518 (ESTABLISHED)
n03/02/2016 15:48
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104576261      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37519 (ESTABLISHED)
n03/02/2016 15:50
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104576261      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37519 (ESTABLISHED)
n03/02/2016 15:50
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104577020      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37522 (ESTABLISHED)
n03/02/2016 15:52
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104577020      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37522 (ESTABLISHED)
n03/02/2016 15:53
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104577833      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37525 (ESTABLISHED)
n03/02/2016 15:55
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104577833      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37525 (ESTABLISHED)
n03/02/2016 15:55
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104578600      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37528 (ESTABLISHED)
n03/02/2016 15:57
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104578600      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37528 (ESTABLISHED)
n03/02/2016 15:57
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104580076      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37536 (ESTABLISHED)
n03/02/2016 15:59
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104580076      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37536 (ESTABLISHED)
n03/02/2016 16:00
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104580917      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37539 (ESTABLISHED)
n03/02/2016 16:03
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104580917      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37539 (ESTABLISHED)
n03/02/2016 16:04
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104582359      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37543 (ESTABLISHED)
n03/02/2016 16:06
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104582359      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37543 (ESTABLISHED)
n03/02/2016 16:06
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104583128      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37547 (ESTABLISHED)
n03/02/2016 16:08
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104583128      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37547 (ESTABLISHED)
n03/02/2016 16:09
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104583967      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37549 (ESTABLISHED)
n03/02/2016 16:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104583967      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37549 (ESTABLISHED)
n03/02/2016 16:11
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104584763      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37551 (ESTABLISHED)
n03/02/2016 16:15
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104584763      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37551 (ESTABLISHED)
n03/02/2016 16:15
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104586136      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37553 (ESTABLISHED)
n03/02/2016 16:17
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104586136      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37553 (ESTABLISHED)
n03/02/2016 16:17
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104586908      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37555 (ESTABLISHED)
n03/02/2016 16:21
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104586908      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37555 (ESTABLISHED)
n03/02/2016 16:22
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104588378      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37559 (ESTABLISHED)
n03/02/2016 16:24
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104588378      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37559 (ESTABLISHED)
n03/02/2016 16:24
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104589140      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37561 (ESTABLISHED)
n03/02/2016 16:26
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104589140      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37561 (ESTABLISHED)
n03/02/2016 16:26
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104589892      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37565 (ESTABLISHED)
n03/02/2016 16:30
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104589892      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37565 (ESTABLISHED)
n03/02/2016 16:30
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104592068      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37570 (ESTABLISHED)
n03/02/2016 16:33
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104592068      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37570 (ESTABLISHED)
n03/02/2016 16:33
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104592846      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37577 (ESTABLISHED)
n03/02/2016 16:35
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104592846      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37577 (ESTABLISHED)
n03/02/2016 16:35
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104593585      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37580 (ESTABLISHED)
n03/02/2016 16:41
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104593585      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37580 (ESTABLISHED)
n03/02/2016 16:41
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104595635      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37587 (ESTABLISHED)
n03/02/2016 16:43
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104595635      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37587 (ESTABLISHED)
n03/02/2016 16:44
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104596439      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37588 (ESTABLISHED)
n03/02/2016 16:46
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104596439      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37588 (ESTABLISHED)
n03/02/2016 16:46
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104597226      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37590 (ESTABLISHED)
n03/02/2016 16:48
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104597226      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37590 (ESTABLISHED)
n03/02/2016 16:48
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104598002      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37592 (ESTABLISHED)
n03/02/2016 16:52
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104598002      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37592 (ESTABLISHED)
n03/02/2016 16:52
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104599449      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37598 (ESTABLISHED)
n03/02/2016 16:54
35c35
< TangoTest 9195 roberto.borghes    8u  IPv6          104600112      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37600 (ESTABLISHED)
---
> TangoTest 9195 roberto.borghes    8u  IPv6          104599449      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37598 (ESTABLISHED)
n03/02/2016 16:57
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104600112      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37600 (ESTABLISHED)
n03/02/2016 16:57
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104601688      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37603 (ESTABLISHED)
n03/02/2016 17:03
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104601688      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37603 (ESTABLISHED)
n03/02/2016 17:04
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104604005      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37606 (ESTABLISHED)
n03/02/2016 17:08
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104604005      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37606 (ESTABLISHED)
n03/02/2016 17:08
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104605446      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37611 (ESTABLISHED)
n03/02/2016 17:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104605446      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37611 (ESTABLISHED)
n03/02/2016 17:10
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104606238      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37614 (ESTABLISHED)
n03/02/2016 17:12
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104606238      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37614 (ESTABLISHED)
n03/02/2016 17:13
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104607059      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37615 (ESTABLISHED)
n03/02/2016 17:15
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104607059      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37615 (ESTABLISHED)
n03/02/2016 17:15
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104607841      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37618 (ESTABLISHED)
n03/02/2016 17:19
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104607841      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37618 (ESTABLISHED)
n03/02/2016 17:21
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104609926      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37624 (ESTABLISHED)
n03/02/2016 17:23
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104609926      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37624 (ESTABLISHED)
n03/02/2016 17:23
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104610696      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37626 (ESTABLISHED)
n03/02/2016 17:25
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104610696      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37626 (ESTABLISHED)
n03/02/2016 17:26
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104611544      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37627 (ESTABLISHED)
n03/02/2016 17:28
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104611544      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37627 (ESTABLISHED)
n03/02/2016 17:28
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104613055      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37629 (ESTABLISHED)
n03/02/2016 17:30
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104613055      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37629 (ESTABLISHED)
n03/02/2016 17:30
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104613829      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37632 (ESTABLISHED)
n03/02/2016 17:34
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104613829      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37632 (ESTABLISHED)
n03/02/2016 17:35
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104615284      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37635 (ESTABLISHED)
n03/02/2016 17:37
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104615284      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37635 (ESTABLISHED)
n03/02/2016 17:37
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104616071      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37638 (ESTABLISHED)
n03/02/2016 17:41
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104616071      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37638 (ESTABLISHED)
n03/02/2016 17:41
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104617535      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37640 (ESTABLISHED)
n03/02/2016 17:43
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104617535      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37640 (ESTABLISHED)
n03/02/2016 17:44
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104618317      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37642 (ESTABLISHED)
n03/02/2016 18:37
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104618317      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37642 (ESTABLISHED)
n03/02/2016 18:37
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104638191      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37675 (ESTABLISHED)
n03/02/2016 18:39
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104638191      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37675 (ESTABLISHED)
n03/02/2016 18:40
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104639075      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37677 (ESTABLISHED)
n03/02/2016 18:44
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104639075      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37677 (ESTABLISHED)
n03/02/2016 18:44
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104640493      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37679 (ESTABLISHED)
n03/02/2016 18:46
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104640493      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37679 (ESTABLISHED)
n03/02/2016 18:46
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104641269      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37682 (ESTABLISHED)
n03/02/2016 18:48
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104641269      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37682 (ESTABLISHED)
n03/02/2016 18:49
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104642056      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37683 (ESTABLISHED)
n03/02/2016 18:51
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104642056      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37683 (ESTABLISHED)
n03/02/2016 18:51
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104642916      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37684 (ESTABLISHED)
n03/02/2016 18:53
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104642916      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37684 (ESTABLISHED)
n03/02/2016 18:53
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104643687      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37688 (ESTABLISHED)
n03/02/2016 18:57
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104643687      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37688 (ESTABLISHED)
n03/02/2016 18:58
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104645795      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37690 (ESTABLISHED)
n03/02/2016 19:00
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104645795      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37690 (ESTABLISHED)
n03/02/2016 19:00
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104646677      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37693 (ESTABLISHED)
n03/02/2016 19:02
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104646677      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37693 (ESTABLISHED)
n03/02/2016 19:04
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104648105      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37704 (ESTABLISHED)
n03/02/2016 19:06
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104648105      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37704 (ESTABLISHED)
n03/02/2016 19:06
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104648898      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37706 (ESTABLISHED)
n03/02/2016 19:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104648898      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37706 (ESTABLISHED)
n03/02/2016 19:11
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104650340      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37710 (ESTABLISHED)
n03/02/2016 19:15
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104650340      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37710 (ESTABLISHED)
n03/02/2016 19:15
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104651792      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37714 (ESTABLISHED)
n03/02/2016 19:17
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104651792      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37714 (ESTABLISHED)
n03/02/2016 19:17
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104652568      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37716 (ESTABLISHED)
n03/02/2016 19:19
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104652568      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37716 (ESTABLISHED)
n03/02/2016 19:19
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104653356      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37720 (ESTABLISHED)
n03/02/2016 19:23
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104653356      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37720 (ESTABLISHED)
n03/02/2016 19:24
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104654832      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37724 (ESTABLISHED)
n03/02/2016 19:28
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104654832      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37724 (ESTABLISHED)
n03/02/2016 19:28
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104657050      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37729 (ESTABLISHED)
n03/02/2016 19:32
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104657050      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37729 (ESTABLISHED)
n03/02/2016 19:34
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104659106      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37734 (ESTABLISHED)
n03/02/2016 19:36
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104659106      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37734 (ESTABLISHED)
n03/02/2016 19:36
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104659882      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37735 (ESTABLISHED)
n03/02/2016 19:38
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104659882      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37735 (ESTABLISHED)
n03/02/2016 19:39
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104660654      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37740 (ESTABLISHED)
n03/02/2016 19:41
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104660654      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37740 (ESTABLISHED)
n03/02/2016 19:41
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104661510      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37742 (ESTABLISHED)
n03/02/2016 19:43
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104661510      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37742 (ESTABLISHED)
n03/02/2016 19:43
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104662292      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37743 (ESTABLISHED)
n03/02/2016 19:45
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104662292      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37743 (ESTABLISHED)
n03/02/2016 19:46
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104663079      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37746 (ESTABLISHED)
n03/02/2016 19:48
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104663079      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37746 (ESTABLISHED)
n03/02/2016 19:48
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104663929      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37748 (ESTABLISHED)
n03/02/2016 19:50
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104663929      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37748 (ESTABLISHED)
n03/02/2016 19:51
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104664735      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37750 (ESTABLISHED)
n03/02/2016 19:54
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104664735      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37750 (ESTABLISHED)
n03/02/2016 19:55
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104666124      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37754 (ESTABLISHED)
n03/02/2016 19:59
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104666124      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37754 (ESTABLISHED)
n03/02/2016 19:59
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104668282      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37759 (ESTABLISHED)
n03/02/2016 20:03
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104668282      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37759 (ESTABLISHED)
n03/02/2016 20:03
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104669784      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37763 (ESTABLISHED)
n03/02/2016 20:07
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104669784      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37763 (ESTABLISHED)
n03/02/2016 20:08
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104671362      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37765 (ESTABLISHED)
n03/02/2016 20:10
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104671362      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37765 (ESTABLISHED)
n03/02/2016 20:10
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104672174      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37767 (ESTABLISHED)
n03/02/2016 20:14
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104672174      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37767 (ESTABLISHED)
n03/02/2016 20:14
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104673590      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37771 (ESTABLISHED)
n03/02/2016 20:16
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104673590      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37771 (ESTABLISHED)
n03/02/2016 20:17
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104674378      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37773 (ESTABLISHED)
n03/02/2016 20:20
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104674378      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37773 (ESTABLISHED)
n03/02/2016 20:21
35d34
< TangoTest 9195 roberto.borghes    8u  IPv6          104675837      0t0       TCP kaori.esce.elettra.trieste.it:55707->nami.esce.elettra.trieste.it:37777 (ESTABLISHED)
n03/02/2016 20:25
34a35
> TangoTest 9195 roberto.borghes    8u  IPv6          104675837      0t0       TCP kaori.esce.elettra.trieste.it:...
 
[truncated message content]

Re: [tauruslib-devel] client dependent memory leak

[Zbigniew R. <zre...@ce...>]

Hi Roberto,

Thanks for this information.
I will try to reproduce it with Tango 9 and TangoTest with the final 
objective to consult it on the Tango Forum.

I will get back to you,
Zibi


On 02/02/2016 11:24 AM, Roberto Borghes wrote:
> Hi Zibi,
> in both cases I use taurusform from the command line with the device 
> name as argument, then I click the button "Show Device".
> In this modality all the attributes are showed (also State and Status).
> Currently we're not using events, so Taurus is polling the readings.
>
> Ciao,
>     Roberto
>
>
> On 02/02/2016 10:42, Zbigniew Reszela wrote:
>> Hi Roberto,
>>
>> So you start directly a taurusform with these 18 DevShort and 18 
>> DevBoolean attributes, don't you?
>> There is nothing else in the form? (no State, Status?).
>> Do these attributes emit events? or it is Taurus who polls them?
>>
>> Good that you have reproduced it with TangoTest. Which attributes do 
>> you monitor in this case? All of the attributes of TangoTest?
>> I will move to Tango 9 to check if the problem also exist there.
>>
>> Cheers,
>> Zibi
>>
>> On 02/02/2016 10:00 AM, Roberto Borghes wrote:
>>> Hi Zibi,
>>> thank you for your analysis. I don't have any graph to show you but 
>>> I can confirm that the memory consumption is slow and constant.
>>> Obviously the ratio depends on the number of attributes. The device 
>>> we're monitoring has 18 DevShort attributes and 18 DevBoolean 
>>> attributes.
>>> Since yesterday, this device gained approximately 30 MB of memory in 
>>> 18 hours.
>>>
>>> But I've another information for you: the TangoTest device seems to 
>>> have the same problem. The memory consumption is slower but does exists.
>>>
>>> Ciao,
>>>     Roberto
>>>
>>>
>>> On 02/02/2016 09:26, Zbigniew Reszela wrote:
>>>> Good morning!
>>>>
>>>> I have also observed slight increase in the memory - approx. 2 Mb 
>>>> per 14 hours.
>>>> I explain you the setup which I used to monitor that.
>>>> I simultaneously restarted two Python device servers (each of them 
>>>> exporting just one device), and their baseline memory footprint was:
>>>>
>>>> 24071 sicilia   20   0  178m  30m  16m S    1  1.2   0:03.13 python 
>>>> PyAlbaEm.py BL22_DI_EMET-01
>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   0:03.23 python 
>>>> PyAlbaEm.py BL22_DI_EMET-02
>>>>
>>>> Then I have started a taurusform monitoring some models from the 
>>>> BL22_DI_EMET-01 instance. The other instance was not monitored by 
>>>> any GUI.
>>>> These models were (in total 11):
>>>> * the device itself
>>>> * SCALAR DevDouble (for this one I have started polling every 3 
>>>> seconds, with a very demanding absolute change threshold, making it 
>>>> emitting events almost every polling period)
>>>> * 2 x SCALAR DevString attribute
>>>> * SCALAR DevBoolean attribute
>>>> * SCALAR DevLong attribute
>>>> * 2 x SPECTRUM DevString attribute
>>>> * SPECTRUM DevDouble attribute
>>>> * State
>>>> * Status
>>>>
>>>> After 14 hours the memory footprint was:
>>>>
>>>> 24071 sicilia   20   0  172m  32m  16m S    1  1.3   6:56.07 python 
>>>> PyAlbaEm.py BL22_DI_EMET-01
>>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   6:18.53 python 
>>>> PyAlbaEm.py BL22_DI_EMET-02
>>>>
>>>> See the attached plot with the memory consumption evolution.
>>>>
>>>> What is exactly your setup? Do you see similar leak?
>>>>
>>>> Thanks,
>>>> Zibi
>>>>
>>>>
>>>>
>>>> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>>>>> Hi Roberto!
>>>>>
>>>>> I'll move this discussion to the taurus-devel mailing list 
>>>>> (recently the Sardana and Taurus had separated their SourceForge 
>>>>> infrastructure)
>>>>>
>>>>> Here at Alba we use the following versions of the software:
>>>>>
>>>>> * server side:
>>>>> ** OpenSUSE 11.3 32 bits
>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>> ** PyTango 8.1.4
>>>>>
>>>>> * client side:
>>>>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>>> ** PyTango 8.1.4
>>>>> ** we try to follow the develop branch of Taurus (it is at least 
>>>>> 3.6.0)
>>>>>
>>>>> AFAIK we do not observe the memory leaks. But just in case I will 
>>>>> leave a taurusform with few attributes and devices running overnight.
>>>>> Tomorrow I will get back to you with the results.
>>>>>
>>>>> Meanwhile could you provide us more information:
>>>>> * how many attributes / devices (models) do you have in your form.
>>>>> * what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
>>>>> DevLong, etc...
>>>>> * do the attributes emit events? are they polled by the server?
>>>>> * are your models coming from the default TANGO_HOST of the client 
>>>>> machine? or you specify the model names with the explicit tango 
>>>>> database and port?
>>>>> * how do you choose them? specifying the models as the execution 
>>>>> parameters? or from the model chooser? or with the drag&drop 
>>>>> mechanism? or maybe you programmed taurusform GUI with the 
>>>>> hardcoded models?
>>>>>
>>>>> Cheers,
>>>>> Zibi
>>>>>
>>>>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>>>>> Hi everybody,
>>>>>> here at Elettra we're facing a mysterious memory leak with some python
>>>>>> device servers.
>>>>>> The strangefact is that the memory leaks do appear only using taurus
>>>>>> clients (like taurusform)
>>>>>> , using atkpanel there is no memory increasing...
>>>>>>
>>>>>> If nobody faced this problem till now probably we've something wrong
>>>>>> with our installation:
>>>>>>
>>>>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>>>>
>>>>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>>>>
>>>>>> Any information will be helpful.
>>>>>> Thank you in advance,
>>>>>>
>>>>>>       Roberto
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>>>> Monitor end-to-end web transactions and take corrective actions now
>>>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>>>>> _______________________________________________
>>>>>> Sardana-devel mailing list
>>>>>> Sar...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>>>>
>>>>> -- 
>>>>>
>>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>>
>>>>> 	Zbigniew Reszela
>>>>> Controls Section - Computing Division
>>>>>
>>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona 
>>>>> | Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>>> (+34) 93 592 4407
>>>>> www.albasynchrotron.es| zre...@ce...
>>>>>
>>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>>> **Si heu rebut aquest correu per error, us informo que pot 
>>>>> contenir informació confidencial i privada i que està prohibit el 
>>>>> seu ús. Us agrairíem que ho comuniqueu al remitent i l'elimineu. 
>>>>> Gràcies.
>>>>> Si ha recibido este correo por error, le informo de que puede 
>>>>> contener información confidencial y privada y que está prohibido 
>>>>> su uso. Le agradeceré que lo comunique a su remitente y lo 
>>>>> elimine. Gracias.
>>>>> If you have received this e-mail in error, please note that it may 
>>>>> contain confidential and private information, therefore, the use 
>>>>> of this information is strictly forbidden. Please inform the 
>>>>> sender of the error and delete the information received. Thank you.
>>>>>
>>>>
>>>> -- 
>>>>
>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>
>>>> 	Zbigniew Reszela
>>>> Controls Section - Computing Division
>>>>
>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>> (+34) 93 592 4407
>>>> www.albasynchrotron.es| zre...@ce...
>>>>
>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>>> Si ha recibido este correo por error, le informo de que puede 
>>>> contener información confidencial y privada y que está prohibido su 
>>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>>> Gracias.
>>>> If you have received this e-mail in error, please note that it may 
>>>> contain confidential and private information, therefore, the use of 
>>>> this information is strictly forbidden. Please inform the sender of 
>>>> the error and delete the information received. Thank you.
>>>>
>>>
>>
>> -- 
>>
>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>
>> 	Zbigniew Reszela
>> Controls Section - Computing Division
>>
>> ALBA SYNCHROTRON LIGHT SOURCE
>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>> (+34) 93 592 4407
>> www.albasynchrotron.es| zre...@ce...
>>
>> **Please, do not print this e-mail unless it is absolutely necessary.
>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>> informació confidencial i privada i que està prohibit el seu ús. Us 
>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>> Si ha recibido este correo por error, le informo de que puede 
>> contener información confidencial y privada y que está prohibido su 
>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. Gracias.
>> If you have received this e-mail in error, please note that it may 
>> contain confidential and private information, therefore, the use of 
>> this information is strictly forbidden. Please inform the sender of 
>> the error and delete the information received. Thank you.
>>
>

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

Re: [tauruslib-devel] client dependent memory leak

[Roberto B. <rob...@el...>]

Hi Zibi,
in both cases I use taurusform from the command line with the device 
name as argument, then I click the button "Show Device".
In this modality all the attributes are showed (also State and Status).
Currently we're not using events, so Taurus is polling the readings.

Ciao,
     Roberto


On 02/02/2016 10:42, Zbigniew Reszela wrote:
> Hi Roberto,
>
> So you start directly a taurusform with these 18 DevShort and 18 
> DevBoolean attributes, don't you?
> There is nothing else in the form? (no State, Status?).
> Do these attributes emit events? or it is Taurus who polls them?
>
> Good that you have reproduced it with TangoTest. Which attributes do 
> you monitor in this case? All of the attributes of TangoTest?
> I will move to Tango 9 to check if the problem also exist there.
>
> Cheers,
> Zibi
>
> On 02/02/2016 10:00 AM, Roberto Borghes wrote:
>> Hi Zibi,
>> thank you for your analysis. I don't have any graph to show you but I 
>> can confirm that the memory consumption is slow and constant.
>> Obviously the ratio depends on the number of attributes. The device 
>> we're monitoring has 18 DevShort attributes and 18 DevBoolean attributes.
>> Since yesterday, this device gained approximately 30 MB of memory in 
>> 18 hours.
>>
>> But I've another information for you: the TangoTest device seems to 
>> have the same problem. The memory consumption is slower but does exists.
>>
>> Ciao,
>>     Roberto
>>
>>
>> On 02/02/2016 09:26, Zbigniew Reszela wrote:
>>> Good morning!
>>>
>>> I have also observed slight increase in the memory - approx. 2 Mb 
>>> per 14 hours.
>>> I explain you the setup which I used to monitor that.
>>> I simultaneously restarted two Python device servers (each of them 
>>> exporting just one device), and their baseline memory footprint was:
>>>
>>> 24071 sicilia   20   0  178m  30m  16m S    1  1.2   0:03.13 python 
>>> PyAlbaEm.py BL22_DI_EMET-01
>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   0:03.23 python 
>>> PyAlbaEm.py BL22_DI_EMET-02
>>>
>>> Then I have started a taurusform monitoring some models from the 
>>> BL22_DI_EMET-01 instance. The other instance was not monitored by 
>>> any GUI.
>>> These models were (in total 11):
>>> * the device itself
>>> * SCALAR DevDouble (for this one I have started polling every 3 
>>> seconds, with a very demanding absolute change threshold, making it 
>>> emitting events almost every polling period)
>>> * 2 x SCALAR DevString attribute
>>> * SCALAR DevBoolean attribute
>>> * SCALAR DevLong attribute
>>> * 2 x SPECTRUM DevString attribute
>>> * SPECTRUM DevDouble attribute
>>> * State
>>> * Status
>>>
>>> After 14 hours the memory footprint was:
>>>
>>> 24071 sicilia   20   0  172m  32m  16m S    1  1.3   6:56.07 python 
>>> PyAlbaEm.py BL22_DI_EMET-01
>>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   6:18.53 python 
>>> PyAlbaEm.py BL22_DI_EMET-02
>>>
>>> See the attached plot with the memory consumption evolution.
>>>
>>> What is exactly your setup? Do you see similar leak?
>>>
>>> Thanks,
>>> Zibi
>>>
>>>
>>>
>>> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>>>> Hi Roberto!
>>>>
>>>> I'll move this discussion to the taurus-devel mailing list 
>>>> (recently the Sardana and Taurus had separated their SourceForge 
>>>> infrastructure)
>>>>
>>>> Here at Alba we use the following versions of the software:
>>>>
>>>> * server side:
>>>> ** OpenSUSE 11.3 32 bits
>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>> ** PyTango 8.1.4
>>>>
>>>> * client side:
>>>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>>> ** PyTango 8.1.4
>>>> ** we try to follow the develop branch of Taurus (it is at least 3.6.0)
>>>>
>>>> AFAIK we do not observe the memory leaks. But just in case I will 
>>>> leave a taurusform with few attributes and devices running overnight.
>>>> Tomorrow I will get back to you with the results.
>>>>
>>>> Meanwhile could you provide us more information:
>>>> * how many attributes / devices (models) do you have in your form.
>>>> * what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
>>>> DevLong, etc...
>>>> * do the attributes emit events? are they polled by the server?
>>>> * are your models coming from the default TANGO_HOST of the client 
>>>> machine? or you specify the model names with the explicit tango 
>>>> database and port?
>>>> * how do you choose them? specifying the models as the execution 
>>>> parameters? or from the model chooser? or with the drag&drop 
>>>> mechanism? or maybe you programmed taurusform GUI with the 
>>>> hardcoded models?
>>>>
>>>> Cheers,
>>>> Zibi
>>>>
>>>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>>>> Hi everybody,
>>>>> here at Elettra we're facing a mysterious memory leak with some python
>>>>> device servers.
>>>>> The strangefact is that the memory leaks do appear only using taurus
>>>>> clients (like taurusform)
>>>>> , using atkpanel there is no memory increasing...
>>>>>
>>>>> If nobody faced this problem till now probably we've something wrong
>>>>> with our installation:
>>>>>
>>>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>>>
>>>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>>>
>>>>> Any information will be helpful.
>>>>> Thank you in advance,
>>>>>
>>>>>       Roberto
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>>> Monitor end-to-end web transactions and take corrective actions now
>>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>>>> _______________________________________________
>>>>> Sardana-devel mailing list
>>>>> Sar...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>>>
>>>> -- 
>>>>
>>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>>
>>>> 	Zbigniew Reszela
>>>> Controls Section - Computing Division
>>>>
>>>> ALBA SYNCHROTRON LIGHT SOURCE
>>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>>> (+34) 93 592 4407
>>>> www.albasynchrotron.es| zre...@ce...
>>>>
>>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>>> Si ha recibido este correo por error, le informo de que puede 
>>>> contener información confidencial y privada y que está prohibido su 
>>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>>> Gracias.
>>>> If you have received this e-mail in error, please note that it may 
>>>> contain confidential and private information, therefore, the use of 
>>>> this information is strictly forbidden. Please inform the sender of 
>>>> the error and delete the information received. Thank you.
>>>>
>>>
>>> -- 
>>>
>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>
>>> 	Zbigniew Reszela
>>> Controls Section - Computing Division
>>>
>>> ALBA SYNCHROTRON LIGHT SOURCE
>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>> (+34) 93 592 4407
>>> www.albasynchrotron.es| zre...@ce...
>>>
>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>> Si ha recibido este correo por error, le informo de que puede 
>>> contener información confidencial y privada y que está prohibido su 
>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>> Gracias.
>>> If you have received this e-mail in error, please note that it may 
>>> contain confidential and private information, therefore, the use of 
>>> this information is strictly forbidden. Please inform the sender of 
>>> the error and delete the information received. Thank you.
>>>
>>
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>

Re: [tauruslib-devel] client dependent memory leak

[Zbigniew R. <zre...@ce...>]

Hi Roberto,

So you start directly a taurusform with these 18 DevShort and 18 
DevBoolean attributes, don't you?
There is nothing else in the form? (no State, Status?).
Do these attributes emit events? or it is Taurus who polls them?

Good that you have reproduced it with TangoTest. Which attributes do you 
monitor in this case? All of the attributes of TangoTest?
I will move to Tango 9 to check if the problem also exist there.

Cheers,
Zibi

On 02/02/2016 10:00 AM, Roberto Borghes wrote:
> Hi Zibi,
> thank you for your analysis. I don't have any graph to show you but I 
> can confirm that the memory consumption is slow and constant.
> Obviously the ratio depends on the number of attributes. The device 
> we're monitoring has 18 DevShort attributes and 18 DevBoolean attributes.
> Since yesterday, this device gained approximately 30 MB of memory in 
> 18 hours.
>
> But I've another information for you: the TangoTest device seems to 
> have the same problem. The memory consumption is slower but does exists.
>
> Ciao,
>     Roberto
>
>
> On 02/02/2016 09:26, Zbigniew Reszela wrote:
>> Good morning!
>>
>> I have also observed slight increase in the memory - approx. 2 Mb per 
>> 14 hours.
>> I explain you the setup which I used to monitor that.
>> I simultaneously restarted two Python device servers (each of them 
>> exporting just one device), and their baseline memory footprint was:
>>
>> 24071 sicilia   20   0  178m  30m  16m S    1  1.2   0:03.13 python 
>> PyAlbaEm.py BL22_DI_EMET-01
>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   0:03.23 python 
>> PyAlbaEm.py BL22_DI_EMET-02
>>
>> Then I have started a taurusform monitoring some models from the 
>> BL22_DI_EMET-01 instance. The other instance was not monitored by any 
>> GUI.
>> These models were (in total 11):
>> * the device itself
>> * SCALAR DevDouble (for this one I have started polling every 3 
>> seconds, with a very demanding absolute change threshold, making it 
>> emitting events almost every polling period)
>> * 2 x SCALAR DevString attribute
>> * SCALAR DevBoolean attribute
>> * SCALAR DevLong attribute
>> * 2 x SPECTRUM DevString attribute
>> * SPECTRUM DevDouble attribute
>> * State
>> * Status
>>
>> After 14 hours the memory footprint was:
>>
>> 24071 sicilia   20   0  172m  32m  16m S    1  1.3   6:56.07 python 
>> PyAlbaEm.py BL22_DI_EMET-01
>> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   6:18.53 python 
>> PyAlbaEm.py BL22_DI_EMET-02
>>
>> See the attached plot with the memory consumption evolution.
>>
>> What is exactly your setup? Do you see similar leak?
>>
>> Thanks,
>> Zibi
>>
>>
>>
>> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>>> Hi Roberto!
>>>
>>> I'll move this discussion to the taurus-devel mailing list (recently 
>>> the Sardana and Taurus had separated their SourceForge infrastructure)
>>>
>>> Here at Alba we use the following versions of the software:
>>>
>>> * server side:
>>> ** OpenSUSE 11.3 32 bits
>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>> ** PyTango 8.1.4
>>>
>>> * client side:
>>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>>> ** Tango 8.1.2.c + 4 patches from the Tango website
>>> ** PyTango 8.1.4
>>> ** we try to follow the develop branch of Taurus (it is at least 3.6.0)
>>>
>>> AFAIK we do not observe the memory leaks. But just in case I will 
>>> leave a taurusform with few attributes and devices running overnight.
>>> Tomorrow I will get back to you with the results.
>>>
>>> Meanwhile could you provide us more information:
>>> * how many attributes / devices (models) do you have in your form.
>>> * what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
>>> DevLong, etc...
>>> * do the attributes emit events? are they polled by the server?
>>> * are your models coming from the default TANGO_HOST of the client 
>>> machine? or you specify the model names with the explicit tango 
>>> database and port?
>>> * how do you choose them? specifying the models as the execution 
>>> parameters? or from the model chooser? or with the drag&drop 
>>> mechanism? or maybe you programmed taurusform GUI with the hardcoded 
>>> models?
>>>
>>> Cheers,
>>> Zibi
>>>
>>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>>> Hi everybody,
>>>> here at Elettra we're facing a mysterious memory leak with some python
>>>> device servers.
>>>> The strangefact is that the memory leaks do appear only using taurus
>>>> clients (like taurusform)
>>>> , using atkpanel there is no memory increasing...
>>>>
>>>> If nobody faced this problem till now probably we've something wrong
>>>> with our installation:
>>>>
>>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>>
>>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>>
>>>> Any information will be helpful.
>>>> Thank you in advance,
>>>>
>>>>       Roberto
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>> Monitor end-to-end web transactions and take corrective actions now
>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>>> _______________________________________________
>>>> Sardana-devel mailing list
>>>> Sar...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>>
>>> -- 
>>>
>>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>>
>>> 	Zbigniew Reszela
>>> Controls Section - Computing Division
>>>
>>> ALBA SYNCHROTRON LIGHT SOURCE
>>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>>> (+34) 93 592 4407
>>> www.albasynchrotron.es| zre...@ce...
>>>
>>> **Please, do not print this e-mail unless it is absolutely necessary.
>>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>>> informació confidencial i privada i que està prohibit el seu ús. Us 
>>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>>> Si ha recibido este correo por error, le informo de que puede 
>>> contener información confidencial y privada y que está prohibido su 
>>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. 
>>> Gracias.
>>> If you have received this e-mail in error, please note that it may 
>>> contain confidential and private information, therefore, the use of 
>>> this information is strictly forbidden. Please inform the sender of 
>>> the error and delete the information received. Thank you.
>>>
>>
>> -- 
>>
>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>
>> 	Zbigniew Reszela
>> Controls Section - Computing Division
>>
>> ALBA SYNCHROTRON LIGHT SOURCE
>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>> (+34) 93 592 4407
>> www.albasynchrotron.es| zre...@ce...
>>
>> **Please, do not print this e-mail unless it is absolutely necessary.
>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>> informació confidencial i privada i que està prohibit el seu ús. Us 
>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>> Si ha recibido este correo por error, le informo de que puede 
>> contener información confidencial y privada y que está prohibido su 
>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. Gracias.
>> If you have received this e-mail in error, please note that it may 
>> contain confidential and private information, therefore, the use of 
>> this information is strictly forbidden. Please inform the sender of 
>> the error and delete the information received. Thank you.
>>
>

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

Re: [tauruslib-devel] client dependent memory leak

[Roberto B. <rob...@el...>]

Hi Zibi,
thank you for your analysis. I don't have any graph to show you but I 
can confirm that the memory consumption is slow and constant.
Obviously the ratio depends on the number of attributes. The device 
we're monitoring has 18 DevShort attributes and 18 DevBoolean attributes.
Since yesterday, this device gained approximately 30 MB of memory in 18 
hours.

But I've another information for you: the TangoTest device seems to have 
the same problem. The memory consumption is slower but does exists.

Ciao,
     Roberto


On 02/02/2016 09:26, Zbigniew Reszela wrote:
> Good morning!
>
> I have also observed slight increase in the memory - approx. 2 Mb per 
> 14 hours.
> I explain you the setup which I used to monitor that.
> I simultaneously restarted two Python device servers (each of them 
> exporting just one device), and their baseline memory footprint was:
>
> 24071 sicilia   20   0  178m  30m  16m S    1  1.2   0:03.13 python 
> PyAlbaEm.py BL22_DI_EMET-01
> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   0:03.23 python 
> PyAlbaEm.py BL22_DI_EMET-02
>
> Then I have started a taurusform monitoring some models from the 
> BL22_DI_EMET-01 instance. The other instance was not monitored by any GUI.
> These models were (in total 11):
> * the device itself
> * SCALAR DevDouble (for this one I have started polling every 3 
> seconds, with a very demanding absolute change threshold, making it 
> emitting events almost every polling period)
> * 2 x SCALAR DevString attribute
> * SCALAR DevBoolean attribute
> * SCALAR DevLong attribute
> * 2 x SPECTRUM DevString attribute
> * SPECTRUM DevDouble attribute
> * State
> * Status
>
> After 14 hours the memory footprint was:
>
> 24071 sicilia   20   0  172m  32m  16m S    1  1.3   6:56.07 python 
> PyAlbaEm.py BL22_DI_EMET-01
> 24373 sicilia   20   0  170m  30m  16m S    1  1.2   6:18.53 python 
> PyAlbaEm.py BL22_DI_EMET-02
>
> See the attached plot with the memory consumption evolution.
>
> What is exactly your setup? Do you see similar leak?
>
> Thanks,
> Zibi
>
>
>
> On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
>> Hi Roberto!
>>
>> I'll move this discussion to the taurus-devel mailing list (recently 
>> the Sardana and Taurus had separated their SourceForge infrastructure)
>>
>> Here at Alba we use the following versions of the software:
>>
>> * server side:
>> ** OpenSUSE 11.3 32 bits
>> ** Tango 8.1.2.c + 4 patches from the Tango website
>> ** PyTango 8.1.4
>>
>> * client side:
>> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
>> ** Tango 8.1.2.c + 4 patches from the Tango website
>> ** PyTango 8.1.4
>> ** we try to follow the develop branch of Taurus (it is at least 3.6.0)
>>
>> AFAIK we do not observe the memory leaks. But just in case I will 
>> leave a taurusform with few attributes and devices running overnight.
>> Tomorrow I will get back to you with the results.
>>
>> Meanwhile could you provide us more information:
>> * how many attributes / devices (models) do you have in your form.
>> * what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
>> DevLong, etc...
>> * do the attributes emit events? are they polled by the server?
>> * are your models coming from the default TANGO_HOST of the client 
>> machine? or you specify the model names with the explicit tango 
>> database and port?
>> * how do you choose them? specifying the models as the execution 
>> parameters? or from the model chooser? or with the drag&drop 
>> mechanism? or maybe you programmed taurusform GUI with the hardcoded 
>> models?
>>
>> Cheers,
>> Zibi
>>
>> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>>> Hi everybody,
>>> here at Elettra we're facing a mysterious memory leak with some python
>>> device servers.
>>> The strangefact is that the memory leaks do appear only using taurus
>>> clients (like taurusform)
>>> , using atkpanel there is no memory increasing...
>>>
>>> If nobody faced this problem till now probably we've something wrong
>>> with our installation:
>>>
>>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>>
>>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>>
>>> Any information will be helpful.
>>> Thank you in advance,
>>>
>>>       Roberto
>>>
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>> _______________________________________________
>>> Sardana-devel mailing list
>>> Sar...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>>
>> -- 
>>
>> ALBA Synchrotron <http://www.albasynchrotron.es>
>>
>> 	Zbigniew Reszela
>> Controls Section - Computing Division
>>
>> ALBA SYNCHROTRON LIGHT SOURCE
>> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
>> Spain <http://www.albasynchrotron.es/AboutUs/Access>
>> (+34) 93 592 4407
>> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
>> zre...@ce... <mailto:zre...@ce...>
>>
>> **Please, do not print this e-mail unless it is absolutely necessary.
>> **Si heu rebut aquest correu per error, us informo que pot contenir 
>> informació confidencial i privada i que està prohibit el seu ús. Us 
>> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
>> Si ha recibido este correo por error, le informo de que puede 
>> contener información confidencial y privada y que está prohibido su 
>> uso. Le agradeceré que lo comunique a su remitente y lo elimine. Gracias.
>> If you have received this e-mail in error, please note that it may 
>> contain confidential and private information, therefore, the use of 
>> this information is strictly forbidden. Please inform the sender of 
>> the error and delete the information received. Thank you.
>>
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>

Re: [tauruslib-devel] client dependent memory leak

[Zbigniew R. <zre...@ce...>]

Good morning!

I have also observed slight increase in the memory - approx. 2 Mb per 14 
hours.
I explain you the setup which I used to monitor that.
I simultaneously restarted two Python device servers (each of them 
exporting just one device), and their baseline memory footprint was:

24071 sicilia   20   0  178m  30m  16m S    1  1.2   0:03.13 python 
PyAlbaEm.py BL22_DI_EMET-01
24373 sicilia   20   0  170m  30m  16m S    1  1.2   0:03.23 python 
PyAlbaEm.py BL22_DI_EMET-02

Then I have started a taurusform monitoring some models from the 
BL22_DI_EMET-01 instance. The other instance was not monitored by any GUI.
These models were (in total 11):
* the device itself
* SCALAR DevDouble (for this one I have started polling every 3 seconds, 
with a very demanding absolute change threshold, making it emitting 
events almost every polling period)
* 2 x SCALAR DevString attribute
* SCALAR DevBoolean attribute
* SCALAR DevLong attribute
* 2 x SPECTRUM DevString attribute
* SPECTRUM DevDouble attribute
* State
* Status

After 14 hours the memory footprint was:

24071 sicilia   20   0  172m  32m  16m S    1  1.3   6:56.07 python 
PyAlbaEm.py BL22_DI_EMET-01
24373 sicilia   20   0  170m  30m  16m S    1  1.2   6:18.53 python 
PyAlbaEm.py BL22_DI_EMET-02

See the attached plot with the memory consumption evolution.

What is exactly your setup? Do you see similar leak?

Thanks,
Zibi



On 02/01/2016 04:49 PM, Zbigniew Reszela wrote:
> Hi Roberto!
>
> I'll move this discussion to the taurus-devel mailing list (recently 
> the Sardana and Taurus had separated their SourceForge infrastructure)
>
> Here at Alba we use the following versions of the software:
>
> * server side:
> ** OpenSUSE 11.3 32 bits
> ** Tango 8.1.2.c + 4 patches from the Tango website
> ** PyTango 8.1.4
>
> * client side:
> ** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
> ** Tango 8.1.2.c + 4 patches from the Tango website
> ** PyTango 8.1.4
> ** we try to follow the develop branch of Taurus (it is at least 3.6.0)
>
> AFAIK we do not observe the memory leaks. But just in case I will 
> leave a taurusform with few attributes and devices running overnight.
> Tomorrow I will get back to you with the results.
>
> Meanwhile could you provide us more information:
> * how many attributes / devices (models) do you have in your form.
> * what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
> DevLong, etc...
> * do the attributes emit events? are they polled by the server?
> * are your models coming from the default TANGO_HOST of the client 
> machine? or you specify the model names with the explicit tango 
> database and port?
> * how do you choose them? specifying the models as the execution 
> parameters? or from the model chooser? or with the drag&drop 
> mechanism? or maybe you programmed taurusform GUI with the hardcoded 
> models?
>
> Cheers,
> Zibi
>
> On 01/29/2016 05:49 PM, Roberto Borghes wrote:
>> Hi everybody,
>> here at Elettra we're facing a mysterious memory leak with some python
>> device servers.
>> The strangefact is that the memory leaks do appear only using taurus
>> clients (like taurusform)
>> , using atkpanel there is no memory increasing...
>>
>> If nobody faced this problem till now probably we've something wrong
>> with our installation:
>>
>>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>>
>>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>>
>> Any information will be helpful.
>> Thank you in advance,
>>
>>       Roberto
>>
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>> _______________________________________________
>> Sardana-devel mailing list
>> Sar...@li...
>> https://lists.sourceforge.net/lists/listinfo/sardana-devel
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

[tauruslib-devel] client dependent memory leak

[Zbigniew R. <zre...@ce...>]

Hi Roberto!

I'll move this discussion to the taurus-devel mailing list (recently the 
Sardana and Taurus had separated their SourceForge infrastructure)

Here at Alba we use the following versions of the software:

* server side:
** OpenSUSE 11.3 32 bits
** Tango 8.1.2.c + 4 patches from the Tango website
** PyTango 8.1.4

* client side:
** OpenSUSE 11.3 64 bits or OpenSUSE 12.1 64 bits
** Tango 8.1.2.c + 4 patches from the Tango website
** PyTango 8.1.4
** we try to follow the develop branch of Taurus (it is at least 3.6.0)

AFAIK we do not observe the memory leaks. But just in case I will leave 
a taurusform with few attributes and devices running overnight.
Tomorrow I will get back to you with the results.

Meanwhile could you provide us more information:
* how many attributes / devices (models) do you have in your form.
* what type of attributes do you use? SPECTRUM, SCALAR, DevFloat, 
DevLong, etc...
* do the attributes emit events? are they polled by the server?
* are your models coming from the default TANGO_HOST of the client 
machine? or you specify the model names with the explicit tango database 
and port?
* how do you choose them? specifying the models as the execution 
parameters? or from the model chooser? or with the drag&drop mechanism? 
or maybe you programmed taurusform GUI with the hardcoded models?

Cheers,
Zibi

On 01/29/2016 05:49 PM, Roberto Borghes wrote:
> Hi everybody,
> here at Elettra we're facing a mysterious memory leak with some python
> device servers.
> The strangefact is that the memory leaks do appear only using taurus
> clients (like taurusform)
> , using atkpanel there is no memory increasing...
>
> If nobody faced this problem till now probably we've something wrong
> with our installation:
>
>       - server side: Centos6 x64, Tango 8.1.2.c, PyTango 8.0.2
>
>       - client side: Centos7 x64, Tango 8.1.2.c, PyTango 8.1.6, taurus 3.6.0
>
> Any information will be helpful.
> Thank you in advance,
>
>       Roberto
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Sardana-devel mailing list
> Sar...@li...
> https://lists.sourceforge.net/lists/listinfo/sardana-devel

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

Re: [tauruslib-devel] [PATCH] Fix bug-251: avoid exception on empty model list selection

[Carlos P. <cpa...@ce...>]

Applied to develop

On Wed 20 January 2016 12:51:10 cpa...@ce... wrote:
> From: cpascual <cpa...@ce...>
> 
> Handle the case of applying an empty model list with the model
> selection tool in extra_guiqwt.
> ---
>  lib/taurus/qt/qtgui/extra_guiqwt/tools.py | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
> b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py index 5ecd2bd..0c55967
> 100644
> --- a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
> +++ b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
> @@ -100,7 +100,10 @@ class TaurusModelChooserTool(CommandTool):
>          models, ok = TaurusModelChooser.modelChooserDlg(parent=plot,
> selectables=[TaurusElementType.Attribute],
> singleModel=self.singleModel) if ok:
>              if self.singleModel:
> -                self.manager.setModel(models[0])
> +                if models:
> +                    self.manager.setModel(models[0])
> +                else:
> +                    self.manager.setModel('')
>              else:
>                  self.manager.setModel(models)

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] [PATCH] Fix bug-111: store geometry in taurusform config

[Carlos P. <cpa...@ce...>]

Applied to develop

On Tue 19 January 2016 16:07:53 cpa...@ce... wrote:
> From: cpascual <cpa...@ce...>
> 
> When launching taurusform as an standalone application, store the
> window geometry in the config dict/file so that it is restored when
> loading the stored settings.
> ---
>  lib/taurus/qt/qtgui/panel/taurusform.py | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/lib/taurus/qt/qtgui/panel/taurusform.py
> b/lib/taurus/qt/qtgui/panel/taurusform.py index 99c2ec5..4b38c58
> 100644
> --- a/lib/taurus/qt/qtgui/panel/taurusform.py
> +++ b/lib/taurus/qt/qtgui/panel/taurusform.py
> @@ -947,6 +947,10 @@ def taurusFormMain():
>      dialog.setModifiableByUser(True)
>      dialog.setModelInConfig(True)
>      dialog.setWindowTitle(options.window_name)
> +
> +    # Make sure the window size and position are restored
> +    dialog.registerConfigProperty(dialog.saveGeometry,
> dialog.restoreGeometry, +                                 
> 'MainWindowGeometry')
> 
>      from taurus.qt.qtgui.resource import getThemeIcon
>      quitApplicationAction = 
> Qt.QAction(getThemeIcon("process-stop"),'Close Form', dialog)

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] [PATCH] Fix bug-258: handle non-increasing x values

[<cpa...@ce...>]

From: cpascual <cpa...@ce...>

Detect non-increasing x values and ignore such events. They happen when
using a time mode and clicking on the TaurusModel tool.
---
 lib/taurus/qt/qtgui/extra_guiqwt/image.py | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/image.py b/lib/taurus/qt/qtgui/extra_guiqwt/image.py
index 087f623..4aedefa 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/image.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/image.py
@@ -256,7 +256,6 @@ class TaurusTrend2DItem(XYImageItem, TaurusBaseComponent):
         if evt_value is None or getattr(evt_value,'value', None) is None:
             self.debug('Ignoring event from %s'%repr(evt_src))
             return
-
         plot = self.plot()
         if plot is None:
             return
@@ -278,28 +277,33 @@ class TaurusTrend2DItem(XYImageItem, TaurusBaseComponent):
         
         #update x values
         if self.stackMode == 'datetime':
+            x = evt_value.time.totime()
             if self.__timeOffset is None:
-                self.__timeOffset = evt_value.time.totime()
+                self.__timeOffset = x
                 plot.set_axis_title('bottom', 'Time')
                 plot.set_axis_unit('bottom', '')
-            self._xBuffer.append(evt_value.time.totime())
         
         elif self.stackMode == 'deltatime':
             try:
-                self._xBuffer.append(evt_value.time.totime() - self.__timeOffset)
+                x = evt_value.time.totime() - self.__timeOffset
             except TypeError: #this will happen if self.__timeOffset has not been initialized
                 self.__timeOffset = evt_value.time.totime()
-                self._xBuffer.append(0)
+                x = 0
                 plot.set_axis_title('bottom', 'Time since %s'%evt_value.time.isoformat())
                 plot.set_axis_unit('bottom', '')
         else:  
             try:
                 step = 1 # +numpy.random.randint(0,4) #for debugging we can put a variable step
-                self._xBuffer.append(self._xBuffer[-1]+step) 
+                x = self._xBuffer[-1]+step
             except IndexError: #this will happen when the x buffer is empty
-                self._xBuffer.append(0) 
+                x = 0
                 plot.set_axis_title('bottom', 'Event #')
                 plot.set_axis_unit('bottom', '')
+
+        if len(self._xBuffer) and x <= self._xBuffer[-1]:
+            self.info('Ignoring event (non-increasing x value)')
+            return
+        self._xBuffer.append(x)
         
         #update z
         self._zBuffer.append(evt_value.value)
-- 
2.6.4

Re: [tauruslib-devel] [PATCH] Fix bug-142: Avoid bad stretch when using extrawidget in forms

[Zbigniew R. <zre...@ce...>]

Hi Carlos,

Thanks for the patch. I have applied it to the develop branch.

Cheers,
Zibi

On 01/20/2016 11:33 AM, cpa...@ce... wrote:
> From: cpascual <cpa...@ce...>
>
> When using a TaurusValue customized with an extra widget, the grid
> layout behaves in an unexpected way regarding to its rows/columns
> stretch (see http://sf.net/p/tauruslib/tickets/142/#f4e4/9e68).
> Prevent this by inserting a spacer in the extrawidget column if no
> extrawidget is used.
> ---
>   lib/taurus/qt/qtgui/panel/taurusvalue.py | 16 +++++++++++-----
>   1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/lib/taurus/qt/qtgui/panel/taurusvalue.py b/lib/taurus/qt/qtgui/panel/taurusvalue.py
> index 543ba0e..dff58d2 100644
> --- a/lib/taurus/qt/qtgui/panel/taurusvalue.py
> +++ b/lib/taurus/qt/qtgui/panel/taurusvalue.py
> @@ -833,11 +833,17 @@ class TaurusValue(Qt.QWidget, TaurusBaseWidget):
>                                                1, 1, -1, alignment)
>       
>       def addExtraWidgetToLayout(self):
> -        if self._extraWidget is not None and self.parent() is not None:
> -            alignment = getattr(self._extraWidget, 'layoutAlignment',
> -                                Qt.Qt.AlignmentFlag(0))
> -            self.parent().layout().addWidget(self._extraWidget, self._row,
> -                                             5, 1, 1, alignment)
> +        parent = self.parent()
> +        if parent is not None:
> +            if self._extraWidget is None:
> +                # Adding this spacer is some voodoo magic to avoid bug #142
> +                # See: http://sf.net/p/tauruslib/tickets/142/
> +                parent.layout().addItem(Qt.QSpacerItem(0, 0), self._row, 5)
> +            else:
> +                alignment = getattr(self._extraWidget, 'layoutAlignment',
> +                                    Qt.Qt.AlignmentFlag(0))
> +                parent.layout().addWidget(self._extraWidget, self._row,
> +                                            5, 1, 1, alignment)
>   
>       @Qt.pyqtSignature("parentModelChanged(const QString &)")
>       def parentModelChanged(self, parentmodel_name):

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

Re: [tauruslib-devel] [PATCH] Fix bug#172 TaurusPropTable.setModel does nothing

[Carlos P. <cpa...@ce...>]

I did a complete rework based on cfalcon's work and pushed it to 
taurus4.


On Wed 2 December 2015 09:57:35 Carlos Pascual wrote:
> Hi, the changes seem ok to me, but the implementation has one problem:
> 
> It assumesthat the "normal_name" returned by the validator is
> equivalent to the device name (and it psses it to setTable). But this
> is not always the case. The normal name may contain the DB name in it
> if it is not the default one.
> 
> For example, in my system I have constrols02:10000 as my default DB,
> and the device cpascual/pysignalsimulator/1 is exported only in
> controls01 (not in controls02) then:
> 
> This fails:
> 
> ~~~~
> python taurusdevicepropertytable.py \
> tango://controls01:10000/cpascual/pysignalsimulator/1
> ~~~~
> 
> This also fails:
> 
> ~~~~
> devenv python taurusdevicepropertytable.py \
> --tango-host=controls01:10000 cpascual/pysignalsimulator/1
> ~~~~
> 
> And this works:
> 
> ~~~~
> TANGO_HOST=controls01:10000 python taurusdevicepropertytable.py \
> cpascual/pysignalsimulator/1
> ~~~~
> 
> Apart from this, simply running `python taurusdevicepropertytable.py` 
> I get this exception (the widget seems to work anyway):
> 
> ~~~~
> Traceback (most recent call last):
>   File
> "/home/cpascual/src/taurus/lib/taurus/qt/qtgui/base/taurusbase.py",
> line 341, in filterEvent
>     self.handleEvent(*evt)
>   File
> "/home/cpascual/src/taurus/lib/taurus/qt/qtgui/base/taurusbase.py",
> line 1257, in handleEvent
>     self._setText(text)
> TypeError: setText() takes exactly 4 arguments (2 given)
> 
> ~~~~
> 
> Finally,
> it would be nice if you test the implementation on taurus4-preview as
> well (I haven't yet)
> 
> Can you please resubmit addressing this problems?
> 
> Note: if it is too much work, I think the current implementation is
> more or less ok and can be applied with just a TODO notifying of the
> currently known limitations
> 
> Cheers,
> 
> Carlos
> 
> On Wed 11 November 2015 11:56:56 cfalcon wrote:
> > setModel of taurus.qt.qtgui.table.TaurusPropTable does not work.
> > 
> > TaurusPropTable uses the inherit setModel method of TaurusBaseWidget
> > class that  does not cover the funcionality of this widget.
> > 
> > Implement a setModel method acording the specifications provided
> > by S.Rubio.
> > ---
> > 
> >  .../qt/qtgui/table/taurusdevicepropertytable.py    | 57
> > 
> > ++++++++++++++-------- 1 file changed, 38 insertions(+), 19
> > deletions(-)
> > 
> > diff --git a/lib/taurus/qt/qtgui/table/taurusdevicepropertytable.py
> > b/lib/taurus/qt/qtgui/table/taurusdevicepropertytable.py index
> > 9901ec3..cc9722e 100644
> > --- a/lib/taurus/qt/qtgui/table/taurusdevicepropertytable.py
> > +++ b/lib/taurus/qt/qtgui/table/taurusdevicepropertytable.py
> > @@ -31,14 +31,15 @@ __all__ = ["TaurusPropTable"]
> > 
> >  from taurus.external.qt import Qt, QtCore, QtGui
> >  from taurus.qt.qtgui.base import TaurusBaseWidget
> > 
> > -import taurus.core
> > -import PyTango
> > +import taurus
> > +from taurus.core.taurusdevice import TaurusDevice
> > 
> >  class TaurusPropTable(QtGui.QTableWidget, TaurusBaseWidget):
> >      '''
> >      This widget will show a list of properties of device and the
> >      list
> > 
> > of values. @todo add a frame for Add, Delete and Refresh buttons!
> > 
> >      '''
> > 
> > +    # TODO This widget is Tango-centric
> > 
> >      __pyqtSignals__ = ("modelChanged(const QString &)",)
> > 
> >      def __init__(self, parent=None, designMode = False):
> > @@ -59,6 +60,14 @@ class TaurusPropTable(QtGui.QTableWidget,
> > TaurusBaseWidget):
> > #-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> > ~
> > -~-~-~- # TaurusBaseWidget over writing methods
> > 
> > #-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> > ~
> > -~-~-~- +    def setModel(self, model):
> > +        name_validator = TaurusDevice.getNameValidator()
> > +        TaurusBaseWidget.setModel(self, model)
> > +        try:
> > +            _, normal_name, _ = name_validator.getNames(model)
> > +            self.setTable(normal_name)
> > +        except ValueError:
> > +            self.debug('Wrong model!! %s' %(model))
> > 
> >      def sizeHint(self):
> >          return QtGui.QTableWidget.sizeHint(self)
> > 
> > @@ -67,7 +76,7 @@ class TaurusPropTable(QtGui.QTableWidget,
> > TaurusBaseWidget): return QtGui.QTableWidget.minimumSizeHint(self)
> > 
> >      def getModelClass(self):
> > -        return taurus.core.taurusdatabase.TaurusDatabase
> > +        return TaurusDevice
> > 
> >      @classmethod
> > 
> >      def getQtDesignerPluginInfo(cls):
> > @@ -82,7 +91,7 @@ class TaurusPropTable(QtGui.QTableWidget,
> > TaurusBaseWidget):
> > #-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> > ~
> > -~-~-~-
> > 
> >      model = QtCore.pyqtProperty("QString",
> >      TaurusBaseWidget.getModel,
> > 
> > -                                TaurusBaseWidget.setModel,
> > +                                setModel,
> > 
> >                                  TaurusBaseWidget.resetModel)
> >      
> >      useParentModel = QtCore.pyqtProperty("bool",
> > 
> > @@ -95,30 +104,37 @@ class TaurusPropTable(QtGui.QTableWidget,
> > TaurusBaseWidget):
> > #-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> > ~
> > -~-~-~-
> > 
> >      @QtCore.pyqtSignature("setTable(QString)")
> > 
> > -    def setTable(self,dev_name):
> > 
> > +    def setTable(self, dev_name):
> >          '''
> >          This method is used to connect TaurusPropTable widget with
> > 
> > TaurusClassTable widget This method fill the table with the names of
> > properties and values for the device selected in the
> > TaurusClassTable
> > '''
> > -
> > QtCore.QObject.disconnect(self,QtCore.SIGNAL("cellChanged(int,int)")
> > ,
> > self.valueChanged) -        self.db = PyTango.Database()
> > +        QtCore.QObject.disconnect(self,
> > QtCore.SIGNAL("cellChanged(int, int)"), +
> > 
> >      self.valueChanged)
> > 
> > +        self.db = taurus.Database()
> > 
> >          dev_name = str(dev_name)
> > 
> > -        self.list_prop =
> > list(self.db.get_device_property_list(dev_name,'*')) +
> > self.list_prop = list(self.db.get_device_property_list(dev_name,
> > '*')) self.setRowCount(len(self.list_prop))
> > 
> >          for i in range(0,len(self.list_prop)):
> >              elem = self.list_prop[i]
> >              self.setText(elem,i,0)
> > 
> > -
> > self.dictionary=self.db.get_device_property(dev_name,self.list_prop)
> > -            self.debug('Getting %s properties: %s ->
> > %s'%(dev_name,self.list_prop,self.dictionary)) +
> > self.dictionary= self.db.get_device_property(dev_name, +
> > 
> >                                            self.list_prop) +
> >   
> >   self.debug('Getting %s properties: %s -> %s' %(dev_name, +
> >   
> >                                                  self.list_prop, +
> > 
> > self.dictionary)) value=self.dictionary[elem]
> > -            self.debug('TaurusPropsTable: property %s is type
> > %s'%(elem,type(value))) -            USE_TABLES=False
> > +            self.debug('TaurusPropsTable: property %s is type %s'
> > %(elem, +
> > 
> >        type(value)) +                       )
> > 
> > +            USE_TABLES= False
> > 
> >              if USE_TABLES: self.setPropertyValue(value,i,1)
> >              
> >              else:
> >                  if not isinstance(value,str): #not something like
> >                  an
> > 
> > string #if isinstance(value,list):#type(value) is list: heigh1 =
> > len(value)
> > -                    value = '\n'.join(str(v) for v in value) #
> > adding new lines in between elements in the list +                 
> >   # adding new lines in between elements in the list +
> > value = '\n'.join(str(v) for v in value)
> > self.setText(str(value),i,1)
> > 
> >          self.updateStyle()
> > 
> > @@ -372,12 +388,15 @@ class Delegate(QtGui.QItemDelegate):
> >          return size
> >  
> >  if __name__ == '__main__':
> > -    import sys,os
> > -    app = QtGui.QApplication([])
> > +    import sys
> > +    from  taurus.qt.qtgui.application import TaurusApplication
> > +    app = TaurusApplication(app_name="TaurusDevice property table")
> > 
> >      widget = TaurusPropTable()
> > 
> > -    args = sys.argv[1:]
> > -    if not args: args =
> > ['tango/admin/%s'%(os.environ['TANGO_HOST'].split(':')[0])] -
> > widget.setTable(sys.args)
> > +    args = sys.argv
> > +    if len(args) == 1:
> > +        model = 'sys/tg_test/1'
> > +    else:
> > +        model = str(args[1])
> > +    widget.setModel(model)
> > 
> >      widget.show()
> >      app.exec_()
> > 
> > -

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] [PATCH] Fix bug-256: make models store a strong ref to parent

[Carlos P. <cpa...@ce...>]

Forget this patch. If this approach is to be followed, some more things 
need to be done:
-clean the _parentObj ref in TaurusModel.cleanUp
-remove the TaurusAttribute.__parentDevice member (created in 
constructor) since it is unneeded

(also, see discussion in https://sf.net/p/tauruslib/tickets/256/#02a4 )

On Wed 27 January 2016 16:36:30 cpa...@ce... wrote:
> From: cpascual <cpa...@ce...>
> 
> TaurusModel stores a weak ref to its parent. If the parent is not
> referenced elsewhere, the getParentObj API does not work as expected.
> Fix by making TaurusModel store a strong ref to parent instead of a
> weak one.
> ---
>  lib/taurus/core/taurusmodel.py | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/lib/taurus/core/taurusmodel.py
> b/lib/taurus/core/taurusmodel.py index 4f11b9d..e5cbc4f 100644
> --- a/lib/taurus/core/taurusmodel.py
> +++ b/lib/taurus/core/taurusmodel.py
> @@ -58,10 +58,7 @@ class TaurusModel(Logger):
>                  serializationMode = s_obj.getSerializationMode()
>          self._serialization_mode = serializationMode
> 
> -        try:
> -            self._parentObj = weakref.ref(parent)
> -        except Exception:
> -            self._parentObj = None
> +        self._parentObj = parent
>          self._listeners = []
> 
>      def __str__name__(self, name):
> @@ -121,8 +118,7 @@ class TaurusModel(Logger):
>     
> #-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
> -~-~-~-
> 
>      def getParentObj(self):
> -        if self._parentObj is None: return None
> -        return self._parentObj()
> +        return self._parentObj
> 
>      def getChildObj(self,child_name):
>          return None

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+