Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-9445: Centrify_client log is not being populated on SUSE 12 SP2

Authentication Service ,  

11 December,17 at 10:58 PM

Problem: After turning on addebug, it does not generate any logs at all, centrify_client.log has size of zero. 

rwww 1 root root 0 Sep 18 10:42 centrify_client.log
rw------ 1 root root 30 Sep 18 10:36 centrify_mapper_error.log
rw-rr- 1 root root 506 May 25 14:06 centrifycc-install.log
rw-rr- 1 root root 7432 Sep 18 10:05 centrifydc-install.log
rw------ 1 root root 3150 Sep 18 10:43 centrifydc.log
drwxr-xr-x 1 lp lp 0 Jun 7 2016 cups

Cause: The issue with centrify_client.log is that it is updated by LRPC2 clients only (e.g. Centrify PAM/NSS modules).

Workaround: It works after restarting the adclient process.

Resolution:  This issue will be fixed in the Suite 2017.3 release.





 

Related Articles

 articleKB-9716: addebug does not work on SUSE 12 SP2 articleCentrify 21.2 Release Notes articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleCentrify 20.7 Release Notes articleCentrify 21.1 Release Notes articleCentrify 20.4 Release Notes articleCentrify 20.5 Release Notes articleCentrify 20.6 Release Notes articleCentrify 20.3 Release Notes