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.

Description of problem:
same as here:
https://bugzilla.redhat.com/show_bug.cgi?id=963942

Hello,
I know this is an old discussion,but I just encountered same problem.
Could you tell me please if there is any way of sending those messages/files from spool to processing so they can get to receiver/consumer?
I expect to be an workaround that can make rsyslog read the spool, or I hope it exists.
The second question is do I neet to have the .qi file?Because in some of my problematic server there is the file but in some of them there is not
Thank you


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 5.11 (Tikanga)
rsyslogd 7.6.7


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I will not put details about version and so on as the question is very general
Thank you for understanding

(In reply to printul77700 from comment #0)
> Could you tell me please if there is any way of sending those messages/files
> from spool to processing so they can get to receiver/consumer?

There's a simple script called rsyslog-recover-qi.pl in the package that might be of some help.

> The second question is do I neet to have the .qi file?

Yes, you do.

> Version-Release number of selected component (if applicable):
> Red Hat Enterprise Linux Server release 5.11 (Tikanga)

This bug is filed for el6..?

> rsyslogd 7.6.7
>
> I will not put details about version and so on as the question is very
> general
> Thank you for understanding

The package you've filed the bug for won't get any more updates, hence I'm closing this bz.