similar to: "rec_read bad magic" error when printing... again

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

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

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

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

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

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

Hello, I tried to run a program written in Delphi in wine and it ran quite perfectly, but sadly there was one important detail that made using it impossible... It seems that wine has a problem with the text inputs (edits). They are "string" datatypes (8 bit ansi string), and not null terminated. The problem was showing itself e.g. at the login form of the program. The password I

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:

Hi All, Firstly, I know this is a MacOS X issue and not sure if you guys can help, but I'm really hoping you can since I don't appear to be getting any joy elsewhere. Running OSX 10.5.4 and recently (last week) nmbd is hogging the CPU. I know this is a part of the Samba server on OSX, hence the post to this mail-list. When I disconnect from the network, nmbd goes away and doesn't

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)

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

Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware:

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

Urs Rau wrote: >>I start to wonder what "dammage" it would do to set lpq to >>lpq command =/bin/true >>for my pdf printer? ;-) > > > > Well, wonder no more sir!!!!!! I set my lpq command = /bin/true and > ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you! That was all I did, I can't believe it worked......thank you!!!!!! >

Hello! I'm using samba with CUPS printing (with raw passthru) for a long time now and it worked very well. But after upgrading my samba installation from 3.0.2 to 3.0.9, the printjobs (sent from XP Workstations) aren't removed from the joblist anymore. Means: the job is printed correctly, but opening the printqueue on the XP machine still contains the job (not only mine, but jobs from

I'm getting the following errors in my error logs: ERROR! vuid 100 did not map to a valid vuser struct! At the time this error was being created I was trying to add a domain user as a local admin. I was trying to get the browse list of domain users up, but being denied. Cheers Jeff -- Jeff Gardiner [ gardiner@nospam.imaging.robarts.ca ] System Administrator - Imaging Research

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was running a netbench performance test against Samba 3.0.11, and the test has not been able to complete fully. The samba logs contain lines such as this: [2005/02/28 11:35:23, 1] smbd/service.c:make_connection_snum(645) ~ slave16 (192.168.133.116) connect to service netbench initially as user BENCHLAB+slave16 (uid=10016, gid=10001) (pid

Hello, after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3 days my Samba Server freeze the whole Server. First the clients get connection problems, timing out to access the shares and then some minutes later the whole Server freeze, i can't even logon on the console. Only a cold reset is possible. I convert all files from latin-1 to a UTF-8 and then from UTF-8 to ISO-8859-1

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)

I have a Samba server configured as PDC for ~100 computers. It's version 3.0.24 running on Debian Etch (distribution package). I want to write a tool for user logon/logoff tracking. Because parsing log files is hard job (windows frequently disconnets or connects during user session or etc.) I decide to use smbstatus output which seem to be reliable. So I run smbstatus binary every 10