Not even “Normal”? Then the tooltip should communicate this better. Currently, it only reads:
What makes it more interesting is that if you change it from anything other than “Minimum”, you’d think the default is “Normal” if you revisit that page in the GUI.
In fact, if you forgot “Did I ever change this?”, you might suspect that “Normal” is the default setting, even if it is currently set to “Minimum”.
The tooltip does not tell you what the “default” is. Not even the drop-down tells you. Nor is there any warning about “Log level should never be set above MINIMUM for production environments.”
Of course, I’m on Core. So maybe this is different in SCALE?
EDIT: Wait, so on “Minimum”, you can expect that “error and warning level messages are logged”?
Because if this is “Mininum”…
…error messages can include denied access, issues with accessing files, and other “errors”, which will log the filenames and paths. Unless the tooltip is referring to something else?
Normal installation and operation can be through the web GUI.
However, trouble shooting beyond simple things requires Unix Shell access, generally through SSH though the console could be used.
While a new SysAdmin of TrueNAS can install and use TrueNAS without much ZFS or Unix Shell knowledge, over time such a person NEEDS to learn some things. The longer they use TrueNAS the more they should learn about ZFS and Unix Shell.
Whence the proverbial excrement hits the rotating impellers, it can be hard to gather trouble shooting information. Let alone fix problems.
Here in the forums we are in essence constantly prompting new problem posts to list important, (and generally required), information. Even then, sometimes we have to walk the user through in HOW to gather the information. (Constant in this context means at least once a week, aka >52 times a year…)
We almost need a new user guide;
In the first 6 months learn: Unix Shell zpool status zpool import etc…
In the first year: lsbrk smartctl zpool get all POOL zfs get all POOL/DATASET
Thx Arwen Wiki-San. I’m setting up this device for a small, moderately tech-savvy org who just wants a file server in-house people can do maintenance on and keep running. No advanced config necessary. The GUI should be enough, I think, to mitigate requests for remote hours.
I’m running into a lot of problems I wouldn’t typically expect of a Unix-like OS myself, however, during the initial setup and config process. At first brush, the points of delineation between the capabilities of the GUI and traditional shell interaction seem pretty par-for-the-course, but weird stuff keeps happening. You seem pretty knowledgeable: maybe you could offer some input on my other open topic? Mysterious Permissions Issues in Syncthing/Nextcloud App Installs (24.04) - #3 by NAStyBusiness
