Remote syslog broken after update/reboot? - Changing it away, then back fixes.
-
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
-
@stormi Thanks, that sounds great!
If there is something I can test / provide please let me know! -
Fix has been merged, expect a package in your updates soon.
Meanwhile check this notice about upcoming changes regarding remote syslog.
https://github.com/xcp-ng-rpms/xcp-ng-release/pull/41#issuecomment-3800419449
-
This community is amazing Great job all around!
-
@rzr Thank you very much!
@michmoor0725 Absolutely! The community is another aspect of why working with XCP-ng is a lot more fun compared to working with VMWare!
-
The update should now be available. You can view the announcement here: https://xcp-ng.org/blog/2026/01/29/january-2026-security-and-maintenance-updates-for-xcp-ng-8-3-lts/
So don’t hesitate to update it and confirm that it properly addresses the issue.
-
@gduperrey Thanks!
Will test tomorrow as our internal lab / test environment is currently unavailable.
I will inform you about the results of my testing here.Best regards
-
@gduperrey Hey,
I tested it at can confirm that after applying latest set of patches and rebooting remote syslog is still working fine.
It appears to be fixed, good job guys -
Yay!! \o/ Thanks for the reminder on this issue, it wasn't hard to fix but was kind of lost in the backlog ^^
-
O olivierlambert marked this topic as a question
-
O olivierlambert has marked this topic as solved
-
@olivierlambert No it wasn't
-
To elaborate: it was already in progress, but delayed due to 1. the fact that I underestimated the impact (I thought we'd overwrite the file only when we'd modify it, not every update the package) and 2. lots of other priorities keeping the team busy.
But it's clearly the reminder, and the help in better diagnosing it, that allowed to have it re-prioritized and (partly, we've mostly bought time to fix it properly, by simply avoiding to touch the file at all at the moment) fixed so fast.
