similar to: Problem in restarting samba server

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

I've run into a problem with samba and tdb reporting "too many connections" If I do a typical configure: ./configure --prefix=/usr/local/samba \ --localstatedir=/var/samba \ --with-lockdir=/var/samba/locks \ --with-configdir=/usr/local/samba/etc I see errors like the following in /var/samba/log.smbd: [2001/11/10 22:58:53, 0] tdb/tdbutil.c:tdb_log(342)

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

Hi, I'm wondering if anyone can diagnose the following errors from my log.smbd: ------------ smbd version 2.2.3 started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/02/21 12:04:19, 0] tdb/tdbutil.c:tdb_log(475) tdb(/usr/local/samba/var/locks/connections.tdb): tdb_oob len 1111638618 beyond eof at 8192 [2002/02/21 12:04:19, 0] smbd/connection.c:claim_connection(188)

Hi, I know this isn't a supported platform or anything, but I'm trying to get Samba 2.2.5 going on my Playstation 2 (mipsel-linux). There's an RPM for 2.0.something on the PS2-Linux CD, but I'm always a fan of running the latest version. It compiles okay, as long as I specity ./configure --host=mipsel-linux (not "--build=mipsel-linux" for some reason, like most

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

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

Hello, for this two platforms x86 and MIPS, I use Samba 2.2.12 on Linux 2.4 (Debian). It run well on x86 platform after configure and compilation on this platform, with glibc. I configure for MIPS and compile samba on MIPS platform with uClibc. smbd daemon aborted on error. Here, in the end of this /var/log/samba/log.smbd file : ... [1970/01/02 07:30:11, 0]

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

Hi all,. I'm getting this:- [2002/03/08 10:26:28, 8] lib/util.c:(1274) fcntl_lock 6 34 0 1 2 [2002/03/08 10:26:28, 8] lib/util.c:(1314) fcntl_lock: Lock call successful [2002/03/08 10:26:28, 5] tdb/tdbutil.c:(475) tdb((NULL)): tdb_brlock failed (fd=7) at offset 4 rw_type=2 lck_type=6 [2002/03/08 10:26:28, 5] smbd/connection.c:(156) claiming 0 [2002/03/08 10:26:28, 0]

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, all. I'm using Samba 2.2.2 at my FreeBSD 4.4-STABLE server, and have next problems: There is pool of W2K machines, each starting compilation job (usually 2 at one dual CPU machine). Then these jobs trying to simultaneously access sources, located at Samba server, appear problems. Then I running 2 compilation threads from single machine - there is no problems. For jobs error seems

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

Please, What's this? Please, please, how to resolve ? [root@neosaldina-lj003 samba]# more nmbd.log tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04 00:12:51, 2] tdb/tdbutil.c:tdb_log(725) tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04

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)

Hello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the

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

Dear all, The server log is filled with entries "xxx len xxxxx deyond eof at 8192" I have search on google but can't found a solution for it, please advise. The server is running FC2 with samba-3.0.7-2.FC2 Jan 24 14:49:16 smb nmbd[30183]: [2005/01/24 14:49:16, 0] tdb/tdbutil.c:tdb_log(725) Jan 24 14:49:16 smb nmbd[30183]: tdb(/var/cache/samba/gencache.tdb): tdb_oob len

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:

Some times I have in log : [2004/02/04 12:00:06, 5] lib/gencache.c:gencache_init(59) Opening cache file at /var/lock/samba/gencache.tdb [2004/02/04 12:00:06, 5] tdb/tdbutil.c:tdb_log(724) tdb(unnamed): tdb_brlock failed (fd=12) at offset 4 rw_type=1 lck_type=13: Ressource temporairement non disponible [2004/02/04 12:00:06, 5] libsmb/namecache.c:namecache_enable(58) namecache_enable: