RE : SAMBA 2.2.4 or 2.2.7a and broken pipe
SAMBA 2.0.6 allows the smbd process to be run interactively Sure, 2.2.7 kept that very interesting feature for debugging. The syntax is RUN SAMBA_ROOT:[BIN]SMBD -i -dn n being the debug (trace) level you want. Between 3 and 5 is usually enough to have a lot of information. Before doing that, however, you'll have to $ TCPIP disable service SMBD and to stop any SMBD_* process of the system. Note that this feature is also available for NMBD. PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
re: SAMBA 2.2.4 or 2.2.7a and broken pipe
From: [EMAIL PROTECTED] (Carl Gunnar Linden, MSL Stockholm Sweden.) wrote: I am running OpenVMS V7.3 and Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 1 I try to run SAMBA 2.2.4 or 2.2.7a. It works with TCPIP V5.3-18 but I think it stopped working since I applied the TCPIP_ECO V5.3-181 patch. snip Has anybody else seen something like this and what is a broken pipe? A broken pipe indicates a general connection problem. By it self it is not useful to tell you what the problem is. I would try the nmblookup (OpenVMS), NET VIEW (DOS Command prompt) tests to see if you can get information that way. There is a file diagnostic.txt that should be in the SAMBA distribution that describes how isolate some of these problems. You can get a copy of it at http://www.samba.org. The other thing to do is to increase the error level for the SMBD process. Previous versions of SAMBA allowed this to be done by defining a SYSTEM wide logical. SAMBA 2.0.6 allows the smbd process to be run interactively so that these tests can be more easily run. I do not know if the SAMBA 2.2.x branch has this ability. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: SAMBA 2.2.4 or 2.2.7a and broken pipe
From: SMTP%[EMAIL PROTECTED] 26-FEB-2003 04:51:01.13 To: [EMAIL PROTECTED] CC: Subj: SAMBA 2.2.4 or 2.2.7a and broken pipe I am running OpenVMS V7.3 and Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 1 I try to run SAMBA 2.2.4 or 2.2.7a. It works with TCPIP V5.3-18 but I think it stopped working since I applied the TCPIP_ECO V5.3-181 patch. I can connect by using SMBCLIENT. If I try from Windows 95, for example, I get the following written to the log-file [2003/02/25 17:12:15, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(1018) getpeername failed. Error was socket is not connected [2003/02/25 17:12:16, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(505) write_socket_data: write failure. Error = broken pipe [2003/02/25 17:12:16, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(529) write_socket: Error writing 4 bytes to socket 3: ERRNO = broken pipe [2003/02/25 17:12:16, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(709) Error writing 4 bytes to client. -1. (broken pipe) Has anybody else seen something like this and what is a broken pipe? Thankfull for any hint. Carl Gunnar Linden MSL Stockholm Sweden == RFC 822 Headers == Return-Path: [EMAIL PROTECTED] Received: from dp.samba.org (66.70.73.150) by idia02.srfnet.com (V5.3-18, OpenVMS V7.3-1 Alpha); Wed, 26 Feb 2003 04:50:57 -0500 (EST) Received: from dp.samba.org (localhost [127.0.0.1]) by lists.samba.org (Postfix) with ESMTP id B1E002C526 for [EMAIL PROTECTED]; Wed, 26 Feb 2003 09:50:56 + (GMT) Delivered-To: [EMAIL PROTECTED] Received: from msia02.msi.se (msia02.msi.se [130.237.217.62]) by lists.samba.org (Postfix) with SMTP id F38632C33A for [EMAIL PROTECTED]; Wed, 26 Feb 2003 09:50:21 + (GMT) Date: Wed, 26 Feb 2003 10:49:27 +0100 (MET) Message-Id: [EMAIL PROTECTED] From: [EMAIL PROTECTED] (Carl Gunnar Linden, MSL Stockholm Sweden.) To: [EMAIL PROTECTED] X-VMS-To: [EMAIL PROTECTED] Subject: SAMBA 2.2.4 or 2.2.7a and broken pipe X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1 Precedence: list List-Id: Using Samba with VMS samba-vms.lists.samba.org List-Unsubscribe: http://lists.samba.org/listinfo/samba-vms, mailto:[EMAIL PROTECTED] List-Archive: http://lists.samba.org/pipermail/samba-vms List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.samba.org/listinfo/samba-vms, mailto:[EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED]
Re: SAMBA 2.2.4 or 2.2.7a and broken pipe
I am running OpenVMS V7.3 and Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 1 I try to run SAMBA 2.2.4 or 2.2.7a. It works with TCPIP V5.3-18 but I think it stopped working since I applied the TCPIP_ECO V5.3-181 patch. I can connect by using SMBCLIENT. If I try from Windows 95, for example, I get the following written to the log-file Sorry about the previous reply, I hit return too quickly. Yes, you are correct, this is a bug introduced by V5.3 ECO 1. Some race condition was causing the socket handoff from the inet daemon (TCPIP$INET_ACP) to the created service process to fail. I first saw it using SWAT, which creates a number of service processes very quickly as your browser requests the .GIF files for the initial page. This bug is listed as fixed in V5.3 ECO 2, and it HAS been fixed as far as I can see from my initial testing. -- George Watson [EMAIL PROTECTED]
