similar to: smbfs intermittent errors: tdb_lock failed, ERRDOS 71

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

Here's what I sent yesterday, more info follows: > Hello. I'm having a bit of trouble with my upgrade. I installed 3.0.8 > over a copy of the 2.2.8a directory, and when I went to start it up, got > errors about accessing the secrets.tdb. I was able to use tdbdump to > access it and created one in the new format using tdbtool, but then it's > also unable to access

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

Has anyone seen any fixes above 3.0.23a that addresses an issue similar to this one? [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_log(783) tdb(/usr/local/samba-3.0.23a/private/secrets.tdb): tdb_lock failed on list 65 ltype=1 (Interrupted system call) [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82) tdb_chainlock_with_timeout_internal: alarm (10) timed out for

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)

Hello, I'm having problems with samba share and trying to make multiple connections from one PC. Here are the errors I'm seeing in the log file: [2006/12/19 09:02:48, 1] smbd/service.c:make_connection_snum(648) amcfp001 (10.210.4.65) connect to service bvvol02_U1 initially as user bvvol02 (uid=502, gid=502) (pid 17671) [2006/12/19 09:02:48, 1]

Hi, Excuse my poor english !! I have a problem samba between linux and windows. I explain my actual situation : - windows 2000 SP4 - share a directory my_windows : d:\jagodin\partage - linux Redhat ES 4 - kernel version 2.6.9-5 in /etc/fstab : //my_windows/partage /export/home/cerit/jagodin/partage smbfs

Hello, i am running Samba 2.2.3a on a Red Hat Linux 7.3 box with kernel 2.4.18-10. I am experiencing some problems on a particular samba share, which is accessed by 10 Windows 98SE clients working on a COBOL production packet by mapping with a G: letters this samba folder. Well, some times a day it happens that this packed blocks because some files on that samba folder remains locked; i

Forgot to provide errors from my samba.log [2004/10/30 19:37:00, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/gencache.tdb): tdb_lock failed on list 4 ltype=1 (Bad file descriptor) [2004/10/30 19:37:00, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/gencache.tdb): tdb_lock failed on list 4 ltype=1 (Bad file descriptor) <shrug>, oplocks is turned off, so

We've just gone live with a file & print server, and are having major problems with Samba. When used out of hours, with all PCs switched on and connected to the domain, everything works fine. However, during the day, we have problems where users can't print to any samba-hosted printer, Access database applications (where the database is held on the server) won't work, or work

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings. I'm seeing an odd problem with 3.0.10 and 3.0.11 here. We have some pdf printers defined: [Accounting pdf printer] printer admin = "DOMAIN+Domain Users" browseable = yes path = /pdfdropbox/Accounting printable = yes writeable = no print command = /usr/bin/preprintpdf %s -r lpq command = lprm command =

Hi all, After much grief today, we'd like to support the 'TODO' note in source/lib/util_tdb.c :- /* TODO: If we time out waiting for a lock, it might * be nice to use F_GETLK to get the pid of the * process currently holding the lock and print that * as part of the debugging message. -- mbp */ It could have saved us a whole-sale restart of Samba if we could have more easily

Hello, We have a 3.0.21c samba server in a PDC role with ldap as the backend database, the server has been working without any problem for several weeks, but today it's started showing this log message: [2006/11/20 09:40:48, 0] tdb/tdbutil.c:tdb_log(772) tdb(/usr/local/etc2/samba_SACOU/private/secrets.tdb): tdb_lock failed on list 100 ltype=1 (Interrupted system call) [2006/11/20

Thanks, chdir dir /data error seems go away, but at 12:00 o'clock the following error appear: Feb 20 11:45:03 brulx01 vsftpd: Mon Feb 20 11:45:03 2006 [pid 12273] [job260] OK DOWNLOAD: Client "10.90.1.1", "/data/mde/DATA/.././ACTUAL/mdeact260.msg", 12481 bytes, 174.76Kbyte/sec Feb 20 11:56:10 brulx01 smbd[12410]: [2006/02/20 11:56:10, 0]

Hi all Follow up to this post, as it didn't seem to go through the first time. We have a common problem occurring with our Samba setups. We run 3 (identical) processing environments that each contain a Samba host sharing approx .5TB of data to 6 Wintel machines. Normally these hosts operate fine, though we intermittently experience a Samba panic (intermittent = every 2-3 days) as per below.

Hi All, I'm working on SUSE Linux 2.6.11.4-21.9-default i686 i386 GNU/Linux, with Samba Version 3.0.21a-0.1-SUSE. At Initially installation seems all works fine, but sometimes happens nobody can access to data share, people already authenticated, continuing working as well, while new users entry receive an error message. I have found something in "/var/log/messages" file

We have been using samba for years now and are generally very happy. But since a recent upgrade to 2.2.8 we have seen samba slowing down periodically to a crawl every 2 or 3 days. BTW the start of these problems coincided with the upgrade to samba 2.2.8 and a partial cabling upgrade to 100 MBit, which also coincided with the introduction of the first Win XP Pro machines to our LAN. ;-( We have

Hi all, By some days around 12:00 o'clock I have the following problem with my SUSE Linux 2.6.11.4-21.9-default i686 i386 GNU/Linux, with Samba Version 3.0.21a-0.1-SUSE: xxx:~ # tail /var/log/samba/log.machine01 [2006/02/23 12:05:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(180) Failed to verify incoming ticket! [2006/02/23 12:06:04, 0] tdb/tdbutil.c:tdb_log(772)