Question about log messages
don_mccall at hp.com
Mon Jan 29 17:59:25 GMT 2001
That message comes from a couple of places in the code;both are called after
a new smbd daemon is spawned to handle the connection of a new client to
Samba, and is calling getpeername against the socket fd that the connection
was started on. What this message is saying is that the socket (fd) that it
was passed is no longer a valid socket, and probably means that by the time
the smbd process got to the point of making this call, the connection had
been terminated for some reason, ie the client making the connection attempt
Could be any number of reasons for this. One thing you could do to gather
more info is change your smb.conf file global parameter
log file = /usr/local/samba/var/log.%m
This would give you a separate log file for every client machine name
connecting to the Samba server, and you could track which of these machines
were making connections at the time you see these messages.
Hope this helps,
From: MEwing at berkleyis.com [mailto:MEwing at berkleyis.com]
Sent: Friday, January 26, 2001 8:37 AM
To: samba at samba.org
Subject: Question about log messages
I have the Samba-2.0.7 server operating on a HP K200 system running HP-UX
11.00. It seems to be running
ok, but the log files contain numerous entries similar to the following
(the samba log level is set to three).
Jan 25 20:08:15 bisup3 smbd: getpeername failed. Error was Bad
Jan 25 20:09:46 bisup3 above message repeats 5 times
Jan 25 19:54:38 bisup3 smbd: [2001/01/25 19:54:38, 0]
Jan 25 20:11:34 bisup3 smbd: [2001/01/25 20:11:34, 0]
I have checked the documents provided with the source code as well as the
FAQ and do not find any
mention of this type of error message. Is this a normal message?
Is there something that I need to
fix to eliminate these messages?
If you need additional information about this, please let me know.
Thank you for your assistance.
UNIX System Administrator
Berkley Information Services
More information about the samba