v7.1.4

I'm using the logging trickery from the docs to log locally however I'm wanting to log to an Unassigned Device, not a share on the array. Since I can't select UD Devices from the GUI I've been trying to hardcode the directory into rsyslog.cfg, rsyslog.conf, & rsyslog.local (when present) . This used to be possible but as hoopster mentioned it doesn't seem to work anymore? @Hoopster did you ever fix your issue with this?

I've edited the files (in /boot/config/ & /etc/ just in case) and tried restarting the service and the entire server but it stubbornly sticks to whatever directory was last chosen through the web ui. It's not changing the modified files back (unless I select a new directory through the web ui) it's almost like it's not reading those files or it's getting it's config from somewhere else.

Is there somewhere else UnRAID stores its rsyslog config besides the files in the /boot/config/ folder and the /etc/ folder for the live in RAM system? Or is my config just wrong somehow?

node-diagnostics-20250715-0718.zip

Edited July 15, 2025Jul 15 by weirdcrap

On 7/15/2025 at 6:20 AM, weirdcrap said:

did you ever fix your issue with this?

No. <custom> appears in the drop-down list for syslog configuration on all three of my servers but it is not selectable. On all three servers, I now have to use an Unraid share or pool device I have setup for the syslog. I wish <custom> worked the way it used to but that was broken/changed a long time ago and has never reverted to its former functionality.

I even went to the trouble of documenting how to set up the syslog for a local <custom> location on an unassigned devices, but, that appears to be no longer possible.

Edited July 16, 2025Jul 16 by Hoopster

12 hours ago, Hoopster said:

No. <custom> appears in the drop-down list for syslog configuration on all three of my servers but it is not selectable. On all three servers, I now have to use an Unraid share or pool device I have setup for the syslog. I wish <custom> worked the way it used to but that was broken/changed a long time ago and has never reverted to its former functionality.

I even went to the trouble of documenting how to set up the syslog for a local <custom> location on an unassigned devices, but, that appears to be no longer possible.

Well that sucks. Since this at one point worked and since the <custom> option is still present I'm going to open a bug report on this. Maybe limetech will fix it.

In the meantime I have some Pi 2Bs that I can just plug the USB drive into and setup logging remotely that way. It's irritating I have to setup an entirely separate device when this was literally working for me up until last week when I changed a setting not realizing it was going to break my perfectly functional config permanently.

Edited July 17, 2025Jul 17 by weirdcrap