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.
Bug 1001153 - sssd service could not be started
Summary: sssd service could not be started
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: ppc64
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-26 14:52 UTC by David Spurek
Modified: 2020-05-02 17:26 UTC (History)
8 users (show)

Fixed In Version: sssd-1.11.0-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:41:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3099 0 None None None 2020-05-02 17:26:29 UTC

Description David Spurek 2013-08-26 14:52:35 UTC
Description of problem:
sssd service could not be started on big endian architectures

Version-Release number of selected component (if applicable):
sssd-1.11.0-0.1.beta2.el7

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
sssd service could not be started

Expected results:
sssd service could be started 

Additional info:

Comment 1 Jakub Hrozek 2013-08-26 15:02:16 UTC
This is caused by a bad DBus message construction. We use the standard C bool type which is 1 byte wide and DBus expects 4 bytes.

Comment 2 Jakub Hrozek 2013-08-26 15:04:48 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2057

Comment 3 Jakub Hrozek 2013-08-29 16:36:06 UTC
Fixed upstream in 1.11.0

Comment 6 Jakub Hrozek 2013-10-04 13:23:51 UTC
Temporarily moving bugs to MODIFIED to work around errata tool bug

Comment 8 Amith 2013-11-15 13:08:29 UTC
Verified the bug on SSSD version: sssd-1.11.2-1.el7.s390x and sssd-1.11.2-1.el7.ppc64

Successfully installed and started sssd service on both arch's. See the sssd service status from both the systems:

-------------------------------------------------------
HOSTNAME=ibm-ps701-01-lp3.rhts.eng.bos.redhat.com
DISTRO=RHEL-7.0-20131107.1
ARCHITECTURE=ppc64

[root@ibm-ps701-01-lp3 ~]# systemctl start sssd.service
[root@ibm-ps701-01-lp3 ~]# 
[root@ibm-ps701-01-lp3 ~]# systemctl status sssd.service
sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
   Active: active (running) since Fri 2013-11-15 07:40:38 EST; 13s ago
  Process: 9562 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
 Main PID: 9563 (sssd)
   CGroup: /system.slice/sssd.service
           ├─9563 /usr/sbin/sssd -D -f
           ├─9564 /usr/libexec/sssd/sssd_be --domain LDAP --debug-to-files
           ├─9565 /usr/libexec/sssd/sssd_nss --debug-to-files
           └─9566 /usr/libexec/sssd/sssd_pam --debug-to-files

---------------------------------------------------------------------
HOSTNAME=ibm-z10-29.rhts.eng.bos.redhat.com
DISTRO=RHEL-7.0-20131113.n.0
ARCHITECTURE=s390x

[root@ibm-z10-29 ~]# service sssd status
Redirecting to /bin/systemctl status  sssd.service
sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
   Active: active (running) since Thu 2013-11-14 08:32:09 EST; 23h ago
  Process: 26043 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
 Main PID: 26044 (sssd)
   CGroup: /system.slice/sssd.service
           ├─26044 /usr/sbin/sssd -D -f
           ├─26045 /usr/libexec/sssd/sssd_be --domain LDAP --debug-to-files
           ├─26046 /usr/libexec/sssd/sssd_nss --debug-to-files
           └─26047 /usr/libexec/sssd/sssd_pam --debug-to-files

Comment 9 Ludek Smid 2014-06-13 11:41:52 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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