Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1153677 - jabberd and init script issue
jabberd and init script issue
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
560
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Stephen Herr
Dimitar Yordanov
:
: 1153457 (view as bug list)
Depends On:
Blocks: sat570-blockers
  Show dependency treegraph
 
Reported: 2014-10-16 10:06 EDT by DzungDo
Modified: 2015-09-21 14:06 EDT (History)
19 users (show)

See Also:
Fixed In Version: jabberd-2.2.8-23
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-01-14 10:33:27 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1237023 None None None Never

  None (edit)
Description DzungDo 2014-10-16 10:06:12 EDT
Description of problem:
New RHEL 6.6 updates initscripts to initscripts-9.03.40-2.el6_5.2.x86_64.

After update, jabberd start/restart returned the following message:

Starting sm: /usr/bin/dirname: extra operand `2>&1'
Try `/usr/bin/dirname --help' for more information.

Version-Release number of selected component (if applicable):
5.6

How reproducible:
Always

Steps to Reproduce:
1. yum update initscripts (to update initscripts to 9.03.40-2.el6_5.2)
2. rhn-satellite restart (or service jabberd restart)
3. To remove the message, run "yum downgrade initscripts-9.03.40-2.el6_5.2.x86_64", and then "service jabberd restart"

Actual results:


Expected results:


Additional info:
Comment 7 Stephen Herr 2014-11-04 15:37:32 EST
For the record, please note that this is only a cosmetic issue when running with the new RHEL 6 initscripts-9.03.46-1.el6_6.1

There is no impact on the operation of Satellite.
Comment 9 Clifford Perry 2014-11-06 05:26:21 EST
*** Bug 1153457 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.