Unix: When AD authorization is not working

 [root@db2tst601 ~]# systemctl status sssd

● sssd.service - System Security Services Daemon

   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Tue 2025-07-15 17:30:04 CDT; 2h 22min ago

  Process: 49817 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=1/FAILURE)

 Main PID: 49817 (code=exited, status=1/FAILURE)


Jul 15 17:28:26 db2tst601 sssd_nss[1663851]: Starting up

Jul 15 17:28:27 db2tst601 sssd[49817]: Child [49890] ('TMW.COM':'%BE_TMW.COM') was terminated by own WATCHDOG. Consult corresponding logs to figure out the reason.

Jul 15 17:28:27 db2tst601 sssd_be[1664041]: Starting up

Jul 15 17:28:29 db2tst601 sssd_nss[1664043]: Starting up

Jul 15 17:28:33 db2tst601 sssd[49817]: Exiting the SSSD. Could not restart critical service [nss].

Jul 15 17:29:42 db2tst601 sssd_be[1664041]: Shutting down (status = 0)

Jul 15 17:29:43 db2tst601 sssd_pam[857047]: Shutting down (status = 0)

Jul 15 17:29:45 db2tst601 sssd_pac[50031]: Shutting down (status = 0)

Jul 15 17:30:04 db2tst601 systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE

Jul 15 17:30:04 db2tst601 systemd[1]: sssd.service: Failed with result 'exit-code'.


[root@db2tst601 ~]# systemctl start sssd



[root@db2tst601 ~]# systemctl status sssd

● sssd.service - System Security Services Daemon

   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled)

   Active: active (running) since Tue 2025-07-15 19:52:59 CDT; 4s ago

 Main PID: 2684126 (sssd)

    Tasks: 6 (limit: 615049)

   Memory: 178.7M

   CGroup: /system.slice/sssd.service

           ├─2684126 /usr/sbin/sssd -i --logger=files

           ├─2684127 /usr/libexec/sssd/sssd_be --domain TMW.COM --uid 0 --gid 0 --logger=files

           ├─2684129 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files

           ├─2684130 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files

           ├─2684131 /usr/libexec/sssd/sssd_pac --uid 0 --gid 0 --logger=files

           └─2684632 /usr/libexec/sssd/krb5_child --dumpable=1 --debug-microseconds=0 --debug-timestamps=1 --debug-fd=32 --debug-level=0x0010 --chain-id=25 --sss-creds-password --canonicalize --check-pac=42 --realm=TMW.COM -->


Jul 15 19:52:55 db2tst601 systemd[1]: Starting System Security Services Daemon...

Jul 15 19:52:56 db2tst601 sssd[2684126]: Starting up

Jul 15 19:52:57 db2tst601 sssd_be[2684127]: Starting up

Jul 15 19:52:59 db2tst601 sssd_pac[2684131]: Starting up

Jul 15 19:52:59 db2tst601 sssd_nss[2684129]: Starting up

Jul 15 19:52:59 db2tst601 sssd_pam[2684130]: Starting up

Jul 15 19:52:59 db2tst601 systemd[1]: Started System Security Services Daemon.


Comments

Post a Comment

Popular posts from this blog

Oracle: To clean up WRI$_ADV_OBJECTS

 set linesize 200; select segment_name, segment_type, bytes from dba_segments where tablespace_name='SYSAUX' order by bytes asc; COL OCCUPANT_NAME FORMAT A30 SELECT OCCUPANT_NAME,SPACE_USAGE_KBYTES FROM V$SYSAUX_OCCUPANTS ORDER BY SPACE_USAGE_KBYTES DESC; COL SEGMENT_NAME FORMAT A30 COL OWNER FORMAT A10 COL TABLESPACE_NAME FORMAT A10 COL SEGMENT_TYPE FORMAT A15 SELECT * FROM (SELECT SEGMENT_NAME,OWNER,TABLESPACE_NAME,BYTES/1024/1024 "SIZE(MB)",SEGMENT_TYPE FROM DBA_SEGMENTS WHERE TABLESPACE_NAME='SYSAUX' ORDER BY BYTES DESC) WHERE ROWNUM<=10; 1.  automatic clean-up default 31 days           SELECT dbms_stats.get_stats_history_availability from Dual; 2. modify retention policy        exec  dbms_stats.alter_stats_history_retention (14); 3. a manual cleaning  exec dbms_stats.purge_stats (sysdate-14);   ALTER TABLE WRI$_ADV_OBJECTS MOVE; ALTER INDEX WRI$_ADV_OBJECTS_IDX_01 REBUILD; ALTER INDEX WRI$_ADV_OBJECTS_IDX_02 R...
Read more