Remote syslog broken after update/reboot? - Changing it away, then back fixes.
-
The fix was already high in the priority list anyway, but I'll try to make sure we don't postpone it more. Had I realized sooner, I would have made it so we'd release it earlier.
According to the package definitions, we even overwrite it each time we update the
xcp-ng-release-configpackage. I'm surprised that we haven't had more support requests.I'll see if we can release a quick fix that just leaves the file alone until we apply the change that will move the remote configuration to its own file.
-
There's a similar magic we've seen countless time with XO: you have a bug that nobody reports for years and suddenly it pops from various sources (or with many details so it's easy to spot), you think it's recently introduced, you check your diff and then after hours you realize it's there since a while
