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 Solved Compute
    32 Posts 9 Posters 7.0k 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.
    • M
      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
        rzr Vates πŸͺ XCP-ng Team @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

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

          This community is amazing Great job all around!

          1 Reply Last reply
          Reply Quote 3
          • M
            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
              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 2 Replies Last reply
              Reply Quote 2
              • M
                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
                • M
                  MajorP93 @gduperrey
                  last edited by

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

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

                    Yay!! \o/ Thanks for the reminder on this issue, it wasn't hard to fix but was kind of lost in the backlog ^^

                    stormiS 1 Reply Last reply
                    Reply Quote 1
                    • olivierlambertO olivierlambert marked this topic as a question on
                    • olivierlambertO olivierlambert has marked this topic as solved on
                    • stormiS
                      stormi Vates πŸͺ XCP-ng Team @olivierlambert
                      last edited by

                      @olivierlambert No it wasn't πŸ™‚

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

                        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.

                        1 Reply Last reply
                        Reply Quote 2

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better πŸ’—

                        Register Login
                        • First post
                          Last post