syslog enhancements

[tjb_altf4]

#1

Currently for local syslog storage, you can only use existing shares for syslog storage, and cannot specify custom paths / pool / unassigned device etc.

I'd like to see the ability to add custom paths in the GUI, without needing to modify config files as is the only workaround currently (shown below for reference).

 

My particular use case is I have a pool named system which does not participate in user shares, which is where I want my logs to reside (alongside related items such as swapfile, docker.img, libvirt etc)..

 

On 4/27/2020 at 8:11 PM, bonienl said:

Though, I don't recommend to write logs to unassigned devices, it is possible to do.

 

You need to manually edit the file /config/rsyslog.cfg on your USB device and change the setting "server_folder" to the desired destination.

Restarting the syslog server is required to take the new setting into account and the GUI will display "custom" as location.

 

#2

As a sneaky related request, I'd also like to see a force log rotate button added.

 

Thanks!

 

 

 

[-Daedalus]

+1

 

I'd like this as well. Having an entire share just for logs is a little much I think.

[bonienl]

31 minutes ago, -Daedalus said:

Having an entire share just for logs is a little much I think.

 

Syslog supports subfolders, but you need to edit the configuration file to make it work.

 

[-Daedalus]

I know, just adding the +1 because the request was for support for this on the UI.

[dalben]

I've noticed that despite having syslog setup, any startup log syslog message that occur before unraid starts the syslog server are lost, or if you mirror the syslog, can be found on flash/logs/syslog.

 

Also plenty of syslog server errors in syslog when the syslog server hasn't started yet.  Understand they can be ignored, but they are annoying.

 

Mar  8 06:57:22 tdm rsyslogd: omfwd/udp: socket 8: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Mar  8 06:57:22 tdm rsyslogd: omfwd: socket 8: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Mar  8 06:57:22 tdm rsyslogd: action 'action-3-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2102.0 try https://www.rsyslog.com/e/2007 ]
Mar  8 06:57:22 tdm rsyslogd: action 'action-3-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2102.0 try https://www.rsyslog.com/e/2359 ]
Mar  8 06:57:22 tdm rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Mar  8 06:57:22 tdm rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Mar  8 06:57:22 tdm rsyslogd: action 'action-3-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2102.0 try https://www.rsyslog.com/e/2007 ]
Mar  8 06:57:22 tdm rsyslogd: action 'action-3-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2102.0 try https://www.rsyslog.com/e/2359 ]
Mar  8 06:57:22 tdm rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Mar  8 06:57:22 tdm rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]

 

[nlz]

+1