Forwarding logs using syslog fails with a message too long error in RHOCP 4

Solution Verified - Updated -

Issue

  • Fluentd fails forwarding logs to a syslog server with error Errno::EMSGSIZE:

    2021-03-10 16:02:41 +0000 [warn]: [syslog] failed to flush the buffer. retry_time=2422 next_retry_seconds=2021-03-10 16:03:47 +0000 chunk="xxxxxxxxxxxxxxx" error_class=Errno::EMSGSIZE error="Message too long - sendto(2) for \"10.0.0.1\" port 514"
    
  • FluentDHighErrorRate alert is shown in the OpenShift Console when sending logs to syslog.
  • CollectorHighErrorRate alert is observed when sending logs to a syslog server
  • Vector fails forwarding some logs to a syslog server with the error:

    2025-04-03T12:28:28.352935582Z 2025-04-03T12:28:28.352804Z ERROR sink{component_kind="sink" component_id=output_rsyslog_ahps component_type=socket}: vector::internal_events::socket: Error sending data. error=Message too long (os error 90) error_code="socket_send" error_type="writer_failed" stage="sending" mode=udp internal_log_rate_limit=true
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Logging (RHOL)
    • 5
  • Fluentd
  • Vector
  • Syslog

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content