search for: rec_read

...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): rec_free_read bad magic 0x2e6e7270 at offset=4940 [1995/12/08 12:52:10, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/lib/samba/printing.tdb): rec_read bad magic 0xd9fee666 at offset=4888 [1995/12/08 12:52:10, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/lib/samba/printing.tdb): rec_read bad magic 0xd9fee666 at offset=4888 [1995/12/08 12:52:10, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/lib/samba/printing.tdb): rec_read bad magic 0xd9fee666 at offset=48...

...able range available for sid: S-1-5-32-545 [2005/03/03 14:15:01, 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:27:51, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=17036 [2005/03/03 14:27:51, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=17036 [2005/03/03 14:27:51, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/winbindd_idmap.tdb): rec_...

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 setup. Either your hardware is flaky or your smbd processes tend to crash. If...

...t server principal name =dc1$@BLAH.DOMAIN.NZ ads_krb5_mk_req: krb5_cc_get_principal failed (No credentials cache found) Ticket in ccache[MEMORY:winbind_ccache] expiration Mon, 31 Oct 2005 23:47:43 GMT ads: query_user_list ads query_user_list gave 100 entries tdb(/var/lib/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset= 59948 error getting user id for sid S-1-5-21-997653320-332963777-2638616180-1106 could not lookup domain user IWAM_DC1 tdb(/var/lib/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset= 59948 tdb(/var/lib/samba/winbindd_idmap.tdb): rec_free_read bad m...

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 samba, delete the tdb file, and restart it. I am in charge of 25 servers of this kind and would be happy for a more "professional" solution to this... :-) Is there any... ? O...

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 0xd9fee666 at offset=23256 Jan 30 12:28:38 primary smbd[2577]: [2006/01/30 12:28:...

...002/09/03 09:56:30, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/cache/samba/printing.tdb): rec_free_read bad magic 0xfee1dead at offset=17772 [2002/09/03 09:56:31, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/cache/samba/printing.tdb): rec_read bad magic 0xd9fee666 at offset=16684 (What's the chance that a hex number spells out what looks like "feel dead"? A flagged value or pure chance?) Anyway, I noticed that someone else had what looks like the same problem in 2.2.3 on February 22nd, but apparently no one replied. Any...

...who sent one). When I now delete them manually, they're gone. Since I can't find any remaining SMB or CUPS spool-files, (thought about missing access rights for deletion) I don't know what to look for. The only error message I found is: tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad magic 0xd9fee666 at offset=26084 in /var/log/samba/smbd (but I got this message sometimes before the upgrade too ...) Thanks for some hints on that (2) problem(s) Thomas

...in smbstatus Now the MACHINE1 is switched off. 18:16:21 - MACHINE1/USER1 - is in smbstatus !! (and the MACHINE1 is switched off several hours!) 18:16:31 - MACHINE1/USER1 - is NOT in smbstatus Sometimes (cca twice a day) smbstatus return error output like this: tdb(/var/run/samba/sessionid.tdb): rec_read bad magic 0xd9fee666 at offset=116988 It's a bug or a feature and smbstatus is only informative? It's solved in some newer version? Can you tell me about better source for connected user status? Thanks.

...failed with error Corrupt database. Aug 3 11:18:15 Server smbd[22142]: read_data: read failure for 4. Error = No route to host Aug 3 11:18:15 Server smbd[22142]: [2002/08/03 11:18:15, 0] tdb/tdbutil.c:tdb_log(492) Aug 3 11:18:15 Server smbd[22142]: tdb(/var/run/samba/connections.tdb): rec_read bad magic 0x42424242 at offset=5036 Aug 3 11:18:15 Server smbd[22142]: [2002/08/03 11:18:15, 0] smbd/connection.c:yield_connection(62) Aug 3 11:18:15 Server smbd[22142]: yield_connection: tdb_delete for name rabe-www failed with error Corrupt database. Aug 3 11:18:15 Server smbd[22142]: [...

...r and when I check the driver didn't seem to be in the driver list anymore. Now when I try to re-upload the drivers it give me an error about not being able to save the parameters because there's not enough memory. And in my log I get a bunch of these: tdb(/var/cache/samba/ntprinters.tdb): rec_read bad magic 0xd9fee666 at offset=9260 What can I do about that? Here's my print$ share: [print$] path = /var/lib/samba/printers guest ok = No browseable = No read only = Yes valid users = @users write list = root, jrc Jean-Rene Cormier

...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 most appreciated. Jordan -- Jordan R. Thompson Mail:Jordan@ThompCo.com Web:www.Jordan.ThompCo.com Tel:(321) 777-8377 Cel:(321) 501-2259 Fax:(509) 267-5577

...error message on the windows machine was: "A StartDocPrinter call was not issued". On viewing samba logs for the machine, we got following error: tdb(/var/lib/samba/printing/Samsung.tdb): rec_free_read bad magic 0x42424242 at offset=63736 tdb(/var/lib/samba/printing/Samsung.tdb): rec_read bad magic 0xd9fee666 at offset=58844 tdb(/var/lib/samba/printing/Samsung.tdb): rec_read bad magic 0xd9fee666 at offset=58844 tdb(/var/lib/samba/printing/Samsung.tdb): rec_free_read bad magic 0x42424242 at offset=63736 We had a thought that Samsung.tdb file might have got corrupted, so we remov...

...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] 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, 1] sam/idmap_ad.c:ad_idmap_get_id_from_sid(329) ad_idmap_get_id_from_sid: ads_pull_uint32:...

...failed with error Corrupt database. Aug 3 11:18:15 Server smbd[22142]: read_data: read failure for 4. Error = No route to host Aug 3 11:18:15 Server smbd[22142]: [2002/08/03 11:18:15, 0] tdb/tdbutil.c:tdb_log(492) Aug 3 11:18:15 Server smbd[22142]: tdb(/var/run/samba/connections.tdb): rec_read bad magic 0x42424242 at offset=5036 Aug 3 11:18:15 Server smbd[22142]: [2002/08/03 11:18:15, 0] smbd/connection.c:yield_connection(62) Aug 3 11:18:15 Server smbd[22142]: yield_connection: tdb_delete for name rabe-www failed with error Corrupt database. Aug 3 11:18:15 Server smbd[22142]: [...

...- 0) The log file is filled with lines similar to the following: [2002/07/16 17:34:02, 0] tdb/tdbutil.c:(342) tdb(/usr/local/samba/var/locks/locking.tdb): rec_free_read bad magic 0xa8ad6646 at offset=1124 [2002/07/16 17:35:22, 0] tdb/tdbutil.c:(342) tdb(/usr/local/samba/var/locks/locking.tdb): rec_read bad magic 0xd9fee666 at offset=840 [2002/07/18 21:41:15, 0] smbd/nttrans.c:(1798) call_nt_transact_ioctl: Currently not implemented. [2002/07/18 21:41:41, 0] tdb/tdbutil.c:(342) tdb(/usr/local/samba/var/locks/connections.tdb): remove_from_freelist: not on list at off=237568 [2002/07/18 21:41:41...

...> > > > Since I can't find any remaining SMB or CUPS spool-files, > > (thought about missing access rights for deletion) > > I don't know what to look for. > > > > The only error message I found is: > > tdb(/var/lib/samba/printing/Kyocera7000.tdb): rec_read bad magic 0xd9fee666 > > at offset=26084 > > in /var/log/samba/smbd (but I got this message sometimes before the upgrade > > too ...) > > > > Thanks for some hints on that (2) problem(s) > > Thomas > > > > > > > > > > > > &gt...

----- 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] tdb/tdbutil.c:tdb_log(724) I stopped smb then proceeded to delete this file (made a backup before doing so) and started smb again. The file was recreated and I havent seen this particula...

...ar/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 Stop smbd, remove printing.tdb and restart. btw...there code in the current SAMBA_3_0 cvs branch to work around this but removing the tdb at run time. cheers, jerry - ---------------------------------------------------------------------- Hewlett-Packard...

...functioning fine, I haven't noticed any odd behavior, haven't had any complaints. But, a few weird errors have got me concerned. 1) I often run smbstatus, about once every dozen or so times of running smbstatus I'll get an error like this.. tdb(/usr/local/samba/var/locks/locking.tdb): rec_read bad magic 0xd9fee666 at offset=250092, I run smbstatus again, literally 1 second later and its fine. 2) Every several seconds to every several minutes depending, I guess depending on how heavy the server's being worked I'm getting log.smbd entries: [2007/03/07 08:16:57, 0] passdb/pdb_smb...