Tango Archiving - TANGO Controls

# 9 years ago
TCS_GMRT	Hello. I already answered that kind of question in that post: "Mambo was not designed to work with multiple tango hosts at the same time. The coma separator is more likely interpreted to consider that if the first one does'nt answer, try second one." Regards, Hi Rapheal Thanks for your instant reply. I got your point,Mambo is not designed to work with multiple hosts. But one of my project requirement is to archive from devices of different hosts. If not from mambo, how can i achieve this functionality ? Is there any workaround to do so ? Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT

# 9 years ago

Hello.
I already answered that kind of question in that post:
"Mambo was not designed to work with multiple tango hosts at the same time. The coma separator is more likely interpreted to consider that if the first one does'nt answer, try second one."
Regards,

Hi Rapheal

Thanks for your instant reply.
I got your point,Mambo is not designed to work with multiple hosts. But one of my project requirement is to archive from devices of different hosts. If not from mambo, how can i achieve this functionality ? Is there any workaround to do so ?

Thanks and Regards
TCS-GMRT Team

Regards,
TCS_GMRT

# 9 years ago
girardot	Let's just say it is a bit tricky : If you are sure the same device full name won't appear in 2 different tango hosts, then you can register Archivers on each tango host, and configure them the same way, so that they all archive on the same database. But then, you will have to remember which device comes from which tango host, as it is not saved in database. Otherwise, the solution is to have 1 archiving system per tango host, and make a custom mambo script to force the tango host you want to use. (You have to do a custom mambo script only if you want to check your tango hosts/ databases from the same computer) Rg Edited 9 years ago

# 9 years ago

girardot

Let's just say it is a bit tricky :
If you are sure the same device full name won't appear in 2 different tango hosts, then you can register Archivers on each tango host, and configure them the same way, so that they all archive on the same database.
But then, you will have to remember which device comes from which tango host, as it is not saved in database.

Otherwise, the solution is to have 1 archiving system per tango host, and make a custom mambo script to force the tango host you want to use.

(You have to do a custom mambo script only if you want to check your tango hosts/ databases from the same computer)

Edited 9 years ago

# 9 years ago
Andy	Are you sure you are talking about the same concept when you say hosts? GMRT, do you mean different computers but all using the same TANGO_HOST or do you devices with different TANGO_HOST running on different computer hosts? It is not clear in your question. If you mean devices from different TANGO_HOSTS then the new HDB++ archiving system supports this feature. Raphael is the expert for everything concerning HDB so ignore my previous answer! Andy

# 9 years ago

Andy

Are you sure you are talking about the same concept when you say hosts?

GMRT, do you mean different computers but all using the same TANGO_HOST or do you devices with different TANGO_HOST running on different computer hosts? It is not clear in your question.

If you mean devices from different TANGO_HOSTS then the new HDB++ archiving system supports this feature.

Raphael is the expert for everything concerning HDB so ignore my previous answer!

Andy

# 9 years ago
TCS_GMRT	Hi Rapheal My device name won't be same in two different hosts. I have registered the archiver in the multiple tango hosts. There is one archiving system per host also. I didn't get what you mean by configuring the archiver the same way. In host 1 , I have to archive the attributes of host 1 In host 2 , I have to archive the attributes of host 2 In host 3 , I have to archive the attributes of host1, host2 and host3 as well. Also I have found When i archive around 40-50 parameters in HDB, it results in slowing of mambo. I found the below errors when I archive more than 20 parameters 03-09-15 19:43:43.289 - ERROR: Message : [1] : Reason : org.omg.CORBA.TIMEOUT: client timeout reached vmcid: 0x0 minor code: 0 completed: No Severity : ERROR Description : Device (archiving/hdb/hdbarchiver.01_01) timed out (>7000 ms)! Origin : archiving/hdb/hdbarchiver.01_01.class fr.esrf.TangoApi.ConnectionDAODefaultImpl.command_inout) The attributes are archived but the error is coming in the log console of mambo. Please do help. Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT Edited 9 years ago

# 9 years ago

TCS_GMRT

Hi Rapheal

My device name won't be same in two different hosts. I have registered the archiver in the multiple tango hosts. There is one archiving system per host also.
I didn't get what you mean by configuring the archiver the same way.

In host 1 , I have to archive the attributes of host 1
In host 2 , I have to archive the attributes of host 2
In host 3 , I have to archive the attributes of host1, host2 and host3 as well.

Also I have found When i archive around 40-50 parameters in HDB, it results in slowing of mambo.

I found the below errors when I archive more than 20 parameters
03-09-15 19:43:43.289 - ERROR: Message :
[1] :
Reason : org.omg.CORBA.TIMEOUT: client timeout reached vmcid: 0x0 minor code: 0 completed: No
Severity : ERROR
Description : Device (archiving/hdb/hdbarchiver.01_01) timed out (>7000 ms)!
Origin : archiving/hdb/hdbarchiver.01_01.class fr.esrf.TangoApi.ConnectionDAODefaultImpl.command_inout)

The attributes are archived but the error is coming in the log console of mambo.

Please do help.

Thanks and Regards
TCS-GMRT Team

Regards,
TCS_GMRT

Edited 9 years ago

# 9 years ago
TCS_GMRT	Hi Andy/Rapheal Please can u share the link from where i can download HDB++. But does HDB++ supports mysql ? Also where can I found the documents related to HDB++. Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT

# 9 years ago
girardot	TCS_GMRT Hi Rapheal My device name won't be same in two different hosts. I have registered the archiver in the multiple tango hosts. There is one archiving system per host also. I didn't get what you mean by configuring the archiver the same way. I meant you will have to configure them to work with the same database (through the device class properties and the device properties), whatever the tango host. TCS_GMRT In host 1 , I have to archive the attributes of host 1 In host 2 , I have to archive the attributes of host 2 In host 3 , I have to archive the attributes of host1, host2 and host3 as well. Run 1 mambo per tango host, and configure your archiving on each one. You won't have the possibility to configure the archiving of host1, host2 and host3 from host3, unless you use Proxy devices (available in tango-ds), which will reproduce your attributes from host1 and host2 on devices of host3. TCS_GMRT Also I have found When i archive around 40-50 parameters in HDB, it results in slowing of mambo. Thanks and Regards TCS-GMRT Team Yes, there is a limit in what mambo can manage at a time. I suggest splitting archiving configurations that contain too many attributes. Rg Edited 9 years ago

# 9 years ago

girardot

TCS_GMRT
Hi Rapheal

My device name won't be same in two different hosts. I have registered the archiver in the multiple tango hosts. There is one archiving system per host also.
I didn't get what you mean by configuring the archiver the same way.

I meant you will have to configure them to work with the same database (through the device class properties and the device properties), whatever the tango host.

TCS_GMRT
In host 1 , I have to archive the attributes of host 1
In host 2 , I have to archive the attributes of host 2
In host 3 , I have to archive the attributes of host1, host2 and host3 as well.

Run 1 mambo per tango host, and configure your archiving on each one. You won't have the possibility to configure the archiving of host1, host2 and host3 from host3, unless you use Proxy devices (available in tango-ds), which will reproduce your attributes from host1 and host2 on devices of host3.

TCS_GMRT
Also I have found When i archive around 40-50 parameters in HDB, it results in slowing of mambo.

Thanks and Regards
TCS-GMRT Team

Yes, there is a limit in what mambo can manage at a time. I suggest splitting archiving configurations that contain too many attributes.

Edited 9 years ago

# 9 years ago
Andy	TCS_GMRT In host 1 , I have to archive the attributes of host 1 In host 2 , I have to archive the attributes of host 2 In host 3 , I have to archive the attributes of host1, host2 and host3 as well. I don't know why you have multiple TANGO_HOSTs if you only have 3 computers running device servers. I reiterate my question - do you mean computers or TANGO_HOSTs. These are not the same. Can you send us a picture of your control system layout with the TANGO_HOST and computer hosts clearly marked. We have one TANGO_HOST for hundreds of computer hosts and thousands of devices and servers. Andy

# 9 years ago

Andy

TCS_GMRT
In host 1 , I have to archive the attributes of host 1
In host 2 , I have to archive the attributes of host 2
In host 3 , I have to archive the attributes of host1, host2 and host3 as well.

I don't know why you have multiple TANGO_HOSTs if you only have 3 computers running device servers. I reiterate my question - do you mean computers or TANGO_HOSTs. These are not the same. Can you send us a picture of your control system layout with the TANGO_HOST and computer hosts clearly marked.

We have one TANGO_HOST for hundreds of computer hosts and thousands of devices and servers.

Andy

# 9 years ago
Andy	TCS_GMRT Please can u share the link from where i can download HDB++. But does HDB++ supports mysql ? Also where can I found the documents related to HDB++. HDB++ is not released yet but soon will be. To find out more check out the presentations at the previous TANGO meetings in Poland and Grenoble. Andy Edited 9 years ago

# 9 years ago
TCS_GMRT	Hi Andy I don't know why you have multiple TANGO_HOSTs if you only have 3 computers running device servers. I reiterate my question - do you mean computers or TANGO_HOSTs. These are not the same. Can you send us a picture of your control system layout with the TANGO_HOST and computer hosts clearly marked. We have one TANGO_HOST for hundreds of computer hosts and thousands of devices and servers. We have three different computers and 3 different tango hosts. So In host1 and host2 , I have to archive the parameters of host1 and host2 respectively whereas in host3 I have to archive the parameters of host1, host2 and host3. Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT

# 9 years ago

TCS_GMRT

Hi Andy

I don't know why you have multiple TANGO_HOSTs if you only have 3 computers running device servers. I reiterate my question - do you mean computers or TANGO_HOSTs. These are not the same. Can you send us a picture of your control system layout with the TANGO_HOST and computer hosts clearly marked.

We have one TANGO_HOST for hundreds of computer hosts and thousands of devices and servers.

We have three different computers and 3 different tango hosts. So
In host1 and host2 , I have to archive the parameters of host1 and host2 respectively whereas in host3 I have to archive the parameters of host1, host2 and host3.

Thanks and Regards
TCS-GMRT Team

Regards,
TCS_GMRT

# 9 years ago
TCS_GMRT	Hi Rapheal Yes, there is a limit in what mambo can manage at a time. I suggest splitting archiving configurations that contain too many attributes. Actually I have around 200 parameters to archive per tango host. So its not suggestible to split archiving configuration. Here are few other queries: 1.) Is there any API provided to start/stop archiving without using mambo. 2.) Are there any other archiving tools available other than ArchivingRoot-15.2.1 so that I can explore that as well ? Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT Edited 9 years ago

# 9 years ago

TCS_GMRT

Hi Rapheal

Yes, there is a limit in what mambo can manage at a time. I suggest splitting archiving configurations that contain too many attributes.

Actually I have around 200 parameters to archive per tango host. So its not suggestible to split archiving configuration.

Here are few other queries:
1.) Is there any API provided to start/stop archiving without using mambo.

2.) Are there any other archiving tools available other than ArchivingRoot-15.2.1 so that I can explore that as well ?

Thanks and Regards
TCS-GMRT Team

Regards,
TCS_GMRT

Edited 9 years ago