2 Replies Latest reply on Aug 25, 2017 5:55 AM by TheBobkin

    VMware Error

    LBCatalogo Lurker

      Hi guys,

       

      We are encountering this error on our vmware:

       

      2017-08-15T10:15crond: USER root pid 274151686 cmd /usr/lib/vmware/vsan/bin/vsanObserver.sh

      2017-08-15T10:15[274151687]: starting hostd probing.

      2017-08-15T10:15vsanObserver .sh: vsantraced is not started - can't start vsanObserver

      2017-08-15T10:15:01Z syslog[40539]: starting hostd probing.

      2017-08-15T10:16:01Z crond[33605]: crond: USER root pid 40577 cmd /usr/lib/vmware/vsan/bin/vsanObserver.sh

      2017-08-15T10:16:01Z root: vsanObserver.sh: vsantraced is not started - can't start vsanObserver

      2017-08-15T10:16:23Z smartd: smartmgt: plugin /usr/lib/vmware/smart_plugins/libsmartnvme.so is already loaded

      2017-08-15T10:16:23Z smartd: smartmgt: plugin /usr/lib/vmware/smart_plugins/libsmartmicron.so is already loaded

      2017-08-15T10:16:23Z smartd: smartmgt: plugin /usr/lib/vmware/smart_plugins/libsmartnvme.so is already loaded

       

      Although we don't have vSAN installed on our VmWare. Do you guys know what this mean and what do we need to do to resolve this issue.

       

      Thanks.

        • 1. Re: VMware Error
          jameseydoyle Hot Shot
          VMware Employees

          I assume you are finding this 'error' in the syslog.log file? What is the impact to your operations?

           

          The vsantraced is a service that monitors vSAN operations and would be a requirement for getting the vsanObserver to run. vsanObserver is performance monitoring tool and each host participating in a vSAN cluster will collect performance data in the background using this service.

           

          There are scheduled cron jobs that run in the background on your ESXi and these include the performance collection job for vSAN. You can find the cron job configuration at /var/spool/cron/crontab/root. In this file are all the scheduled tasks that ESXi will run, including the vsanObserver.sh, which is scheduled to run every 2 minutes. If vSAN is not running, the necessary daemons will not be running resulting in the errors you are seeing. These 'errors' can be safely ignored as they do not indicate a problem, not should they be causing any impact.

          • 2. Re: VMware Error
            TheBobkin Virtuoso
            VMware EmployeesvExpert

            Hello LBCatalogo,

             

             

            "Although we don't have vSAN installed on our VmWare" - vSAN is built into the vmkernel and thus is present in every ESXi installation (from 5.5 onwards).

            If you do not have vSAN enabled then logging messages such as these referencing vSAN-daemons can be safely ignored.

             

             

            Bob