similar to: Sudden Bug

Suddenly, today, my wife's Windows 95 machine can't print to the network printer on my Linux machine. It complains that "there was an error printing to \\posh\lp ... There was a problem printing to the port." The error 1st occurred (coincidentally?) after I had upgraded the kernel from 2.4.18 to 2.4.19. But rebooting to 2.4.18 has made no difference. We're running smbd

[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):

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

Can't print from client computers: I tailed the /var/log/samba/log.phong (note phong is a windoze client) and got: [2004/02/10 12:10:20, 0] tdb/tdbutil.c:tdb_log(531) tdb(/var/cache/samba/printing.tdb): rec_free_read bad magic 0x0 at offset=1905 6 [2004/02/10 12:10:20, 0] tdb/tdbutil.c:tdb_log(531) tdb(/var/cache/samba/printing.tdb): rec_read bad magic 0x0 at offset=17964 Any help will be

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)

I've had a consistent problem with Samba from 2.2.1 onwards, maybe even before then, I'm not sure when it started. Anyway, Samba will randomly stop responding to any requests, although it usually occurs after transfering large amounts of data (1 GB+). To get around the problem, I've been restarting samba every night, but we still have the problem occasionally. smbclient shows:

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

THANKYOU THANKYOU THANKYOU!!!! That was it exactly. I looked all over the net for the solution to this problem for the last two weeks. Once again thank you!!! jor -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jordan Thompson wrote: | Can't print from client computers: | | I tailed the /var/log/samba/log.phong (note phong is a windoze | client) and got: | [2004/02/10 12:10:20, 0]

Hi there, My Mandrake server has been working fine for years, and I just recently tried adding some rpms to get my squirrel mail updated. (Of course I just removed my uneeded sound card at the same time, amd also found my /var was filling(fixed - printing still doesn't work_, so I am not sure what (if any) broke my system. Any how... here are the symptoms: (1) I can access my shared samba

Hello, some of my servers regularly come up with this error, which makes printing over samba impossible: Mar 6 09:06:44 server smbd[4431]: [2007/03/06 09:06:44, 0] tdb/tdbutil.c:tdb_log(772) Mar 6 09:06:44 server smbd[4431]: tdb(/var/cache/samba/printing/printer.tdb): rec_read bad magic 0xd9fee666 at offset=22796 Searching mailing lists, I just found the "solution" to stop

Hi, I'm seeing this in log.winbind [2004/07/16 13:26:57, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/lib/samba/winbindd_idmap.tdb): rec_free_read bad magic 0x42424242 at offset=25528 [2004/07/16 13:26:57, 1] nsswitch/winbindd_user.c:winbindd_fill_pwent(50) error getting user id for sid S-1-5-21-2216088991-3827457959-3939315012-1283 [2004/07/16 13:26:57, 0] tdb/tdbutil.c:tdb_log(725)

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

I'm running Samba 3.0.11. Compiled with: ./configure '--with-ads' '--with-pam' '--with-winbind' '--with-smbmount' '--with-shared-modules=idmap_rid' It configured, make and make installed fine. I configured the idmap_rid using the following directives in the smb.conf. ; IDMap Stuff idmap backend = idmap_rid:<DOMAINNAME>=500-100000000

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:

I am encountering some error I am unfamiliar with in the log.winbind. Any help is appreciated. [2006/01/23 06:44:32, 1] nsswitch/winbindd_user.c:winbindd_getpwent(715) could not lookup domain user rjb15 [2006/01/23 06:44:32, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/lib/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=20784688 [2006/01/23 06:44:32, 0]

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

Hi everyone, Our system is a Debian GNU/Linux box running Linux kernel 2.4.17-xfs and Samba 2.2.3 (from the 2.2.3-5 package from Sid), built using gcc-3.0.3. With Samba 2.2.2 we hit certain tdb errors where make_connection would reject connections arbitrarily. Supposedly this was fixed using 2.2.3 so we upgraded right away (thankfully we do only have Windows 95, 98 and ME clients so we

I am running Ubuntu with LTSP authenticating to ADS on a Windows 2003 server SP1. My windows side of the network is running fine. The Linux terminals are not able to login all users... weirdly, some can, some can't. In my log.winbindd-idmap file, I get a slew of entries similar to this: [2006/09/25 22:54:21, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/lib/samba/winbindd_idmap.tdb):

----- 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]

When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13