Unix: Centrify status and restart

 [root@db2tst601 etc]# systemctl status sssd.service

● sssd.service - System Security Services Daemon

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

   Active: failed (Result: exit-code) since Fri 2025-05-16 00:31:55 CDT; 4h 0min ago

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

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


May 16 00:31:12 db2tst601 sssd[53976]: Child [54045] ('TMW.COM':'%BE_TMW.COM') was terminated by own WATCHDOG. Consult corresponding logs to figure out the reason.

May 16 00:31:13 db2tst601 sssd_be[1001039]: Starting up

May 16 00:31:14 db2tst601 sssd_nss[1001041]: Starting up

May 16 00:31:18 db2tst601 sssd_nss[1001077]: Starting up

May 16 00:31:18 db2tst601 sssd[53976]: Exiting the SSSD. Could not restart critical service [nss].

May 16 00:31:42 db2tst601 sssd_be[1001039]: Shutting down (status = 0)

May 16 00:31:43 db2tst601 sssd_pam[2311680]: Shutting down (status = 0)

May 16 00:31:45 db2tst601 sssd_pac[54173]: Shutting down (status = 0)

May 16 00:31:55 db2tst601 systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE

May 16 00:31:55 db2tst601 systemd[1]: sssd.service: Failed with result 'exit-code'.

[root@db2tst601 etc]#




[root@db2tst601 etc]# systemctl status sssd.service

● sssd.service - System Security Services Daemon

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

   Active: active (running) since Fri 2025-05-16 04:33:20 CDT; 4s ago

 Main PID: 2653835 (sssd)

    Tasks: 5 (limit: 615049)

   Memory: 174.9M

   CGroup: /system.slice/sssd.service

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

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

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

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

           └─2653846 /usr/libexec/sssd/sssd_pac --uid 0 --gid 0 --logger=files


May 16 04:33:17 db2tst601 systemd[1]: Starting System Security Services Daemon...

May 16 04:33:18 db2tst601 sssd[2653835]: Starting up

May 16 04:33:19 db2tst601 sssd_be[2653843]: Starting up

May 16 04:33:20 db2tst601 sssd_pac[2653846]: Starting up

May 16 04:33:20 db2tst601 sssd_pam[2653845]: Starting up

May 16 04:33:20 db2tst601 sssd_nss[2653844]: Starting up

May 16 04:33:20 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