Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionOndrej Valousek
2011-05-03 09:26:32 UTC
Simple configuration on the client:
*.* @loghost
produces on the server (loghost) only one single message:
2011-05-03T11:17:52+02:00 data rsyslogd: [origin software="rsyslogd" swVersion="4.6.2" x-pid="2292" x-info="http://www.rsyslog.com"] (re)start
No other syslog messages are forwarded to the server. If I run the client in the debug mode I can see that it does not even try to send anything.
Client (data) - RHEL-6
Server (loghost) - RHEL-5.5
(In reply to comment #0)
UDP forwarding seems to work for me.
Please note that if the configuration on the client really consist only of that one line, rsyslog doesn't have any source of messagess. You need to load some input modules for the daemon to do anything useful, e.g.:
$ModLoad imuxsock.so # userspace logging
$ModLoad imklog.so # kernel logging
If that is not the whole configuration, can you please provide your rsyslog.conf files and the debug mode output?
In the debug mode, you should see lines like:
7453.924901200:7f727b51f710: Called action, logging to builtin-fwd
7453.924909973:7f727b51f710: 10.1.2.3:514/udp
You can try running tcpdump to see if the messages actually get sent:
tcpdump -i <if> udp and host <loghost>
Be aware that the forwarded messages still retain their original facility, so they may end up in a different file than /var/log/messages. Therefore you would only see the startup message.