Unstable warning wth

[hendry]

On the first of July I received:

Code:

UNSTABLE--Fail: 0, Warn: 1, Pass: 0
freenas.local:nas-health:FreeNAS health check is warning.

via my preconfigured AWS SNS. Minutes later I received:

Code:

HEALTHY--Fail: 0, Warn: 0, Pass: 1
freenas.local:nas-health:FreeNAS health check is passing.

In my logs I see:

Code:

Jun 30 00:00:00 freenas syslog-ng[1709]: Configuration reload request received, reloading configuration;
Jul  1 00:00:00 freenas syslog-ng[1709]: Configuration reload request received, reloading configuration;
Jul  1 00:00:00 freenas ZFS: vdev state changed, pool_guid=3739077612765955297 vdev_guid=14358330496744373439
Jul  1 00:00:01 freenas ZFS: vdev state changed, pool_guid=3739077612765955297 vdev_guid=15028414175051028718
Jul  1 03:45:01 freenas ZFS: vdev state changed, pool_guid=16173962046104270701 vdev_guid=6933725108086962905
Jul  2 00:00:00 freenas syslog-ng[1709]: Configuration reload request received, reloading configuration;
Jul  2 02:50:41 freenas kernel: bge0: link state changed to DOWN

Sidenote: I'm a little perturbed that there is no Web UI to look at logs. Is this the bug I should be tracking https://redmine.ixsystems.com/issues/23768 ? Do people manage to get their logs upto AWS Cloudwatch?

So my question is... ummm what am I supposed to make of this incident?

 

[Chris Moore]

Code:

Jun 30 00:00:00 freenas syslog-ng[1709]: Configuration reload request received, reloading configuration;
Jul  1 00:00:00 freenas syslog-ng[1709]: Configuration reload request received, reloading configuration;

This is normal. Happens every day at midnight.
Whatever it is that you are using to monitor your FreeNAS doesn't know what it is looking at and is alerting you over normal behavior.

Here are some scripts that you should use instead.

Github repository for FreeNAS scripts, including disk burnin
https://forums.freenas.org/index.ph...for-freenas-scripts-including-disk-burnin.28/