similar to: Error was Transport endpoint is not connected

It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,

Good Afternoon, I have Samba 2.2.1a running on a SPARC Solaris 2.7. All of a sudden I'm having a problem with one PC mapping Samba drives. In the log file for this PC I get the following error messages: [2001/12/11 12:47:22, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2001/12/11 12:47:22, 0] lib/util_sock.c:send_smb(729)

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

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

I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23

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

I've recently developed these messages coming out of the log.smbd. I can no longer connect to my samba drives. I get an explorer window, but no shares displayed. Anyone have any ideas? Thanks [2006/10/29 07:58:48, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/db/samba/locking.tdb): tdb_reopen: open failed (No such file or directory) [2006/10/29 07:58:48, 0]

hello, using SuSE 7.3 with all Patches and SAMBA 2.2.7a-SuSE after a couple of days too many files are opend (bejond 16000) and samba hast to be totally stopped and restartet. the log tells us the following: [2003/03/13 09:21:44, 0] smbd/posix_acls.c:create_canon_ace_lists(919) create_canon_ace_lists: unable to map SID S-1-5-21-823518204-1202660629-842925246-2721 to uid or gid. [2003/03/13

I've noticed a couple disturbing things in the new 2.2.8a-1 rpm patch released yesterday. smbd now seems to run move than one daemon instance. I imagine that this is how they circumvent the whole getting root access. However there seems to be a few bugs that I notice (the first two somewhat important, the last two not so important... although perhaps related?): 1. the executing user of the

Hi, all: I am using Samba 3.0.5 with patch at http://samba.org/~jerry/patches/post-3.0.4/. But I found the follow messages in samba log: =============================================================== [2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1398) PANIC: internal error [2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1406) BACKTRACE: 3 stack frames: #0 smbd(smb_panic2+0xef)

Hi folks, I'm trying to install a pre-compiled version of Samba 2.2.2 on Solaris 7. For the most part, Samba appears to work except I got 2 errors: - Whenever Windows 9?/2K users access any of the shares, I get this message in the samba log: [2001/12/21 15:09:25, 0] tdb/tdbutil.c:tdb_log(342) tdb(/usr/local/admin/samba-2.2.2/private/secrets.tdb): tdb_reopen: failed to obtain active

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

Hi folks, # uname -srvo Linux 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:01:26 EDT 2010 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # smbd --version Version 3.3.8-0.51.el5 I'm trying to run a backup samba server using some custom in-house scripts which I inherited and am stuck with. Essentially the primary server periodically rsyncs a bunch of

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

Hello, I am using Red-hat Linux Application Server 3.0. I have installed and successfully configured samba server & thus able to connect from windows m/c....It works perfectly fine. But when I install our product( Its a java application and one kernel loadable module) on the same machine The samba server does not restart. Following are the messages in /var/log/samba/smbd.log. after

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:

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

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: