Am 30.05.2011 11:23, schrieb Marc Muehlfeld:
Am 30.05.2011 11:21, schrieb Francis Galiegue:
Which version was it prior to the upgrade, on both the server and clients?
Server: 3.2.3 (self compiled)
Client: 2.5.0p2-8.el5 (from the CentOS 5 Repository)
Some more information, after I did some further testings:
I downgraded one client back to 2.5.0p2-8.el5 and let the server on 3.2.3 and
I still have this issue.
I run the 3.2.3 (server) and 2.5.0p2 (clients) combination since almost 3
weeks. But I haven't had a restore in that time. That's why I haven't seen
this issue until today.
I temporarily downgraded the server to 3.2.2 - then the problem is gone (with
2.5.0p2 and 3.2.3 clients). So this bug was introduced in 3.2.3
--
Marc Muehlfeld (IT-Leiter)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780
http://www.medizinische-genetik.de
