Results 1 to 6 of 6

Thread: sssd does not start due to module version missmatch

  1. #1

    Default sssd does not start due to module version missmatch

    I hope anyone can help with that. I am locked out of my user account that is managed by sssd because sssd seems to be broken after a system update. This is what journalctrl is reporting

    Code:
    Apr 06 14:08:05 CLIENT04 systemd[1]: Starting System Security Services Daemon...
    Apr 06 14:08:05 CLIENT04 sssd[4594]: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.4 module_version=1.2.3
    Apr 06 14:08:05 CLIENT04 sssd[4594]: ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable
    Apr 06 14:08:05 CLIENT04 sssd[4594]: ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable
    Apr 06 14:08:05 CLIENT04 sssd[4594]: SSSD couldn't load the configuration database [5]: Input/output error.
    Apr 06 14:08:05 CLIENT04 systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
    Apr 06 14:08:05 CLIENT04 systemd[1]: Failed to start System Security Services Daemon.
    Apr 06 14:08:05 CLIENT04 systemd[1]: sssd.service: Unit entered failed state.
    Apr 06 14:08:05 CLIENT04 systemd[1]: sssd.service: Failed with result 'exit-code'.
    Yast says "1.2.3-lp150.7.2" is installed. However in the system I find

    Code:
     ll /usr/lib64/libldb.so.1*
    lrwxrwxrwx 1 root root     15 Mar 28 13:22 /usr/lib64/libldb.so.1 -> libldb.so.1.2.4
    -rwxr-xr-x 1 root root 200768 Mar 28 13:22 /usr/lib64/libldb.so.1.2.4
    Any clue how to fix this? A quick help is highly appreciated.

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,979

    Default AW: sssd does not start due to module version missmatch


  3. #3

    Default Re: sssd does not start due to module version missmatch

    Hm, great. I am not alone. Looks like someone in packaging made a lot of friends today Thanks for the hint. I will follow the ticket closely.

  4. #4

    Default Re: sssd does not start due to module version missmatch

    Just a quick update for everyone encountering that issue, the fix has been released last week.

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,293
    Blog Entries
    2

    Default Re: sssd does not start due to module version missmatch

    So,
    It sounds like the fix should be that the User should login as root if User credentials don't work (Yeah, this breaks the rule against logging in as root, but this would be a special case and only as long as it takes to fix the problem).

    Once logged in, open a terminal/console and run the following
    Code:
    zypper update
    Or, if the above doesn't include an sssd updated package, then
    Code:
    zypper dup
    After which you should be able to reboot and login as your normal User.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #6

    Default Re: sssd does not start due to module version missmatch

    Hi:

    I fix the problem deleting symlink "/usr/lib64/ldb/samba" and restaring sssd

    Quote Originally Posted by kiozen View Post
    I hope anyone can help with that. I am locked out of my user account that is managed by sssd because sssd seems to be broken after a system update. This is what journalctrl is reporting

    Code:
    Apr 06 14:08:05 CLIENT04 systemd[1]: Starting System Security Services Daemon...
    Apr 06 14:08:05 CLIENT04 sssd[4594]: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.4 module_version=1.2.3
    Apr 06 14:08:05 CLIENT04 sssd[4594]: ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable
    Apr 06 14:08:05 CLIENT04 sssd[4594]: ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable
    Apr 06 14:08:05 CLIENT04 sssd[4594]: SSSD couldn't load the configuration database [5]: Input/output error.
    Apr 06 14:08:05 CLIENT04 systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
    Apr 06 14:08:05 CLIENT04 systemd[1]: Failed to start System Security Services Daemon.
    Apr 06 14:08:05 CLIENT04 systemd[1]: sssd.service: Unit entered failed state.
    Apr 06 14:08:05 CLIENT04 systemd[1]: sssd.service: Failed with result 'exit-code'.
    Yast says "1.2.3-lp150.7.2" is installed. However in the system I find

    Code:
     ll /usr/lib64/libldb.so.1*
    lrwxrwxrwx 1 root root     15 Mar 28 13:22 /usr/lib64/libldb.so.1 -> libldb.so.1.2.4
    -rwxr-xr-x 1 root root 200768 Mar 28 13:22 /usr/lib64/libldb.so.1.2.4
    Any clue how to fix this? A quick help is highly appreciated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •