Hello.
I installed/upgraded TrueNAS Fangtooth 24.05-RC.1 and whenever I want to shut down I need to answer why I want to shut down the system.
Why was this introduced?
Is this logged somewhere?
Is it reported back to ix systems?
Can I turn off this requirement somehow?
I run this as part of a small Personal NAS / Homelab, and it seems to me the “Sutdown reason” is more geared to the professional / enterprise servers.
Thank you.
As part of broader improvements to auditing and STIG security compliance.
Yes, System > Audit shows the logs. TrueNAS records the shutdown reason, along with other details like the initiating user and timestamp. Ex:
No. If you manually submitted a debug as part of a bug report I presume it would be included along with your other logs, but there is no automatic collection.
Not currently. You could propose a Feature Request, but I don’t know how much traction adding an off switch to a security feature to avoid a minor inconvenience would get internally.
An off option would be kinda nice…
Hopefully that’s UI only and a api call will in fact shut down, or, UPS will in fact shut down!
Please, don’t scare me 
Thanks for the response and explanation
“I’m sorry. I’m afraid I can’t do that.”
2001 yeses to that.
My usage model for TrueNAS is quite atypical: The box is used solely by myself. Since I don’t want to waste energy my TrueNAS box is by default off and only switched on when needed.
I mainly use it as backup target and for some apps (e.g. paperless ngx) which I use rather infrequently.
For this usage pattern the mandatory reason for shutdown is nuts. I’d really wanted to have a config option to switch it off.
Meanwhile I’m using cmd line using ssh root@truenas 'shutdown -h now'.
Or at least a choice that reflects that it is not meant to be running 24/7.
Wait until they started asking, “What is the reason you need a NAS server?” every time you boot up. 
It’s not that unusual for a server OS to prompt for a reason for shutdown / reboot.
C.f. Windows server. We’re not collecting this information. It’s to provide server-side audit trails for why events happened for business environments.
I have seen in another thread that the api has changed a bit, just for be sure… there Is some action needed on UPS section or Is intended to continue working as usual? Thanks
Fair enough for “business environments”. But home users would really like to have a big red switch to disable all these audit trail shenanigans. We’re already asked to tick a checkbox to confirm, the “reason” field, which cannot be empty under penalty of cancelling shutdown, is just needlessly annoying.
I second this request. There should be an option to avoid having to jump through this hoop which is completely unnecessary in testing or personal use environments. This is a very simple UI coding task and could be easily implemented if requested by enough users.
If you’re citing Windows Server as precedent, let’s acknowledge their documentation on how to disable or customize the Shutdown Event Tracker.
24 years too late…
Dave Bowman: Shutdown the server, HAL.
HAL: I’m sorry, Dave. I’m afraid I can’t do that.
