DCO 8.1.0 Genome Import Error

DCIM_Support · ‎2020-07-04

This question was originally posted on DCIM Support by Mark Tucker on 2017-10-31

Hi Guy's,

When trying to apply the new genome update from tools-->Prefernces–>Genome Library I get the below error message ? I have attached the client.log log files.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Jef Faridi on 2017-11-01

Hi Mark,

I could easily make a genome update without any problem. I guess, your issue likely solution related, so would it be possible to ask for:

- sever logs (can be downloaded from server webmin interface, StruxureWare DC Operation > Download Log Files > "Download log files")

- copy of the latest backup file

If you have multiple rooms in your setup, are you able to open all rooms?

It might also make sense to retry the genome update by using a clean installed DCO client (this is to make sure that the client has all plugins).

It would also be good idea to do the genome update during the time that other users are not connected/not using the application (DCO).

I will send you an invite to my =S= box shortly, so the data can be safely shared with me (if it's okay with you), thanks.

Kind regards

DCIM_Support · ‎2020-07-04

This answer was originally posted on DCIM Support by Jef Faridi on 2017-11-08

Hi Mark,

Many thanks for providing data.

Issue seems to be cluster related, currently Genome Library update on a cluster setup fails. It is reproducible and I have registered a bug report for this.

Workaround: the current workaround is to offline the slave node, and then run the genome update:

1- Turn off the slave node (or ssh log in to the slave node, and run "sudo systemctl stop operations")

2- Start desktop client, and run the genome update. Now it should complete successfully.

3- Turn on/reboot the slave node

That's it. Please let me know if you have questions, thanks.

The status of the nodes can be identified via webmin interface, StruxureWare DC Operation > Status

Kind regards

DCIM_Support · ‎2020-07-04

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.