Bug 232 - getpeername failed
Summary: getpeername failed
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.0preX
Hardware: All Linux
: P4 normal
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-16 14:09 UTC by Paul Eggleton
Modified: 2005-11-14 09:25 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2003-07-16 14:09:26 UTC
I am getting the following errors in log.smbd every time a client machine 
connects to Samba:

[2003/07/10 15:09:22, 0] lib/util_sock.c:get_socket_addr(895)
  getpeername failed. Error was Transport endpoint is not connected

At the same time I get a log.0.0.0.0 file, as well as a log.clientname and 
log.ip.addr.of.client file. I did some searching and found some reports saying 
that this was a DNS reverse lookup problem. However, I have checked and 
nslookup clientname works, as does nslookup ip.addr.of.client (although it 
returns "clientname.domainname." because that's what the Windows 2000 DNS 
server has defined automatically). WINS is not running on our network. The two 
machines in question (the server and the client machine connecting to it) are 
on the same domain and the same subnet - the client is running Windows 2000 
Server SP3 and the Samba server is running on a fairly clean install of Red Hat 
Linux 9.0. There is no firewalling between the two machines. Samba 3.0beta2 was 
compiled from source.

This problem does not appear to be adversely affecting Samba's operation, but 
it would be nice to figure out why it is occurring.
Comment 1 Kristis Makris 2003-07-17 15:45:40 UTC
I have experienced something similar to what Paul just reported, with the
details of my report found at:

http://lists.samba.org/pipermail/samba/2003-July/099534.html

I get a 0.0.0.0.log file too (not log.0.0.0.0).
Comment 2 Paul Eggleton 2003-07-17 16:52:13 UTC
You are likely getting 0.0.0.0.log because your "log file" setting is set to %
m.log rather than log.%m, so this is unrelated.
Comment 3 Gerald (Jerry) Carter (dead mail address) 2003-07-24 20:31:04 UTC
lowering priority since it appears to be a cosmetic bug 
in the log files.  

Can you send me a level 10 debug log so I can see where in the 
process of things this error is being generated?  Please mail 
it to me directly.
Comment 4 Jim Richardson 2003-09-05 19:24:38 UTC
I have just installed and configured 3.0 rc2 on Redhat 8.0 and am seeing these
same errors.
Comment 5 Gerald (Jerry) Carter (dead mail address) 2003-09-22 12:17:03 UTC
getpeername() fails because the client has disconnected.  Possible 
casues are bad hubs, NICs, drivers, etc....  No response from 
questions posted back in July.  Closing trhis one out.
Comment 6 Gerald (Jerry) Carter (dead mail address) 2005-02-07 08:41:30 UTC
originally reported against 3.0.0beta3.  CLeaning out 
non-production release versions.
Comment 7 Gerald (Jerry) Carter (dead mail address) 2005-11-14 09:25:28 UTC
database cleanup