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

    how to get syslog to remote to work?

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 1.8k Views 3 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.
    • D Offline
      djingo
      last edited by djingo

      hi there. I have set a remote syslog server in XO, but nothing is being sent by XCP. I have taken a look at /etc/rsyslog.conf, there is no remote server setting in there (there is an example which is commented out) as there is a setup option in XO I am reluctant to edit the /etc/rsyslog.conf manually.
      how do I get this to work?

      T 1 Reply Last reply Reply Quote 0
      • T Offline
        techjeff @djingo
        last edited by

        @djingo, FWIW, configuring with XO (from sources) has worked just fine for me. I actually just tested this the other day because I saw that my log server wasn't getting anything. When I looked at the pool settings I realized that I had made a typo. After I fixed it the logs started flowing.

        TL;DR, I think just setting the remote syslog host is enough, but I could be wrong.

        The host's logs might have some insights you can glean: https://xcp-ng.org/docs/troubleshooting.html#log-files

        D 1 Reply Last reply Reply Quote 0
        • D Offline
          djingo @techjeff
          last edited by

          @techjeff yes the hostname also shows in xsconsole. The hostname was correct.

          There must be a problem of some sort. Maybe a Patch overwrite the /etc/rsyslog.d/xenorchestra.conf at some point in time and then the line with the syslog server was gone.

          What now helped was removing the syslog server in xsconsole and re-adding it.

          Removing it did not work in XO as XO UI insists that the server name cannot be empty.
          This maybe should be fixed.

          lawrencesystemsL 1 Reply Last reply Reply Quote 0
          • lawrencesystemsL Offline
            lawrencesystems Ambassador @djingo
            last edited by

            @djingo
            My syslog stopped working (I think after one o the updates) and this bug still exists. If you trying removing it form the Pool or individual hosts in the Pool via XO it will not let you have it as blank. If you ssh in and use xsconsole you can remove the syslog server and but it will not let you specify a port. But once it has been removed from xsconsole you can go back into XO and add in the syslogserver along with a non-default port such as

            192.168.2.7:1521

            and it will work.

            1 Reply Last reply Reply Quote 0

            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