Bug 1965818 - libldb: LANG=tr_TR.UTF-8 make test - fails (sssd - failing on "dotted"languages (Example turkish language))
Summary: libldb: LANG=tr_TR.UTF-8 make test - fails (sssd - failing on "dotted"languag...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libldb
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-30 12:55 UTC by Onuralp SEZER
Modified: 2023-01-20 21:48 UTC (History)
18 users (show)

Fixed In Version: libldb-2.7.0-2.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-20 21:48:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab samba-team samba merge_requests 2804 0 None closed lib:ldb: Fix case folding for dotted languages 2023-01-02 22:26:04 UTC
Red Hat Issue Tracker SSSD-3537 0 None None None 2022-02-03 13:17:25 UTC

Description Onuralp SEZER 2021-05-30 12:55:10 UTC
Description of problem:

Hello,

SSSD Service isn't starting If we use dotted language in our system. For example, adding "LANG=tr_TR" into "/etc/sysconfig/sssd" makes sssd fails on start. If anyone install Fedora with "turkish" or other dotted language in their pc/laptop, that makes sssd fails on start. 

After I made little bit research, I notice this issue has been addressed multiple times around RHEL[0] and samba[1] and github[2] as well. So for that reason at least can we add "english" locale setting into rpm spec with "language" check as a workaround has been suggest in github link.That is at least gives us "working" package in dotted languge, and If anyone wants change setting, they can change it. At least for normal users, we can have working sssd service and not complain about fails all the times. I know this isn't the cleanest solution (proper solution is patching libldb package which causing this issue, but at least we can have a "quick&dirty" solution avoid on new installs. 

Thank you. 


[0] : https://bugzilla.redhat.com/show_bug.cgi?id=1743531
[1] : https://lists.samba.org/archive/samba-technical/2019-December/134659.html
[2] : https://github.com/SSSD/sssd/issues/5285




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

sssd-2.5.0-2.fc34.x86_64
libldb-2.3.0-2.fc34.x86_64


How reproducible:
Steps to Reproduce:
1. Install Fedora or change language into dotted or change "LANG" env into dotted langauge
2. reset sssd counter 
3. start sssd

Actual results:
sssd fails

Expected results:
sssd should start clean in default config.

Additional info:

SSSD Systemctl errors

 systemd[1]: Starting System Security Services Daemon...
 sssd[760632]: Starting up
 systemd[1]: sssd.service: Main process exited, 
code=exited, status=4/NOPERMISSION
 systemd[1]: sssd.service: Failed with result 
'exit-code'.
 systemd[1]: Failed to start System Security Services 
Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
 systemd[1]: sssd.service: Scheduled restart job, 
restart counter is at 1.
 systemd[1]: Stopped System Security Services Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 systemd[1]: Starting System Security Services Daemon...
 sssd[760633]: Starting up
 systemd[1]: sssd.service: Main process exited, 
code=exited, status=4/NOPERMISSION
 systemd[1]: sssd.service: Failed with result 
'exit-code'.
 systemd[1]: Failed to start System Security Services 
Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
 systemd[1]: sssd.service: Scheduled restart job, 
restart counter is at 2.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 systemd[1]: Stopped System Security Services Daemon.
 systemd[1]: Starting System Security Services Daemon...
 sssd[760636]: Starting up
 systemd[1]: sssd.service: Main process exited, 
code=exited, status=4/NOPERMISSION
 systemd[1]: sssd.service: Failed with result 
'exit-code'.
 systemd[1]: Failed to start System Security Services 
Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
 systemd[1]: sssd.service: Scheduled restart job, 
restart counter is at 3.
 systemd[1]: Stopped System Security Services Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 systemd[1]: Starting System Security Services Daemon...
 sssd[760637]: Starting up
 systemd[1]: sssd.service: Main process exited, 
code=exited, status=4/NOPERMISSION
 systemd[1]: sssd.service: Failed with result 
'exit-code'.
 systemd[1]: Failed to start System Security Services 
Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
 systemd[1]: sssd.service: Scheduled restart job, 
restart counter is at 4.
 systemd[1]: Stopped System Security Services Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 systemd[1]: Starting System Security Services Daemon...
 sssd[760639]: Starting up
 systemd[1]: sssd.service: Main process exited, 
code=exited, status=4/NOPERMISSION
 systemd[1]: sssd.service: Failed with result 
'exit-code'.
 systemd[1]: Failed to start System Security Services 
Daemon.
 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

-----------

/var/log/sssd/sssd.log (last error with LANG setting is tr_TR (LANG=tr_TR) )

-----------

********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING 
BACKTRACE:
   *  (2021-05-30 15:46:52): [sssd] [check_file] (0x0400): lstat for 
[/run/sssd.pid] failed: [2][No such file or directory].
   *  (2021-05-30 15:46:52): [sssd] [check_file] (0x0400): lstat for 
[/var/run/nscd/socket] failed: [2][No such file or directory].
   *  (2021-05-30 15:46:52): [sssd] [ldb] (0x0400): server_sort:Unable to 
register control with rootdse!
   *  (2021-05-30 15:46:52): [sssd] [sss_ini_open] (0x0400): No 
/etc/sssd/sssd.conf.
   *  (2021-05-30 15:46:52): [sssd] [sss_ini_read_sssd_conf] (0x0100): File 
/etc/sssd/sssd.conf does not exist.
   *  (2021-05-30 15:46:52): [sssd] [confdb_ldif_from_ini_file] (0x0100): Value 
of config_file_version option not found. Assumed to be version 2.
   *  (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x0400): 
Processing config section [sssd]
   *  (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x0400): 
Processing attribute [services]
   *  (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x4000): services: 
nss

   *  (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x4000): Section 
dn
dn: cn=sssd,cn=config
cn: sssd
services: nss


   *  (2021-05-30 15:46:52): [sssd] [confdb_init_db] (0x0100): LDIF file to 
import:
dn: cn=config
version: 2

dn: cn=sssd,cn=config
cn: sssd
services: nss


   *  (2021-05-30 15:46:52): [sssd] [add_implicit_services] (0x0040): No domains 
configured!
   *  (2021-05-30 15:46:52): [sssd] [get_monitor_config] (0x0040): Failed to add 
implicit configured services. Some functionality might be missing
   *  (2021-05-30 15:46:53): [sssd] [confdb_expand_app_domains] (0x2000): 
implicit_files is not an app domain
   *  (2021-05-30 15:46:53): [sssd] [confdb_get_domain_internal] (0x0400): No 
enumeration for [implicit_files]!
   *  (2021-05-30 15:46:53): [sssd] [confdb_get_domain_internal] (0x0400): 
Please note that when enumeration is disabled `getent passwd` does not return 
all users by design. See sssd.conf man page for more detailed information
   *  (2021-05-30 15:46:53): [sssd] [confdb_get_domain_internal] (0x1000): 
pwd_expiration_warning is -1
   *  (2021-05-30 15:46:53): [sssd] [server_setup] (0x0080): Failed setting 
process group: Operation not permitted[1]. We might leak processes in case of 
failure
   *  (2021-05-30 15:46:53): [sssd] [become_user] (0x0200): Trying to become 
user [0][0].
   *  (2021-05-30 15:46:53): [sssd] [become_user] (0x0200): Already user [0].
   *  (2021-05-30 15:46:53): [sssd] [ldb] (0x0400): server_sort:Unable to 
register control with rootdse!
   *  (2021-05-30 15:46:53): [sssd] [server_setup] (0x0400): CONFDB: 
/var/lib/sss/db/config.ldb
   *  (2021-05-30 15:46:53): [sssd] [confdb_get_enabled_domain_list] (0x0040): 
Failed to get [domains] from [sssd], error [2] (Böyle bir dosya ya da dizin yok)
********************** BACKTRACE DUMP ENDS HERE 
*********************************

(2021-05-30 15:46:53): [sssd] [main] (0x0010): No domains configured.
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING 
BACKTRACE:
   *  (2021-05-30 15:46:53): [sssd] [confdb_get_domains] (0x0080): No domains 
configured, fatal error!
   *  (2021-05-30 15:46:53): [sssd] [main] (0x0010): No domains configured.
********************** BACKTRACE DUMP ENDS HERE 
*********************************

Comment 1 Alexey Tikhonov 2022-02-22 13:48:14 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1743531#c15

Comment 2 Ben Cotton 2022-08-09 13:37:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 3 Andreas Schneider 2022-11-24 13:38:42 UTC
https://gitlab.com/samba-team/samba/-/merge_requests/2804

Comment 4 Fedora Update System 2023-01-20 17:37:30 UTC
FEDORA-2023-39bd85a8ed has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-39bd85a8ed

Comment 5 Fedora Update System 2023-01-20 21:48:56 UTC
FEDORA-2023-39bd85a8ed has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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