Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
Goferd on client system prints syslog messages into pts/tty sessions.
We received a lot of complaints from our users.
Example :
Message from syslogd@slzurncsgl02 at Nov 29 14:30:06 ...
�<30>goferd: [INFO][pulp.agent.c7e5a2c6-c83d-4e9c-9dac-4e0c61f4fb10] root:487 - connecting to slttpr0fxl01.zres.ztech:5647...
Message from syslogd@slzurncsgl02 at Nov 29 14:30:07 ...
�<30>goferd: [INFO][pulp.agent.c7e5a2c6-c83d-4e9c-9dac-4e0c61f4fb10] root:507 - connected to slttpr0fxl01.zres.ztech:5647
Message from syslogd@slzurncsgl02 at Nov 29 14:30:17 ...
�<30>goferd: [INFO][pulp.agent.c7e5a2c6-c83d-4e9c-9dac-4e0c61f4fb10] root:487 - connecting to slttpr0fxl01.zres.ztech:5647...
Message from syslogd@slzurncsgl02 at Nov 29 14:30:17 ...
�<30>goferd: [INFO][pulp.agent.c7e5a2c6-c83d-4e9c-9dac-4e0c61f4fb10] root:507 - connected to slttpr0fxl01.zres.ztech:5647
Message from syslogd@slzurncsgl02 at Nov 29 14:30:27 ...
�<30>goferd: [INFO][pulp.agent.c7e5a2c6-c83d-4e9c-9dac-4e0c61f4fb10] root:487 - connecting to slttpr0fxl01.zres.ztech:5647...
Message from syslogd@slzurncsgl02 at Nov 29 14:30:28 ...
�<30>goferd: [INFO][pulp.agent.c7e5a2c6-c83d-4e9c-9dac-4e0c61f4fb10] root:507 - connected to slttpr0fxl01.zres.ztech:5647
Version-Release number of selected component (if applicable):
# yum info katello-agent
Installed Packages
Name : katello-agent
Arch : noarch
Version : 2.2.6
Release : 1.el6
Size : 49 k
Repo : installed
From repo : rhel-6-server-satellite-tools-6.1-rpms
Summary : The Katello Agent
URL : https://fedorahosted.org/katello/
License : LGPLv2
Description : Provides plugin for gofer, which allows communicating with Katello server
: and execute scheduled actions.
Expected results:
Goferd should not spam pts/tty sessions.
Additional info:
As a workaround, I tried editing goferd configuration /etc/gofer/agent.conf to only log critical events (since the events logged have INFO severity) but apparently it was simply ignored (which is probably a bug too).
Hello,
We are using RHEL 6.4. I tried to find the bug you are referring to but failed. Can you paste me the link ?
We just started using Satellite and encountered this issue. It will take time and lots of tests to update our servers to a newer version of RHEL6.
Maybe we can just update the package(s) that contain the fix ? Is it gofer and/or katello-agent ?
Thanks.
For those wondering, an update of python + python-libs corrects this issue, from the versions that are shipped with RHEL 6.4.
The version of python/python-libs with the fix is:
python-2.6.6-51.el6
python-libs-2.6.6-51.el6
These were shipped with RHEL 6.5 GA, it would appear. Update these packages, restart rsyslog + goferd, notice there will be no messages to stdout.
The changelog that corrected the issue:
* Thu Jul 04 2013 Matej Stuchlik <mstuchli> - 2.6.6-39
- Remove BOM insertion code from SysLogHandler that causes messages to be
treated as EMERG level
Resolves: rhbz#845802
Closing this out.