samba - Apr 2020 - Share inaccessible intermittently and often - restarting smb cures for short time

Ok increased logging and got the error here is what got logged:

2020/04/23 14:03:17.514132,  3]
../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
status[NT_STATUS_SHARING_VIOLATION] || at ../../source3/smbd/smb2_create.c:334
[2020/04/23 14:03:17.514206,  3]
../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[5]
status[NT_STATUS_FILE_CLOSED] || at ../../source3/smbd/smb2_server.c:2635
[2020/04/23 14:03:17.523861,  3]
../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
status[NT_STATUS_SHARING_VIOLATION] || at ../../source3/smbd/smb2_create.c:334
[2020/04/23 14:03:17.525350,  3]
../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
status[NT_STATUS_SHARING_VIOLATION] || at ../../source3/smbd/smb2_create.c:334

Rich
> Sorry it defaulted to sending direct to you - here it is to the list.
> 
>> OS is CentOS 8
>> 
>> I was thinking about the possibility of using the version in the base
repo for
>> the file server since I don't need ADDC for the file server.  I
just need the
>> ability to join.
>> 
>> Here is my configure command that I used to configure the source:
>> 
>> ./configure \
>> --disable-cups \
>> --without-ldb-lmdb \
>> --prefix=/opt/samba \
>> --sysconfdir=/etc/samba \
>> --localstatedir=/var \
>> --with-lockdir=/var/lib/samba/lock \
>> --with-piddir=/run/samba \
>> --with-systemd \
>> --systemd-install-services \
>> --with-logfilebase=/var/log/samba
>> 
>> Nothing really outstanding...
>> 
>> Thanks,
>> Rich
>> 
>> ----- On Apr 23, 2020, at 1:33 PM, samba samba at lists.samba.org
wrote:
>> 
>>> On 23/04/2020 17:58, Rich Webb via samba wrote:
>>>> Hello,
>>>>
>>>> I'm running Samba 4.12.1 both as a domain controller on one
box (DC1) and as a
>>>> joined member on another box for a file server (FS1).
>>>>
>>>> I have three shares on FS1 and intermittently I am getting a
message that says
>>>> "\\fs1\shared is not accessible. You might not have
permissions to use this
>>>> network resource. Contact the administrator of this server to
find out if you
>>>> have access permissions. The process cannot access the file
because it is being
>>>> used by another process."
>>>>
>>>> Now when this is happening on one share it might not be on one
of the other two.
>>>> Sometimes it happens on all of them. This morning I copied a
file over to
>>>> shared and the copy completed but the window didn't update
and the file did not
>>>> show up so I went to refresh the screen and got the error. If I
wait long
>>>> enough or go back and forth between different shares it will
again become
>>>> accessible but when I go to FS1 and restart the smb service I
can again access
>>>> it. It is happening very frequently. Almost every time I want
to use the server
>>>> for something.
>>>>
>>>> Both of these installs were built from source. If you need the
configure
>>>> commands I used I can provide that as well.
>>> Yes please ;-)
>>> 
>>> There is nothing really wrong with your smb.conf files, except I
would
>>> remove the 'winbind enum' lines from FS1, all they really
do is to slow
>>> things down. I would also add 'winbind refresh tickets =
Yes' to FS1.
>>> 
>>> After this, you may have to raise the log level on FS1 to see if
>>> anything pops out.
>>> 
>>> What OS is this ?
>>> 
>>> Rowland
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>> > instructions:  https://lists.samba.org/mailman/options/samba
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

Additional Information:

This is happening on both a Windows 7 client and a Windows 10 client both of
which are joined to the domain.  Seems to be some sort of file locking issue but
it is happening at the share level - before I even attempt to access or write a
file.

On a different server running Samba 4.9.2 and a relatively similar setup (same
build commands but running on CentOS 7) I do not have this issue.
> Ok increased logging and got the error here is what got logged:
> 
> 2020/04/23 14:03:17.514132,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
>  status[NT_STATUS_SHARING_VIOLATION] || at
../../source3/smbd/smb2_create.c:334
> [2020/04/23 14:03:17.514206,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[5]
>  status[NT_STATUS_FILE_CLOSED] || at ../../source3/smbd/smb2_server.c:2635
> [2020/04/23 14:03:17.523861,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
>  status[NT_STATUS_SHARING_VIOLATION] || at
../../source3/smbd/smb2_create.c:334
> [2020/04/23 14:03:17.525350,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
>  status[NT_STATUS_SHARING_VIOLATION] || at
../../source3/smbd/smb2_create.c:334
> 
> Rich
> 
>> Sorry it defaulted to sending direct to you - here it is to the list.
>> 
>>> OS is CentOS 8
>>> 
>>> I was thinking about the possibility of using the version in the
base repo for
>>> the file server since I don't need ADDC for the file server.  I
just need the
>>> ability to join.
>>> 
>>> Here is my configure command that I used to configure the source:
>>> 
>>> ./configure \
>>> --disable-cups \
>>> --without-ldb-lmdb \
>>> --prefix=/opt/samba \
>>> --sysconfdir=/etc/samba \
>>> --localstatedir=/var \
>>> --with-lockdir=/var/lib/samba/lock \
>>> --with-piddir=/run/samba \
>>> --with-systemd \
>>> --systemd-install-services \
>>> --with-logfilebase=/var/log/samba
>>> 
>>> Nothing really outstanding...
>>> 
>>> Thanks,
>>> Rich
>>> 
>>> ----- On Apr 23, 2020, at 1:33 PM, samba samba at lists.samba.org
wrote:
>>> 
>>>> On 23/04/2020 17:58, Rich Webb via samba wrote:
>>>>> Hello,
>>>>>
>>>>> I'm running Samba 4.12.1 both as a domain controller on
one box (DC1) and as a
>>>>> joined member on another box for a file server (FS1).
>>>>>
>>>>> I have three shares on FS1 and intermittently I am getting
a message that says
>>>>> "\\fs1\shared is not accessible. You might not have
permissions to use this
>>>>> network resource. Contact the administrator of this server
to find out if you
>>>>> have access permissions. The process cannot access the file
because it is being
>>>>> used by another process."
>>>>>
>>>>> Now when this is happening on one share it might not be on
one of the other two.
>>>>> Sometimes it happens on all of them. This morning I copied
a file over to
>>>>> shared and the copy completed but the window didn't
update and the file did not
>>>>> show up so I went to refresh the screen and got the error.
If I wait long
>>>>> enough or go back and forth between different shares it
will again become
>>>>> accessible but when I go to FS1 and restart the smb service
I can again access
>>>>> it. It is happening very frequently. Almost every time I
want to use the server
>>>>> for something.
>>>>>
>>>>> Both of these installs were built from source. If you need
the configure
>>>>> commands I used I can provide that as well.
>>>> Yes please ;-)
>>>> 
>>>> There is nothing really wrong with your smb.conf files, except
I would
>>>> remove the 'winbind enum' lines from FS1, all they
really do is to slow
>>>> things down. I would also add 'winbind refresh tickets =
Yes' to FS1.
>>>> 
>>>> After this, you may have to raise the log level on FS1 to see
if
>>>> anything pops out.
>>>> 
>>>> What OS is this ?
>>>> 
>>>> Rowland
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> To unsubscribe from this list go to the following URL and read
the
>>> > instructions:  https://lists.samba.org/mailman/options/samba
>> 
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

Same here, I had also wrote to the mailing list,
2 Customers has the same issue after upgrading to 4.12
Windows Clients get the error ?another prosscess is in use? or ?wrong handle?
when a user try to open a network share.
After restart samba it?s working for a little moment but mostly not.

We?re using Debian 10 Buster and Samba Version is:
Version 4.12.1-SerNet-Debian-5.buster

Von: samba <samba-bounces at lists.samba.org>
Datum: Donnerstag, 23. April 2020 um 20:26
An: samba <samba at lists.samba.org>
Betreff: Re: [Samba] Share inaccessible intermittently and often - restarting
smb cures for short time
Additional Information:

This is happening on both a Windows 7 client and a Windows 10 client both of
which are joined to the domain.  Seems to be some sort of file locking issue but
it is happening at the share level - before I even attempt to access or write a
file.

On a different server running Samba 4.9.2 and a relatively similar setup (same
build commands but running on CentOS 7) I do not have this issue.
> Ok increased logging and got the error here is what got logged:
>
> 2020/04/23 14:03:17.514132,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
>  status[NT_STATUS_SHARING_VIOLATION] || at
../../source3/smbd/smb2_create.c:334
> [2020/04/23 14:03:17.514206,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[5]
>  status[NT_STATUS_FILE_CLOSED] || at ../../source3/smbd/smb2_server.c:2635
> [2020/04/23 14:03:17.523861,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
>  status[NT_STATUS_SHARING_VIOLATION] || at
../../source3/smbd/smb2_create.c:334
> [2020/04/23 14:03:17.525350,  3]
> ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex)
>  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
>  status[NT_STATUS_SHARING_VIOLATION] || at
../../source3/smbd/smb2_create.c:334
>
> Rich
>
>> Sorry it defaulted to sending direct to you - here it is to the list.
>>
>>> OS is CentOS 8
>>>
>>> I was thinking about the possibility of using the version in the
base repo for
>>> the file server since I don't need ADDC for the file server.  I
just need the
>>> ability to join.
>>>
>>> Here is my configure command that I used to configure the source:
>>>
>>> ./configure \
>>> --disable-cups \
>>> --without-ldb-lmdb \
>>> --prefix=/opt/samba \
>>> --sysconfdir=/etc/samba \
>>> --localstatedir=/var \
>>> --with-lockdir=/var/lib/samba/lock \
>>> --with-piddir=/run/samba \
>>> --with-systemd \
>>> --systemd-install-services \
>>> --with-logfilebase=/var/log/samba
>>>
>>> Nothing really outstanding...
>>>
>>> Thanks,
>>> Rich
>>>
>>> ----- On Apr 23, 2020, at 1:33 PM, samba samba at lists.samba.org
wrote:
>>>
>>>> On 23/04/2020 17:58, Rich Webb via samba wrote:
>>>>> Hello,
>>>>>
>>>>> I'm running Samba 4.12.1 both as a domain controller on
one box (DC1) and as a
>>>>> joined member on another box for a file server (FS1).
>>>>>
>>>>> I have three shares on FS1 and intermittently I am getting
a message that says
>>>>> "\\fs1\shared is not accessible. You might not have
permissions to use this
>>>>> network resource. Contact the administrator of this server
to find out if you
>>>>> have access permissions. The process cannot access the file
because it is being
>>>>> used by another process."
>>>>>
>>>>> Now when this is happening on one share it might not be on
one of the other two.
>>>>> Sometimes it happens on all of them. This morning I copied
a file over to
>>>>> shared and the copy completed but the window didn't
update and the file did not
>>>>> show up so I went to refresh the screen and got the error.
If I wait long
>>>>> enough or go back and forth between different shares it
will again become
>>>>> accessible but when I go to FS1 and restart the smb service
I can again access
>>>>> it. It is happening very frequently. Almost every time I
want to use the server
>>>>> for something.
>>>>>
>>>>> Both of these installs were built from source. If you need
the configure
>>>>> commands I used I can provide that as well.
>>>> Yes please ;-)
>>>>
>>>> There is nothing really wrong with your smb.conf files, except
I would
>>>> remove the 'winbind enum' lines from FS1, all they
really do is to slow
>>>> things down. I would also add 'winbind refresh tickets =
Yes' to FS1.
>>>>
>>>> After this, you may have to raise the log level on FS1 to see
if
>>>> anything pops out.
>>>>
>>>> What OS is this ?
>>>>
>>>> Rowland
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> To unsubscribe from this list go to the following URL and read
the
>>> > instructions:  https://lists.samba.org/mailman/options/samba
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba