Every year, since the last 3 years the same problem. When there is the time change and the clock changes from 3 a.m. to 2 a.m. on last Sunday of Octuber the Dude database is corrupted and I have to reinstall the Dude and restore the last backup.
The bug is still on 3.4. Anybody hace noticied this?
My install still works fine.
What is corrupted?
I suppose it is the historical data in the database but, believe me, every year. When I checked on Sunday morning Dude was hunged. I restarted the computer and then when I turned on the Dude all the screen appeared with the word “Loading” and that’s all I can do. The only solution that I have found is to reinstall reseting old configuration and after that restore the last XML configuration.
I have two Dudes with Windows XP running on it and the two machines in different places with the samen problem every year. Perhaps is something to do with the Dude and Windows XP. For more details the Dude server is running on the same machine.
Is as if the Dude couldn’t understand a repeted hour in the database because when there is the time change on Spring there is no problem. On Spring time change there is no repeated hour, just a “missing” hour.
QpoX, are You running the Dude and the Dude server on the same machine? What Windows do You use?