XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Remote syslog broken after update/reboot? - Changing it away, then back fixes.

    Scheduled Pinned Locked Moved Compute
    28 Posts 9 Posters 1.2k Views 8 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stormiS Offline
      stormi Vates πŸͺ XCP-ng Team @MajorP93
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • stormiS Offline
        stormi Vates πŸͺ XCP-ng Team @MajorP93
        last edited by

        @MajorP93 Thanks. That clarifies what happened. I wrongly thought that it was managed in /etc/rsyslog.conf (which never gets overwritten), but it's in /etc/rsyslog.d/xenserver.conf, which can get overwritten if modified by an update.

        1 Reply Last reply Reply Quote 0
        • stormiS Offline
          stormi Vates πŸͺ XCP-ng Team
          last edited by

          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-config package. 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.

          M 1 Reply Last reply Reply Quote 2
          • olivierlambertO Offline
            olivierlambert Vates πŸͺ Co-Founder CEO
            last edited by

            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 πŸ˜†

            1 Reply Last reply Reply Quote 2
            • M Offline
              MajorP93 @stormi
              last edited by

              @stormi Thanks, that sounds great!
              If there is something I can test / provide please let me know!

              rzrR 1 Reply Last reply Reply Quote 0
              • rzrR Offline
                rzr @MajorP93
                last edited by

                @MajorP93

                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

                rzr opened this pull request in xcp-ng-rpms/xcp-ng-release

                closed Preserve /etc/rsyslog.d/xenserver.conf if present #41

                M 1 Reply Last reply Reply Quote 3
                • M Offline
                  michmoor0725
                  last edited by

                  This community is amazing Great job all around!

                  1 Reply Last reply Reply Quote 3
                  • M Offline
                    MajorP93 @rzr
                    last edited by

                    @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!

                    1 Reply Last reply Reply Quote 2
                    • gduperreyG Offline
                      gduperrey Vates πŸͺ XCP-ng Team
                      last edited by

                      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. πŸ™‚

                      M 1 Reply Last reply Reply Quote 2
                      • M Offline
                        MajorP93 @gduperrey
                        last edited by

                        @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

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post