Reporting Log issues/errors

[asb2106]

Im not sure what to expect from the daily emails from FreeNAS, since deployed, I receive this as an email

Code:

No /var/log/mount.today

No /var/log/dmesg.today

Also, something I noticed, after every reboot i loose all logs from before the reboot.

Could someone please help me look in the right direction here. Im at a bit of a loss and searching hasnt resulted in anything all that related.

THANKS

**I could be totally wrong here, but i wonder if this is something to do with a folder not mounting, maybe some access rights not correct, maybe i just really have no idea what im doing.. Potentially completely irrelevant; When i got my plex plugin up and running, I shared the storage with the jail, and inside plex, to access those stores of data, i have to manually type the /usr/local/www/etc, it will not show at any folder level, however typing it accesses the data fine.

 

[dlavigne]

Which build version (from System -> Information)?

 

[asb2106]

FreeNAS-11.1-U4

 

[dlavigne]

Were you able to resolve this?

 

[tij]

by default logs are kept in RAM ... aka you loose logs once computer restarts

you can make logs persistant ... just search for “freenas persistant log” (i would have told you how to do this, but am myself newbie and did not consider implementing it and hence did not research deeper)

 

[Ericloewe]

by default logs are kept in RAM

The system dataset disagrees with you.

/var/log/ is backed by the system dataset.

 

[asb2106]

The system dataset disagrees with you.

/var/log/ is backed by the system dataset.

So after a reboot should the reporting tabs retain the data from before the reboot because it doesn't for me.

Sent from my Pixel 2 XL using Tapatalk

 

[MrToddsFriends]

So after a reboot should the reporting tabs retain the data from before the reboot because it doesn't for me.

It is a known bug that the reporting database gets lost during a reboot/update for (a) certain combination(s) of settings in
System -> System Dataset

https://redmine.ixsystems.com/issues/28862
https://redmine.ixsystems.com/issues/27909

AFAICT this bug does not affect log files in /var/log/.

 

[asb2106]

Happy to say, that upgrading to U5 has fixed this issue!