similar to: Error log assistance with log.winbind

Displaying 20 results from an estimated 600 matches similar to: "Error log assistance with log.winbind"

2007 Jun 27
1
rfc2307 - 3.0.24
I'm running samba 3.0.24 (the latest package that seems to be available for Ubuntu 7). I have a Windows 2003 AD with the R2/RFC2307 schema loaded. I would prefer to use the 3.0.24 package if possible unless there is an ubuntu package for 3.0.25. Any suggestions would be appreciated. Wbinfo -u and -g appear to work great. Net ads testjoin comes back successful. In log.winbindd-idmap I get
2006 Aug 25
0
Attempt to configure idmap_ad giving error on uidNumber
My long sojourn to get some configuration set up that will then allow me to set a uid of an ad user to whatever unix uid I want (nfs reasons), is still going. I set my backend to ad and added the winbind nss info = sfu. Nothing happened initially in the log.winbindd-idmap, but after lunch I saw some new things in there: 83390]: sid to uid S-1-5-21-54348060-1989963526-242692186-2762 [2006/08/25
2007 Oct 05
1
Fwd: could not read attribute 'gidNumber' --> seems to work with ldapsearch
If I run a normal ldapsearch it gives me the gidnumber and uidnumber attributes. It looks like the AD is set up properly. ---------- Forwarded message ---------- From: Urs Golla <urs.golla@gmail.com> Date: Oct 4, 2007 9:47 AM Subject: could not read attribute 'gidNumber' To: samba@lists.samba.org Hi I am using samba 3.0.23c on RHEL5 with security = ads. If I use "idmap
2005 Oct 31
1
Not all users correctly winbind-ing on Server 2003 SP1 with 3.0.20b
Hi all This one has me baffled - leading me to beleive it could be a bug similar to https://bugzilla.samba.org/show_bug.cgi?id=2695 I am running samba 3.0.20b on debian unstable and am having problems with some users not resolving properly using winbind. wbinfo -u shows all users on the system, no problem wbinfo -a user%password works for any user getent passwd shows most but not all users
2004 Nov 03
0
Idmap_ad troubleshooting assistance
I have Samba 3.0.7 installed and running in security = ADS mode and I've built and installed the Idmap_ad backend according to the instructions. Group lookups seem to work fine, but getent passwd and id functions fail with the message - ad_idmap_get_id_from_sid: ads_pull_uint32 : could not read attribute 'gidNumber'. If I manually run an ldap query against Active Directory the
2005 Mar 04
0
Winbind Daemon dying
Samba 3.0.11 on SLES8 on z/VM The system will be running fine then every few days the Winbind daemon will stop. Below are the last lines of the log file. [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475) rid_idmap_get_id_from_sid: no suitable range available for sid: S-1-5-32-545 [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475)
2006 Jul 18
1
Problem with 3.0.23 upgrade from 3.0.22 with rfc2307 patch
I have upgraded one of my servers from a 3.0.22 implementation using the rfc2307 patch I supplied some months ago to the 3.0.23 release. I am now getting some unexplaned failures and would like some pointers as to where to start looking. I am getting the following logged in the samba logs when trying to start the servers. zebra.log: Sid S-1-5-32-544 -> BUILTIN\Administrators(4)
2006 Oct 20
2
could not read attribute 'msSFU30UidNumber'
Hi, I'm using samba 3.0.23c, and having a bit of trouble getting it to play nice with my active directory. I'm using Windows Small Business Server 2003 with the SFU 3.5 NIS server/schema extensions installed. I have samba configured to use ad as the idmap backend, and sfu for nss info. When running getent passwd, only a few active directory users show up, and I get lots of errors
2006 Jan 18
3
Bootable Floppy w/ Networking & Shell?
I realize this is probably the wrong list but since some of the principals this list deals with are similar in nature I figured it could't hurt. What I am looking to do: Provide a solution to either boot from a floppy disk, establish a network connection, give user the ability to run utilities such as fdisk and dd. as well as provide the same solution as a PXE bootable image. My
2002 Aug 03
0
Samba 2.2.5 under Debian 3.0 i386: Still frequent connections.tdb corruption
[CC to Debian package maintainer] Hi there, I'm still experiencing this worrysome tdb corruption even after I upgraded to 2.2.5. I built this package myself from the officially released 2.2.5 source. Here's a log snippet: Aug 3 11:15:04 Server smbd[23307]: [2002/08/03 11:15:04, 0] tdb/tdbutil.c:tdb_log(492) Aug 3 11:15:04 Server smbd[23307]: tdb(/var/run/samba/connections.tdb):
2002 Aug 07
2
REPOST: Samba 2.2.5 under Debian 3.0 i386: Still frequent connections.tdb corruption
Hi there, isn't there really anybody who can give hints about this problem? Thanks, Ralf ==================BEGIN FORWARDED MESSAGE================== >From: "Ralf G. R. Bergs" <rabe@RWTH-Aachen.DE> >To: "samba@lists.samba.org" <samba@lists.samba.org> >Cc: "Eloy A. Paris" <peloy@debian.org> >Date: Sat, 03 Aug 2002 12:19:24 +0200
2004 May 19
0
Printing problem with CUPS / Samba
Hello everyone! We're using samba-3.0.2rc2 with OpenLDAP-2.1.27, cupsys-1.1.20final-cvs200403 and a Samsung printer. Printing was working fine but yesterday all of a sudden it stopped working. The error message on the windows machine was: "A StartDocPrinter call was not issued". On viewing samba logs for the machine, we got following error:
2002 Dec 08
1
Sudden Bug
High I'm using samba in my private network since 1 year. Since yesterday I fi nd the mesg in the appendix when I trie to print. File transfer works fine, you find all printers but its not possible to print anything. Where to search ? Thanks a lot Bernd -------------- next part -------------- [1995/12/08 12:52:10, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/lib/samba/printing.tdb):
2004 Feb 13
0
Windbind_idmap.tdb problems
----- Forwarded by Nic le Roux/rohlig-grindrod on 2004/02/13 03:42 PM ----- Hi All, I discovered something to be wrong with the file winbind_idmap.tdb. Receive lots of messages saying: Feb 13 15:15:59 rh9printsvr winbindd[4201]: tdb(/var/lib/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=119904 Feb 13 15:15:59 rh9printsvr winbindd[4201]: [2004/02/13 15:15:59, 0]
2006 Jan 30
2
Windows print queue not clearing: Part II
Sorry for the addendum, but I've also noticed the following entries in the logs: Jan 30 12:28:38 primary smbd[2577]: tdb(/var/cache/samba/printing/claser_3.tdb): rec_read bad magic 0x0 at offset=21904 Jan 30 12:28:38 primary smbd[2577]: [2006/01/30 12:28:38, 0] tdb/tdbutil.c:tdb_log(725) Jan 30 12:28:38 primary smbd[2577]: tdb(/var/cache/samba/printing/copier_4.tdb): rec_read bad magic
2007 May 07
3
Countless "rec_read bad magic" lines in log.smbd
One of the servers we admin has countless such errors in log.smbd: [2007/05/07 14:17:08, 0] tdb/tdbutil.c:tdb_log(783) tdb(/var/cache/samba/printing/HPLJ3600.tdb): rec_read bad magic 0x443810ec at offset=28412 The only thread I saw regarding "rec_read" stated: <><><><><> If this really happens often to you, then you have some basic problems with your
2006 Apr 21
1
AW: getent not working (again)
I don't think that this is my problem. When I try 'getent passwd <user>' I get no output either. And we only store about 200 users. Is bug 3024 fixed in the newest version? I will try to apply the patch. J?rg -----Urspr?ngliche Nachricht----- Von: Gautier, B (Bob) [mailto:Bob.Gautier@rabobank.com] Gesendet: Freitag, 21. April 2006 12:54 An: Horchler, Joerg;
2006 Apr 21
2
getent not working (again)
Hi all, after I searched the internet about a week now I can't find an answer to my problem: The company I work for is using a Windows 2003 Domain using the Windows Services for UNIX (SFU) and NIS. We are using two Domain Controllers that are hosting the ADS. Now I want to use Samba and NFS to implement a file server for our mixed client enviroment: There will be Linux, HP UNIX, Solaris,
2005 Dec 04
0
AD4Unix & Samba-3.0.20b+winbind (UPDATE)
The nss_ldap has some performance problems and doesn't have any caching features that windbind does. What I was aways wondering is does IDMAP write UID/GID derived from SID to the extended schema in AD? Can winbindd use this extended schema, instead of using nss_ldap? -----Original Message----- From: samba-bounces+letz_samba=realmspace.com@lists.samba.org
2018 May 01
1
cannot compile 4-8-stable or 4-8-test
Samba from git (4-8-stable and 4-8-test) is failing to compile. I did not have these issues with the previous 4-7 branches. Basically this installation is just a simple file server, no domain, ad, print service, etc. necessary or even desired. My configure arguments: $ ./configure --without-winbind --disable-avahi --without-ads --without-ldap --without-pam --without-quotas --without-dnsupdate