Corrupt Configuration File after update to v4.0.5.17

You found a bug or have any issues? Please post them here!
Post Reply
User avatar
Michel67
Posts: 166
Joined: 28 Nov 2016 19:53
Corrupt Configuration File after update to v4.0.5.17

Post by Michel67 »

updated to the latest version. unfortunately something went wrong. I could solve it myself.
Attachments
Knipsel3.PNG
Knipsel3.PNG (10.81 KiB) Viewed 4178 times
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Corrupt Configuration File after update to v4.0.5.17

Post by radio42 »

Normally this can only happen, if there was either a disk or I/O write error happening or if the GPIO client was terminated abnormally (which wouldn't happen with a regular update) - so I am more guess, that it was related to an issue in the I/O sub-system of the OS or even a hardeware issue.
Do you happen to have the corrupt GPIOClient.config file available to look at where/how it got corrupted?
User avatar
Michel67
Posts: 166
Joined: 28 Nov 2016 19:53
Re: Corrupt Configuration File after update to v4.0.5.17

Post by Michel67 »

Hello, updating was normal like other times. I don't have the corrupt GPIOClient.config file because I chose YES, delete the file. After a restart everything worked fine again. I only had to enable the GPIO-Client at startup.

Post Reply