Closed philipgiuliani closed 4 years ago
This error was maybe related to the Supervisor Deadlock of Horde 0.8.2. Until now it did not happen again with Horde 0.8.3
Thanks for checking back in and please reopen if you see this happen again with >0.8.3!
Looking through our logs I could find a lot of these exceptions. They don't seem to have any negative effect on the environment though.
Horde Version: 0.8.2