Alpha 8.3 SAMBA CIFS V1.1 ECO1 PS9 errors

[Peter Barkas]

Running simple standalone server with share security accessed primarily by W2008 server.

Periodically (6 times in the last 61 days) these errors are logged and the W2008 server loses connection. The W2008 server is able to restablish connection later without restarting SAMBA CIFS.

[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend
[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend
[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend
[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.NSSWITCH]WINBINDD_PASSDB.C;1:(129)
Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend
[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.SMBD]SERVICE.C;1:(1009)
'/SAMBA$ROOT/TMP' does not exist or permission denied when connecting to [IPC$] Error was no such file or directory
[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.SMBD]SERVICE.C;1:(188)
chdir (dsa203:[jetform]) failed
[2010/04/26 01:06:59, 0] SAMBA$SRC:[SOURCE.SMBD]SERVICE.C;1:(188)
chdir (dsa203:[jetform]) failed
[2010/04/26 01:06:59, 0] SAMBA$SRC:[SOURCE.SMBD]SERVICE.C;1:(188)
chdir (dsa203:[jetform]) failed
[2010/04/26 01:07:12, 0] SAMBA$SRC:[SOURCE.SMBD]SERVICE.C;1:(188)
chdir (dsa203:[jetform]) failed

Config:

[global]
workgroup = PHBWORLD
server string = Samba %v running on %h (OpenVMS)
netbios name = HERKRO
security = SHARE
; hosts allow = 10.
guest account = jetformscif
log file = /samba$root/var/log_%h.%m
load printers = No
printcap name = /dev/null
ldap ssl = no
# supposedly not required if winbind is not used but errors are logged if not specified:
idmap uid = 15000-20000
idmap gid = 15000-20000
;
inherit owner = Yes
inherit vms rms protections = Yes
guest only = Yes
guest ok = Yes
vms rms format = streamlf
vfs objects = varvfc
[JF]
path = dsa203:[jetform]
read only = No
vms ods5 volume = No
hosts allow = 10.5.20.45,10.5.20.46,10.5.20.20

[JFIN]
path = dsa607:[jetform]
read only = No
vms ods5 volume = Yes
hosts allow = 10.5.20.46,10.5.20.45,10.5.20.20

[JFR]
path = dsa203:[jetform]
read only = Yes
vms ods5 volume = No
hosts allow = 10.

[JFRIN]
path = dsa607:[jetform]
read only = Yes
vms ods5 volume = Yes
hosts allow = 10.

[P Muralidhar Kini]

Hi Peter,

This looks similar/related to one of your previous posts.
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1400607

Is it?

Regards,
Murali

[Peter Barkas]

Murali thank you for the response.

The problem is similar insofar as the Winbind errors are still being logged.

However, that is not the concern here.

When this error is logged, the W2008 server is (temporarily) unable to connect to the share and this causes the remote application to fail:

[2010/04/26 01:06:54, 0] SAMBA$SRC:[SOURCE.SMBD]SERVICE.C;1:(1009)
'/SAMBA$ROOT/TMP' does not exist or permission denied when connecting to [IPC$] Error was no such file or directory

[P Muralidhar Kini]

Hi Peter,

>> '/SAMBA$ROOT/TMP' does not exist or permission denied when connecting
>> to [IPC$] Error was no such file or directory
Just to rule out any obvious errors, I hope the directory exists and has the
required permissions for access.

>> When this error is logged, the W2008 server is (temporarily) unable
>> to connect to the share and this causes the remote application to fail:
This seems to suggest when the server tries to connect to the
share again, it succeeds.
So the problem occurs with the directory but not always. Is that correct ?

Is the problem seen with the same directory always or with different
directories also ?

Regards,
Murali

[Peter Barkas]

Murali, thank you for the response.

Yes, most of the time the share works as expected and the error has happened only 6 times during 61 days.

The share is accessed every day albeit fairly infrequently as it is being used in a test environment until this problem is resolved.

The error has been logged only for the TMP directory.

[P Muralidhar Kini]

Hi Peter,

>> The error has been logged only for the TMP directory.
This makes me believe that the problem has something to do with the way
the TMP directory is accessed.

>> The share is accessed every day albeit fairly infrequently as it is
>> being used in a test environment until this problem is resolved.
Need to know how the TMP directory is accessed.
One possibility is if there is some other accessor of the directory who
may be deleting the directory while others are still accessing it.

How is the directory TMP accessed
- Multiple or single accessors ?
- What kind of operations do each accessor perform on the directory?
- Do any of accessor delete/rename the directory?

When the remote application reties after failure, is the directory TMP
empty to start with or does it have some files?

Regards,
Murali

[Peter Barkas]

The TMP directory was created as part of the SAMBA CIFS installation and has not been deleted since then.

It is referenced in
SAMBA$ROOT:[000000.BIN]SAMBA$SMBD_STARTUP.COM

$! Setup tmpdir
$ tmpdir = f$trnlnm("SAMBA$TMPDIR")
$ define TMP 'tmpdir' ! up to 1.9.16p2
$ define TMPDIR 'tmpdir' ! from 1.9.16p3 on (Andrew told me...)

It is not used directly by any of our applications.

I have never seen a file in the TMP directory.

$ sho log samba$tmpdir/fu
"SAMBA$TMPDIR" [exec] = "SAMBA$ROOT:[TMP]" (LNM$SYSTEM_TABLE)
$

[P Muralidhar Kini]

Hi Peter,

>> The TMP directory was created as part of the SAMBA CIFS installation
>> and has not been deleted since then.
This rules out any problem that may arise due to mutiple access to the
TMP directory.

>> I have never seen a file in the TMP directory.
This is strange. I thought this directory might get used to store some
temporary files at times.

Looks now like its a problem with the permissions associated with the
'/SAMBA$ROOT/TMP' directory.
Similar kind of problem discussed here -
http://www.linuxquestions.org/questions/linux-software-2/samba-share-problems-ipc$-343263/

Regards,
Murali

[Peter Barkas]

Murali

Yes, I saw that posting, however, it seems odd that the error occurs only periodically and that the share works at other times.

Also, the protection on the directory is w:rwed.

Directory SAMBA$ROOT:[000000]

TMP.DIR;1 [COMPUTER,SYSTEM] (RWED,RWED,RWED,RWED)
(DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWED)

[Peter Barkas]

The other thing that I have noticed is that all 6 errors have occurred between 01:00 and 07:30.

It is extremely unlikely that file transfers are in progress in the test environment at these times.

There may be various housekeeping activities that run overnight, however, it is not clear why these might trigger this type of error.