[Pkg-samba-maint] Bug#464035: closed by Mathieu Parent <math.parent at gmail.com> (Re: Bug#464035: 464035 Bug#464035: samba: Cannot connect user)

[Josip Rodin]

It should be noted for anyone looking at the bug report that this didn't
seem to make any sense with regard to the original submission.

Right now things look like this at one of my Samba servers:

% sudo find /var/log/samba/ -type f -mtime -5 -print0 | xargs -0 grep -h -A1 getpeername | grep -v '^--$' | sort | uniq -c
   1938   getpeername failed. Error was Transport endpoint is not connected
   1477   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
     14   read_fd_with_timeout: client 0.0.0.0 read error = Connection timed out.
     81   read_fd_with_timeout: client 0.0.0.0 read error = No route to host.
    366   write_data: write failure in writing to client 0.0.0.0. Error Broken pipe

These subsequent lines make it more obvious that there seems to be a problem
with the remote end rather than with the Samba server, which seems like
a decent enough resolution to the original bug submission.

On Tue, Jun 27, 2017 at 01:45:06PM +0000, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the samba package:
> 
> #464035: samba "getpeername failed." error message
> 
> It has been closed by Mathieu Parent <math.parent at gmail.com>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Mathieu Parent <math.parent at gmail.com> by
> replying to this email.
> 
> 
> -- 
> 464035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464035
> Debian Bug Tracking System
> Contact owner at bugs.debian.org with problems

> Date: Tue, 27 Jun 2017 15:44:06 +0200
> From: Mathieu Parent <math.parent at gmail.com>
> To: "L.P.H. van Belle" <belle at bazuin.nl>, 464035-done at bugs.debian.org
> Subject: Re: Bug#464035: 464035 [Pkg-samba-maint] Bug#464035: samba: Cannot
>  connect user
> 
> Hi,
> 
> I'm closing this bug then.
> 
> 2017-06-27 15:12 GMT+02:00 L.P.H. van Belle <belle at bazuin.nl>:
> > Hai,
> >
> > I agree with Steve, this is not a bug but fix below ( for windows )
> > even that the pdbedit -L fixed this for Peter, im adding this for historical
> > lookups.
> >
> > You see this mainly with windows XP.
> >
> > When attempting to join a domain, you receive the following error message:
> > "Computer Name Changes: The following error occurred attempting to join the
> > domain MYDOMAIN: The specified network password is not correct".
> >
> > Additionally, your Samba logfile (at debug level 1) reveals:
> > "smbd/service.c:make_connection(): Can't become connected user!".
> >
> > This is usually caused by improper registry settings in the client.
> >
> > Use Window's Group Policy Editor (gpedit.msc) to make the following changes
> > in the :
> >  "Local Computer Policy\Computer Configuration\Windows Settings\Security
> > Settings\Local Policies\Security Options"
> >
> > Disable: Domain member: Digitally encrypt or sign secure channel data
> > Disable: Domain member: Digitally sign secure channel data (when possible)
> > Please, close bug.
> >
> >
> > Greetz,
> >
> > Louis
> 
> 
> 
> -- 
> Mathieu

> Date: Mon, 4 Feb 2008 21:33:09 +0100
> From: Josip Rodin <joy at debbugs.entuzijast.net>
> To: submit at bugs.debian.org
> Subject: samba "getpeername failed." error message
> 
> Package: samba
> Version: 3.0.24-6etch9
> 
> Hi,
> 
> source/lib/util_sock.c's get_peer_addr() function does:
> 
> 	if (getpeername(fd, &sa, &length) < 0) {
> 		DEBUG(0,("getpeername failed. Error was %s\n", strerror(errno) ));
> 		return addr_buf;
> 	}
> 
> This is littering my log.smbd file, like this:
> 
>   getpeername failed. Error was Transport endpoint is not connected
> 
> This apparent ENOTCONN is happening a couple of times every hour on one set
> of my machines.
> 
> At first I thought it was harmless, just logged at the level 0 (always),
> but looking more into the source, this should be getting generated after
> the following sequence of call in source/smbd/server.c:
> 
>                         if (allowable_number_of_smbd_processes() && smbd_server_fd() != -1 && sys_fork()==0) {
>                                 /* Child code ... */
>                                 
>                                 /* close the listening socket(s) */
>                                 for(i = 0; i < num_sockets; i++)
>                                         close(fd_listenset[i]);
>                                 
>                                 /* close our standard file
>                                    descriptors */
>                                 close_low_fds(False);
>                                 am_parent = 0;
>                                 
>                                 set_socket_options(smbd_server_fd(),"SO_KEEPALIVE");
>                                 set_socket_options(smbd_server_fd(),user_socket_options);
>                                 
>                                 /* this is needed so that we get decent entries
>                                    in smbstatus for port 445 connects */
>                                 set_remote_machine_name(get_peer_addr(smbd_server_fd()), False);
> ...
> 
> Perhaps it would be a good idea to test if smbd_server_fd() is returning
> something which is dead there, because something else could be going wrong...
> and I'd like to be able to know more about what is causing these.
> 
> -- 
>      2. That which causes joy or happiness.
> 
> 


-- 
     2. That which causes joy or happiness.