(SOLVED) Syslog[6] Write Error, Too Large?

[Squeeth]

I keep receiving messages from my log saying that it is having a write error due to file being too large? This just recently started happening and can not figure out what changes I have made that could have caused these to appear. I've browsed through the diags myself, however I'll admit that there is far smarter and more knowledgeable minds out there that will probably be able to tell what's going on.

Jan 16 21:17:29 ETHAN-UNRAID rsyslogd: file '/boot/logs/syslog'[6] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: File too large [v8.2002.0 try https://www.rsyslog.com/e/2027 ]
Jan 16 21:17:29 ETHAN-UNRAID rsyslogd: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ]

ethan-unraid-diagnostics-20220116-2245.zip

Edited May 2, 2022 by Squeeth

[DesertCookie]

Having the same issue. My server spits out a lot of these but nothing else in the log:

rsyslogd: file '/boot/logs/syslog'[6] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: File too large [v8.2002.0 try https://www.rsyslog.com/e/2027 ]
rsyslogd: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ]

 

[Squid]

You have mirror to flash enabled and looks like you're running into a size limitation.

 

Disable mirror to flash in syslog settings (and delete the file on the flash)  It really should only be enabled on an as-needed basis.  Fix Common Problems should have been notifying you about that.