Jan Jurko
2022-Sep-20 09:31 UTC
[Samba] smbXsrv_client_connection_pass_loop: smb2srv_client_connection_passed() failed => NT_STATUS_OBJECT_NAME_NOT_FOUND
I downgraded 4.17.0 to 4.15.9 and there is no problem with shares and accessing the files. It is difficult to test it on my deployment because it is production so I cannot simply change versions multiple times per day or so. JJ> 20.?9.?2022 v 2:02, Andrew Bartlett via samba <samba at lists.samba.org>: > > If you have the time and patience, a 'git bisect' between the tags > samba-4.16.0rc1 and samba-4.17.0 it would be incredibly awesome as it > will identify the commit that caused this regression. > > Andrew Bartlett > > On Mon, 2022-09-19 at 16:06 -0700, haihua yang via samba wrote: >> Hi, I ran into the same issue. basically, client created seconds >> channels >> but for some reason, server fails in passing the fd. >> The issue seems to happen after 4.16. I compiled v4-16-stable, but I >> did >> not see the same issue. >> Haihua >> >> On Mon, Sep 19, 2022 at 3:27 AM Rowland Penny via samba < >> samba at lists.samba.org >>> wrote: >> >>> >>> On 19/09/2022 11:02, Jan Jurko via samba wrote: >>>>> 19.?9.?2022 v 10:41, Rowland Penny via samba < >>>>> samba at lists.samba.org >>>>>> : >>>>> >>>>> How are you running Samba ? >>>>> As a standalone server ? Or a Unix domain member ? >>>>> What Samba binaries are running ? >>>>> Please post your smb.conf >>>>> What are the clients ? >>>>> >>>>> Rowland >>>>> >>>>> >>>> Samba is started via /usr/local/samba/sbin/samba >>>> It is standalone active directory server. >>> >>> I think you mean that Samba is running as a DC and there is only >>> one DC. >>> >>> You are using the DC as a fileserver, so did you read this: >>> >>> >>> https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Using_the_Domain_Controller_as_a_File_Server_.28Optional.29 >>> >>> >>> Where (amongst other things) it says this: >>> >>> If you do use an AD DC as a fileserver, You must set the >>> permissions >>> from Windows, do not attempt to use any of the old methods (force >>> user >>> etc) . They will not work correctly and will cause problems. >>> >>> I would suggest that you add another DC (for failover) and then a >>> Unix >>> domain member and transfer the fileserver to that. >>> >>> If you do not want to do that, remove all the extraneous config >>> lines >>> from the shares (you only need the path and 'read only = no') and >>> then >>> set the permissions from a Windows machine. >>> >>> Rowland >>> >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: >>> https://lists.samba.org/mailman/options/samba >>> >>> > -- > Andrew Bartlett (he/him) https://samba.org/~abartlet/ > Samba Team Member (since 2001) https://samba.org > Samba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba > > Samba Development and Support, Catalyst IT - Expert Open Source > Solutions > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Andrew Bartlett
2022-Sep-20 20:59 UTC
[Samba] smbXsrv_client_connection_pass_loop: smb2srv_client_connection_passed() failed => NT_STATUS_OBJECT_NAME_NOT_FOUND
Can you set up another environment similar to production that does reproduce this? Either way, I've sent an invite to you and Haihua for our bugzilla to let you file a bug for this, and to fill in what details are known. Hopefully someone who knows this code well can help out with any further debugging steps. Andrew, On Tue, 2022-09-20 at 11:31 +0200, Jan Jurko via samba wrote:> I downgraded 4.17.0 to 4.15.9 and there is no problem with shares and > accessing the files. It is difficult to test it on my deployment > because it is production so I cannot simply change versions multiple > times per day or so. > > JJ > > > > 20.?9.?2022 v 2:02, Andrew Bartlett via samba < > > samba at lists.samba.org > > >: > > > > If you have the time and patience, a 'git bisect' between the tags > > samba-4.16.0rc1 and samba-4.17.0 it would be incredibly awesome as > > it > > will identify the commit that caused this regression. > > > > Andrew Bartlett > > > > On Mon, 2022-09-19 at 16:06 -0700, haihua yang via samba wrote: > > > Hi, I ran into the same issue. basically, client created seconds > > > channels > > > but for some reason, server fails in passing the fd. > > > The issue seems to happen after 4.16. I compiled v4-16-stable, > > > but I > > > did > > > not see the same issue. > > > Haihua > > > > > > On Mon, Sep 19, 2022 at 3:27 AM Rowland Penny via samba < > > > samba at lists.samba.org > > > > > > > wrote: > > > > On 19/09/2022 11:02, Jan Jurko via samba wrote: > > > > > > 19.?9.?2022 v 10:41, Rowland Penny via samba < > > > > > > samba at lists.samba.org > > > > > > > > > > > > > : > > > > > > > > > > > > How are you running Samba ? > > > > > > As a standalone server ? Or a Unix domain member ? > > > > > > What Samba binaries are running ? > > > > > > Please post your smb.conf > > > > > > What are the clients ? > > > > > > > > > > > > Rowland > > > > > > > > > > > > > > > > > > > > > > Samba is started via /usr/local/samba/sbin/samba > > > > > It is standalone active directory server. > > > > > > > > I think you mean that Samba is running as a DC and there is > > > > only > > > > one DC. > > > > > > > > You are using the DC as a fileserver, so did you read this: > > > > > > > > > > > > https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Using_the_Domain_Controller_as_a_File_Server_.28Optional.29 > > > > > > > > > > > > > > > > Where (amongst other things) it says this: > > > > > > > > If you do use an AD DC as a fileserver, You must set the > > > > permissions > > > > from Windows, do not attempt to use any of the old methods > > > > (force > > > > user > > > > etc) . They will not work correctly and will cause problems. > > > > > > > > I would suggest that you add another DC (for failover) and then > > > > a > > > > Unix > > > > domain member and transfer the fileserver to that. > > > > > > > > If you do not want to do that, remove all the extraneous config > > > > lines > > > > from the shares (you only need the path and 'read only = no') > > > > and > > > > then > > > > set the permissions from a Windows machine. > > > > > > > > Rowland > > > > > > > > -- > > > > To unsubscribe from this list go to the following URL and read > > > > the > > > > instructions: > > > > https://lists.samba.org/mailman/options/samba > > > > > > > > > > > > > > > > -- > > Andrew Bartlett (he/him) > > https://samba.org/~abartlet/ > > > > Samba Team Member (since 2001) > > https://samba.org > > > > Samba Team Lead, Catalyst IT > > https://catalyst.net.nz/services/samba > > > > > > Samba Development and Support, Catalyst IT - Expert Open Source > > Solutions > > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: > > https://lists.samba.org/mailman/options/samba > >-- Andrew Bartlett (he/him) https://samba.org/~abartlet/ Samba Team Member (since 2001) https://samba.org Samba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba Samba Development and Support, Catalyst IT - Expert Open Source Solutions