Error in Console syslog-ng[2423]: I/O error occurred while writing; fd='x', error='Message too long (40)'

[Apildk]

Hey there.

My console is currently being spammed by this error as seen in the title, and in the screenshot attached.

root@STORAGE1[~]# zpool status -v array pool: array state: ONLINE scan: none requested config: NAME STATE READ WRITE CKS UM array ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gptid/246500a2-c28e-11e9-b3d8-fcaa1442a9b1 ONLINE 0 0 0 gptid/26b5d1b4-c28e-11e9-b3d8-fcaa1442a9b1 ONLINE 0 0 0 gptid/28e0677a-c28e-11e9-b3d8-fcaa1442a9b1 ONLINE 0 0 0 gptid/2b11adf5-c28e-11e9-b3d8-fcaa1442a9b1 ONLINE 0 0 0 gptid/2d2da7f1-c28e-11e9-b3d8-fcaa1442a9b1 ONLINE 0 0 0 cache gptid/0e9fe852-c4f5-11e9-bbb4-000c29fe1d57 ONLINE 0 0 0 errors: No known data errors
I am not experiencing any problems with the freenas, but concerned what this output means.
Anyone able to help ?

Best regards

 

[dlavigne]

Are you running any jails/plugins? If so, which apps are installed?

 

[Apildk]

Are you running any jails/plugins? If so, which apps are installed?

No jails/plugins.
Services it is running, Smart, SMB, SNMP, SSH and WebDAV.
Els it has a replication task to another freenas, short and long smart tests, an periodic snapshot task of the array, standart scrub task, and this Tunable to stop some other snmpd spam.

I think that is everything.

Best regards
Apil

 

[xurubezi]

I had the same console messages on a server after upgrading to 11.2. There were also 2 additional related lines in /var/log/messages about sending to a remote syslog server. To solve it I went to System -> General, removed the syslog server address, saved, added syslog server back in and saved again. Remote syslog then started working again and messages stopped. Didn't reboot so not sure if it will come back or not.

Aug 28 18:19:16 fnas2 syslog-ng[3593]: Syslog connection established; fd='23', server='AF_INET(192.168.1.22:514)', local='AF_INET(0.0.0.0:514)'
Aug 28 18:19:16 fnas2 syslog-ng[3593]: I/O error occurred while writing; fd='23', error='Message too long (40)'
Aug 28 18:19:16 fnas2 syslog-ng[3593]: Syslog connection broken; fd='23', server='AF_INET(192.168.1.22:514)', time_reopen='60'

 

[SMnasMAN]

I too have been seeing tons of these messages for pretty much the entire 9 or so months that ive been testing / running freenas (i have only used various releases of 11.2). I always use remote syslog (usually set to notice level and being sent to a local splunk server) Ive seen it on different FN hardware (all physical FN, not a FN VM).

Even currently on my "final/production" FN build, which is running 11.2-u5 and syslogging to a local splunk. server. My boot volume is a mirror of 2x intel

any ideas on the cause or fix of these? Also are the syslog , logs, being written to your actual boot volume/disk? (or are they being saved to ram , im pretty sure its ram)
thanks

Code:

Sep  3 00:22:50 freenas syslog-ng[8838]: Syslog connection broken; fd='23', server='AF_INET(172.17.172.5:8011)', time_reopen='60'
Sep  3 00:23:50 freenas syslog-ng[8838]: Syslog connection established; fd='21', server='AF_INET(172.17.172.5:8011)', local='AF_INE$
Sep  3 00:24:15 freenas syslog-ng[8838]: I/O error occurred while writing; fd='21', error='No route to host (65)'
Sep  3 00:24:15 freenas syslog-ng[8838]: Syslog connection broken; fd='21', server='AF_INET(172.17.172.5:8011)', time_reopen='60'
Sep  3 00:25:15 freenas syslog-ng[8838]: Syslog connection established; fd='23', server='AF_INET(172.17.172.5:8011)', local='AF_INE$
Sep  3 00:25:16 freenas syslog-ng[8838]: I/O error occurred while writing; fd='23', error='No route to host (65)'
Sep  3 00:25:16 freenas syslog-ng[8838]: Syslog connection broken; fd='23', server='AF_INET(172.17.172.5:8011)', time_reopen='60'
Sep  3 00:26:16 freenas syslog-ng[8838]: Syslog connection established; fd='21', server='AF_INET(172.17.172.5:8011)', local='AF_INE$
Sep  3 00:26:17 freenas syslog-ng[8838]: I/O error occurred while writing; fd='21', error='No route to host (65)'
Sep  3 00:26:17 freenas syslog-ng[8838]: Syslog connection broken; fd='21', server='AF_INET(172.17.172.5:8011)', time_reopen='60'