Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1153677

Summary: jabberd and init script issue
Product: Red Hat Satellite 5 Reporter: DzungDo <ddo>
Component: OtherAssignee: Stephen Herr <sherr>
Status: CLOSED CURRENTRELEASE QA Contact: Dimitar Yordanov <dyordano>
Severity: low Docs Contact:
Priority: medium    
Version: 560CC: cperry, ddevra, dyordano, fabiano.martins, fcami, hmiles, jhutar, jlyle, ksugawar, lnykryn, michele, mmello, mtaru, pdwyer, rvdwees, sherr, tkasparek, vchepkov, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: jabberd-2.2.8-23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-14 15:33:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1127215    

Description DzungDo 2014-10-16 14:06:12 UTC
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 20:37:32 UTC
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 10:26:21 UTC
*** Bug 1153457 has been marked as a duplicate of this bug. ***