search for: idmap_tdb_allocate_id

...nsswitch/winbindd_sid.c:winbindd_sid_to_gid(312) Could not get convert sid from string ==> /var/log/samba/log.winbindd-idmap <== [2008/05/21 00:47:01, 2] nsswitch/idmap.c:idmap_new_mapping(957) gid allocation failed! Can't create mapping [2008/05/21 00:47:01, 1] nsswitch/idmap_tdb.c:idmap_tdb_allocate_id(470) Fatal Error: GID range full!! (max: 20000) [2008/05/21 00:47:01, 2] nsswitch/idmap.c:idmap_new_mapping(957) gid allocation failed! Can't create mapping [2008/05/21 00:47:01, 1] nsswitch/idmap_tdb.c:idmap_tdb_allocate_id(470) Fatal Error: GID range full!! (max: 20000) [2008/05/21 00:4...

...oc module tdb already registered! [2009/11/10 10:51:14, 0] winbindd/idmap.c:149(smb_register_idmap) Idmap module passdb already registered! [2009/11/10 10:51:14, 0] winbindd/idmap.c:149(smb_register_idmap) Idmap module nss already registered! [2009/11/10 10:51:14, 1] winbindd/idmap_tdb.c:445(idmap_tdb_allocate_id) Fatal Error: GID range full!! (max: 499999) [2009/11/10 10:52:06, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module ldap already registered! [2009/11/10 10:52:06, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module tdb already registered! [2009/11/10 10:...

...l users are unable to access shared folders because the idmap GID range became full!! What I noticed is that each time a user mounts a shared folder, his/her GID is incremented, and when it reaches the upper limit, the file log.winbindd-idmap became full of these errors: "nsswitch/idmap_tdb.c:idmap_tdb_allocate_id(470) Fatal Error: GID range full!! (max: 20000)" Can anyone kindly suggest me what is causing this behavior, or at least put me in the right direction? Can I activate some debug to obtain more info about this? Any help will be greatly appreciated: I convinced the customer to use Mac/BSD/Sam...

...oday I have a weird error message while I am trying to join another fileserver. Error message is the following : # tail -f /var/log/samba/log.winbindd-idmap [2010/07/16 13:26:02, 1] winbindd/idmap.c:idmap_init(385) Initializing idmap domains [2010/07/16 13:27:47, 1] winbindd/idmap_tdb.c:idmap_tdb_allocate_id(444) Fatal Error: GID range full!! (max: 5000000) [2010/07/16 13:41:26, 1] winbindd/idmap.c:idmap_init(385) Initializing idmap domains [2010/07/16 13:41:26, 1] winbindd/idmap_tdb.c:idmap_tdb_allocate_id(444) Fatal Error: GID range full!! (max: 5000000) To bypass that error, I incre...

...the following error in '/var/log/samba': [2011/12/30 09:33:08.072315, 1] smbd/sesssetup.c:454(reply_spnego_kerberos) Username GALILEU-F\teste is invalid on this system Also, in 'winbind-idmap' log file I am getting this: [2011/12/30 09:32:56.902810, 1] winbindd/idmap_tdb.c:445(idmap_tdb_allocate_id) Fatal Error: UID range full!! (max: 120000) So what happens in reality? Trying to 'getent' that user results in nothing, so no mapping, right? root at sputnik:/var/cache/samba# getent passwd bmartins bmartins:*:100001:100000::/home/GALILEU-F/bmartins:/bin/false root at sputnik:/var/cach...

Just upgraded a RedHat 4.5 system to 4.6, including Samba Version 3.0.25b-1.el4_6.2 Smbd starts, but denies all access. winbindd-idmap.log shows this error message: [2007/11/19 10:37:06, 1] nsswitch/idmap_tdb.c:idmap_tdb_allocate_id(470) Fatal Error: GID range full!! (max: 20000) Individual PC log file shows: check_ntlm_password: Authentication for user [chughes] -> [chughes] FAILED with error NT_STATUS_UNSUCCESSFUL Where to look? -- Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court UNIX System Admin Consulting...

When trying to get a listing of print jobs waiting on a windows print queue nothing is being returned. Any windows client can pull the job list without issue. This system has no problem sending print jobs to the queue. AIX 5.3 running Samba 3.5.2 connecting to Windows 2003 /opt/pware64/bin/smbclient "\\\\SERVERNAME\\PRINTER" -U domainAdmin -c "queue" /opt/pware64/bin/net