6 Replies Latest reply on Nov 13, 2019 4:10 PM by dmkmills

    Syslog Options

    Masi45673 Novice



      I have upgraded our Esxi 6.5 to Esxi 6.7 U3. After upgrade cannot update Syslog.global path, every time I'm getting .The "Update option values" operation failed for the entity with the following error message.A general system error occurred: Internal error


      Can someone help please.



        • 1. Re: Syslog Options
          sjesse Master
          User ModeratorsvExpert

          Can you provide an example of what your putting in? I may have seen the same thing, Using [datastore]\folder didn't seem to work no matter what I did, but just putting [datastore] did, I was dealing with it for now since I could use the unique directory to seperate the logs for each host anyway.

          • 2. Re: Syslog Options
            Masi45673 Novice

            I'm putting like [Datastore] Syslog/host

            • 3. Re: Syslog Options
              sjesse Master
              User ModeratorsvExpert

              As a test can you just put [datastore], and if that works and noone else replies open a ticket, I'll probably do some time when I have some time. It may be a bug,

              • 4. Re: Syslog Options
                timweaver23 Novice

                You could use powercli to check the current Syslog location ......


                Log onto the Vcenter/host with powercli  ...


                #Then check the current Syslog.global.logDir setting by running


                Get-VMHostAdvancedConfiguration -Name "Syslog.global.logDir"


                #change the setting by using the following


                Set-VMHostAdvancedConfiguration -Name "Syslog.global.logDir" -Value "Datastorename/scratch/log"


                Make sure you have the right path to the log folder

                • 5. Re: Syslog Options
                  Vijay2027 Expert

                  Please provide screenshot if it is possible. Thank you.

                  • 6. Re: Syslog Options
                    dmkmills Lurker

                    Hey, I just had this problem myself, so I looked at the system logs while I tried to set it -- the actual error it was throwing was "directory must exist and be accessible".


                    I was trying to set it to [DS1] /syslogs --- so I just logged onto the host and went to /vmfs/volumes/DS1 and did a mkdir syslogs.   After that, it accepted the value just fine.

                    If you're not going to use the "unique log dir" directive, you may have to make each host folder manually, but at least it seems to be workable!


                    Hopefully this helps, I just happened to see this as I was having the same problem!  Good luck!