Security Run Output, Any Issues?

[NightNetworks]

FreeNAS.local changes in mounted filesystems:
10c10,11
< ESXi/VMs /mnt/ESXi/VMs zfs rw,nfsv4acls 0 0
---
> Extra /mnt/Extra zfs rw,nfsv4acls 0 0
> Extra/Extra /mnt/Extra/Extra zfs rw,nfsv4acls 0 0

FreeNAS.local kernel log messages:
> ugen1.3: <vendor 0x0000> at usbus1
> uhub4: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus1
> ugen1.4: <vendor 0x0557> at usbus1
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus1
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus1
> ugen1.5: <vendor 0x13fe> at usbus1
> umass0: <vendor 0x13fe Patriot Memory, class 0/0, rev 2.10/1.00, addr 5> on usbus1
> umass0: SCSI over Bulk-Only; quirks = 0x8100
> umass0:7:0:-1: Attached to scbus7
> Timecounter "TSC-low" frequency 1400030856 Hz quality 1000
> vboxdrv: fAsync=0 offMin=0x2c0 offMax=0xf94
> WARNING: 192.168.2.1 (iqn.1998-01.com.vmware:esxi-1d4dad82): no ping reply (NOP-Out) after 5 seconds; dropping connection
> pid 2130 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> GEOM_ELI: Device ada5p1.eli destroyed.
> GEOM_ELI: Detached ada5p1.eli on last close.
> GEOM_ELI: Device ada4p1.eli destroyed.
> GEOM_ELI: Detached ada4p1.eli on last close.
> GEOM_ELI: Device ada0p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: software

-- End of security output --

As the thread suggests I am new to FreeNAS and thought that I would post the Security Run Output e-mail that I got last night to see if there are any issues...

The only two things that I see that may be an issue is the warning regarding the "no ping reply" and the "tsc-low frequency". I think that I know what the "no ping reply" issue is and will look into that, but as far as the "tsc-low frequency" the forums suggested that is an issue with the clock? I am not seeing any issues with the clock?

Thanks in advance!

 

[SweetAndLow]

Looks like you rebooted your box recently? You get an email when this happens.

 

[NightNetworks]

Looks like you rebooted your box recently? You get an email when this happens.

Yes, I rebooted it about 10 hours ago (give or take). So I can ignore the whole time clock thing? I also rebooted the ESXi box as well... thats why the failed PING response is there. Just for good measure though I did confirm this morning that the FreeNAS box can ping the ESXi host on that IP.

Out of curiosity what in that log indicated that the box had been rebooted? Is there some place that I can go that has explanations of the different outputs in the log, for learning purposes?

 

[SweetAndLow]

That log message is just the snipit from the messages file. And the logs are the same when a computer boots so easy to remember. Nothing specifically stands out.

 

[NightNetworks]

That log message is just the snipit from the messages file. And the logs are the same when a computer boots so easy to remember. Nothing specifically stands out.

Oh, OK... makes since, thank you for the information.