[Samba] REPOST: Odd SMBD log message
Miguel Medalha
miguelmedalha at sapo.pt
Sat Feb 7 19:01:50 GMT 2009
> Every so often I will see this in my log file:
>
> smbd[1034]: [2009/02/02 08:47:21, 0]
> lib/util_sock.c:get_peer_addr_internal(1607)
> smbd[1034]: getpeername failed. Error was Transport endpoint is not
> connected
> smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error =
> Connection reset by peer.
>
> smbd[1036]: [2009/02/02 08:47:22, 0]
> lib/util_sock.c:read_socket_with_timeout(939)
> smbd[1036]: [2009/02/02 08:47:22, 0]
> lib/util_sock.c:get_peer_addr_internal(1607)
> smbd[1036]: getpeername failed. Error was Transport endpoint is not
> connected
> smbd[1036]: read_socket_with_timeout: client 0.0.0.0 read error =
> Connection reset by peer.
>
If memory doesn't fail me, I had that in my logs until I set the "socket
address =" parameter to the IP address of the interface Samba is
listening on.
Quoting from the smb.conf man page:
«
This option allows you to control what address Samba will listen for
connections on. This is used to support multiple virtual interfaces
on the one server, each with a different configuration.
Setting this option should never be necessary on usual Samba servers
running only one nmbd.
By default Samba will accept connections on any address.
Default: //|socket address|/ = ||/
Example: //|socket address|/ = |192.168.2.20| /
//»
More information about the samba
mailing list