search for: sss_cache

...e client 'see' new map entries added to the map on the AD server - I've tries reducing various timeout settings in /etc/sssd/sssd.conf to see if that helps - e.g. entry_cache_timeout = 60 entry_cache_autofs_timeout = 15 but map entries don't appear at all - unless I run 'sss_cache -A' to invalidate the sssd autofs map caches Does anyone know how to make new map entries appear automagically ? Thanks James Pearson

I have a large number of CentOS machines (both 6 & 7) getting account information from an LDAP database using SSSD. It all works fine and is fairly reliable. However, I'm having problems with persuading the caching system to forget about users when they are deleted from LDAP. I know about sss_cache with either -E or -U options, but that doesn't delete anything, just invalidates the cache entry. If the cache is invalid SSS will, obviously, go back to the source and return the information there, however, bizarrely, if the original source doesn't have the information (like when a user i...

...quot; ; time id unknown Server role: ROLE_DOMAIN_MEMBER winbind max domain connections = 1 winbind use default domain = No id: unknown: no such user real 1m8.630s user 0m0.000s sys 0m0.009s [root at centos7dev64 ~]# vi /etc/samba/smb.conf ; systemctl restart winbind ; sss_cache -E [root at centos7dev64 ~]# testparm -v 2>&1 < /dev/null|egrep "(Server role|winbind use default domain|max domain connections)" ; time id unknown Server role: ROLE_DOMAIN_MEMBER winbind max domain connections = 10 winbind use default domain = No id: unknow...

I del user 'u1': # userdel u1 But: # groups u1 u1 : g1 Is 'u1' delete? Thansk

A Samba 4.1.12 member server can not authenticate a user anymore after he changed his password. The AD environment is a duplicated 2012 R2 one. Could this be just a temporary problem caused by the old password in the other AD? Using SSSD for authentication so might have to ask from there... Any hints from here still highly valued. -Tom

...irectory) openat(AT_FDCWD, "/etc/group", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) I figured out that if an empty ldap.conf is placed in /mychroot/etc/ the ls command responds fast, and the access control (based on the LDAP groups) is still working (I made sure to do a sss_cache -E to clear cache between tests) The ldap server is defined in /etc/ldap.conf with a fqdn that is resolved by the DNS server. -- You are receiving this mail because: You are watching the assignee of the bug.

Hello, we are using sssd version 1.12 on openSUSE 13.1 with Sernet-Samba Packages 4.1.11. Samba runs as a single AD DC We have removed the complete openSUSE samba stuff before testing. sssd runs on the same machine as samba. Our sssd config: -------------------------------------------------------------------------------- [sssd] services = nss, pam config_file_version = 2 domains =

...i foo > failed to call wbcGetpwnam: WBC_ERR_WINBIND_NOT_AVAILABLE > Could not get info for user foo > > real 1m1.700s > user 0m0.049s > sys 0m0.010s > [root at centos7dev64 ~]# vi /etc/samba/smb.conf > [root at centos7dev64 ~]# systemctl restart smb winbind sssd ; sss_cache > -E ; net cache flush > [root at centos7dev64 ~]# testparm -v 2>/dev/null </dev/null|grep > "ldap.*timeout" > ldap connection timeout = 2 > ldap timeout = 15 > [root at centos7dev64 ~]# time wbinfo -i foo > failed to call wbcGetpwnam: WBC_ERR...

I know that ID. I had this 70001 too sometime. It was a cache problem. Try "net cache flush" and after this getent once more. This should work. Regards Tim Am 25. Februar 2015 09:45:40 MEZ, schrieb "Herv? H?noch" <h.henoch at isc84.org>: >Both groups are Samba groups > >wbinfo --group-info gives for each group : >GID of domain users is 513 >GID of info is

...[root at centos7dev64 ~]# time wbinfo -i foo failed to call wbcGetpwnam: WBC_ERR_WINBIND_NOT_AVAILABLE Could not get info for user foo real 1m1.700s user 0m0.049s sys 0m0.010s [root at centos7dev64 ~]# vi /etc/samba/smb.conf [root at centos7dev64 ~]# systemctl restart smb winbind sssd ; sss_cache -E ; net cache flush [root at centos7dev64 ~]# testparm -v 2>/dev/null </dev/null|grep "ldap.*timeout" ldap connection timeout = 2 ldap timeout = 15 [root at centos7dev64 ~]# time wbinfo -i foo failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get in...

> On 23 Feb 2019, at 14:52, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sat, 23 Feb 2019 14:21:57 +0100 > Remy Zandwijk via samba <samba at lists.samba.org> wrote: > >> >> >>> On 23 Feb 2019, at 14:07, Rowland Penny via samba >>> <samba at lists.samba.org> wrote: >>> >>> On Sat, 23 Feb 2019

...omain accounts resolve as needed). Bad news the problem is still around and reproducible. I teared down noisy services, so i could generate logs with only wbinfo call hitting winbind for testing. Here my result from command line: [root at centos7dev64 samba]# systemctl restart smb winbind sssd ; sss_cache -E ; net cache flush ; date ; smbcontrol winbind debug 10 ; sleep 60 ; date ; touch start ; wbinfo -i foo ; touch stop ; smbcontrol winbind debug 3 ; date ; sleep 5 ; sync ; cp -a st* log.winbindd* log.wb* BAK/ Thu Feb 28 10:31:52 EST 2019 Thu Feb 28 10:32:52 EST 2019 failed to call wbcGetpwnam...

Am 23.02.19 um 22:23 schrieb Rowland Penny via samba: > On Sat, 23 Feb 2019 21:54:31 +0100 > Alexander Spannagel via samba <samba at lists.samba.org> wrote: > >> Am 23.02.19 um 15:48 schrieb Rowland Penny via samba: >>>>>>>>> If you have, as you have, 'files sss winbind' in the the >>>>>>>>> passwd & group line