Server process won't start properly without BYPASS priv

[Art Wiens]

I am trying to setup an environment for Attunity to access a particular datasource. The server process seems to start but fails without the expected results. I am trying to use SET WATCH/CLASS=MAJOR FILE to troubleshoot with and without BYPASS on the process. Without BYPASS, I see this in the logfile:

%XQP, Thread #0, Lookup (81398,22,0) Status: 00000001
%XQP, Thread #0, Access PNO.DAT;194 (81398,22,0) Status: 00000001
%XQP, Thread #0, Lookup PNO.DAT;194 (81398,22,0) Status: 00000001
%XQP, Thread #0, Deaccess (81398,22,0) Reads: 4, Writes: 0, Status: 00000001
error ===> writetcp: failed to write to socket
%XQP, Thread #0, Lookup (2383,1,0) Status: 00000001
%XQP, Thread #0, Lookup (2383,1,0) Status: 00000910
%XQP, Thread #0, Lookup (37,1,0) Status: 00000001
%XQP, Thread #0, Lookup (37,1,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
error ===> writetcp: broken pipe (errno:32)
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
error ===> writetcp: failed to write to socket
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
error ===> writetcp: broken pipe (errno:32)
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910
%XQP, Thread #0, Lookup (0,0,0) Status: 00000910

File (2383,1,0) is SYS$SYSDEVICE:[SYS0]SYS$I18N.DIR;1 and file (37,1,0) is SYS$SYSDEVICE:[VMS$COMMON]SYS$I18N.DIR;1

All files referenced (others weren't listed as they seem to succeed) have at least (W:RE) available to it.

What is (0,0,0) and what is status 910? There doesn't seem to be a file with id 0,0,0 .

Any ideas?

Art

[Robert Brooks_1]

$ exit %x910
%SYSTEM-W-NOSUCHFILE, no such file

[Karl Rohwedder]

DS10_Kalle. she 910
Error 00000910 (%D2320)
%SYSTEM-W-NOSUCHFILE, no such file

regards Kalle

[Art Wiens]

So after further investigation, that's a "red herring", a working process does it too. I found the cause ... the process wasn't able to create a logfile. I didn't think a process needed W:W permission on a parent directory if the subdirectory it was trying to write into had W:RWE permission.

This fails:

$ dir/sec [000000]navroot.dir
Directory SYS$SYSDEVICE:[000000]

NAVROOT.DIR;1 [SYSTEM](RWE,RWED,RE,RE)
Total of 1 file.

$ dir/sec [navroot]tmp.dir
Directory SYS$SYSDEVICE:[NAVROOT]

TMP.DIR;1 [SYSTEM] (RWE,RWE,RE,RWE)
Total of 1 file.

This works:

$ dir/sec [000000]navroot.dir
Directory SYS$SYSDEVICE:[000000]

NAVROOT.DIR;1 [SYSTEM](RWE,RWED,RE,RWE)
Total of 1 file.

$ dir/sec [navroot]tmp.dir
Directory SYS$SYSDEVICE:[NAVROOT]

TMP.DIR;1 [SYSTEM] (RWE,RWE,RE,RWE)
Total of 1 file.

Isn't the W:E on the parent enough to be able to make use of the subdirectory's W:W?

Cheers,
Art

[John Gillings]

Art,

Try leaving BYPASS granted, then use auditing to determine what the process is doing with it.

$ SET AUDIT/AUDIT-
/ENABLE=(ACCESS=BYPASS,PRIVILEGE=SUCCESS:BYPASS)

Once this is set, start your process, then examine the audit journal for entries resulting from activity by that process.

[Karl Rohwedder]

Art,

as you see by the following examples, you did not nead writ access to the parent directory.

Directory CNC_SCRATCH:[ROHW.ROHWEDDER]

TMP.DIR;1 [BO,ROHWEDDER] (RWE,RWE,RE,RE)

Directory CNC_SCRATCH:

1.DIR;1 [BO,ROHWEDDER] (REW,RWE,RE,RWE)

Directory CNC_SCRATCH:

A.A;2 [DECNET,FAL$SRV] (RWED,RWED,RE,)

regards Kalle