Conference csc32::consolemanager

688.0. "Extract failure from non-priv account" by POLAR::HUTCH (Mike Hutchings, OMS Eastern Canada, Kanata) Fri Apr 21 1995 17:42

 If you attempt an EXTRACT from a non-privileged account, this is what occurs...

 $ console extract/since=today/out=t.t acd_reports

Failed to dearchive log data for system ACD_REPORTS - unable to create temporary
 files

 First thing, the PCM error message is insufficient to easily determine what
 the problem is. How about displaying the reason and maybe even the filename?

 I enabled trace mode (see following) and determined it was a privilege
 violation. Write access was required to the CONSOLE$ARCHIVE directory.
 Is this intentional?

 Mike



POLYCENTER Console Manager
Extract facility Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved

%XQP, Thread #0, Access CONSOLE_CFG.DAT;1 (295,189,0) Status: 00000001
%XQP, Thread #0, Deaccess (295,189,0) Reads: 13, Writes: 0, Status: 00000001
%XQP, Thread #0, Lookup  (446,35,0) Status: 00000001
%XQP, Thread #0, Lookup T.T;5 (446,35,0) Status: 00000001
%XQP, Thread #0, Create/Access T.T;6 (458,31843,0) Status: 00000001
%XQP, Thread #0, Access ACD_REPORTS.TIMES;1 (870,10,0) Status: 00000001
%XQP, Thread #0, Access ACD_REPORTS.EVENTS;1 (871,9,0) Status: 00000001
%XQP, Thread #0, Access ACD_REPORTS.LOG;1 (879,2,0) Status: 00000001
%XQP, Thread #0, Deaccess (870,10,0) Reads: 3, Writes: 0, Status: 00000001
%XQP, Thread #0, Deaccess (879,2,0) Reads: 2, Writes: 0, Status: 00000001
%XQP, Thread #0, Deaccess (871,9,0) Reads: 2, Writes: 0, Status: 00000001
%XQP, Thread #0, Access ARCHIVE.DIR;1 (182,604,0) Status: 00000001
%XQP, Thread #0, Deaccess (182,604,0) Reads: 0, Writes: 0, Status: 00000001
%XQP, Thread #0, Lookup  (1174,10,0) Status: 00000001
%XQP, Thread #0, Access ARCHIVE.DIR;1 (182,604,0) Status: 00000001
.
.
.
%XQP, Thread #0, Access ARCHIVE.DIR;1 (182,604,0) Status: 00000001
%XQP, Thread #0, Deaccess (182,604,0) Reads: 0, Writes: 0, Status: 00000001
%XQP, Thread #0, Lookup  (2379,7,0) Status: 00000001
%XQP, Thread #0, Access ARCHIVE.DIR;1 (182,604,0) Status: 00000001
%XQP, Thread #0, Deaccess (182,604,0) Reads: 0, Writes: 0, Status: 00000001
%XQP, Thread #0, Lookup  (182,604,0) Status: 00000930
%XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
%XQP, Thread #0, Create/Access 32925_ACD_REPORTS_DEARCHIVE.LOG;1 (1143,35,0) Sta
tus: 000003EC
%XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
%XQP, Thread #0, Create/Access 32925_ACD_REPORTS_DEARCHIVE.TIMES;1 (1143,36,0) S
tatus: 000003EC
%XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
%XQP, Thread #0, Create/Access 32925_ACD_REPORTS_DEARCHIVE.EVENTS;1 (1143,37,0)
Status: 000003EC
%XQP, Thread #0, Access ACD_REPORTS.9504040025_TO_9504050025_LOG;1 (2379,7,0) St
atus: 00000001
%XQP, Thread #0, Access ACD_REPORTS.9504040025_TO_9504050025_TIMES;1 (2362,11,0)
 Status: 00000001
%XQP, Thread #0, Access ACD_REPORTS.9504040025_TO_9504050025_EVENTS;1 (2377,8,0)
 Status: 00000001
Failed to dearchive log data for system ACD_REPORTS - unable to create temporary
 files
%XQP, Thread #0, Access ARCHIVE.DIR;1 (182,604,0) Status: 00000001
%XQP, Thread #0, Deaccess (182,604,0) Reads: 0, Writes: 0, Status: 00000001
%XQP, Thread #0, Lookup  (182,604,0) Status: 00000910
%XQP, Thread #0, Deaccess (458,31843,0) Reads: 1, Writes: 0, Status: 00000001
%XQP, Thread #0, Deaccess (2379,7,0) Reads: 1, Writes: 0, Status: 00000001
%XQP, Thread #0, Deaccess (2362,11,0) Reads: 13, Writes: 0, Status: 00000001
%XQP, Thread #0, Deaccess (2377,8,0) Reads: 2, Writes: 0, Status: 00000001

Mike,

  Yes, write access is intentional, however, the way extract works is a
  little inefficient as it tries to build a large temporary file containing
  all the archive and live data which will be reported on!!

  We are working on a new extract which will overcome this problem, this may
  or may not make it into the first FT kit for V1.6, however, it will
  certainly make it into the PCM V1.6 release.

Cheers,
Phil

    Thought I would reply to this note rather than posting a new one.
    
    Anyway , I have a customer experiencing the same problem on a PCM V1.5
    system which he is performing an extract/archive on, however when
    this is done without SYSPRV it gives the usual message :
    
    Failed to dearchive log data for system NODENAME - unable to create
    temporary files
    
    However when SYSPRV is enabled all is o.k, so customer is questioning
    what is going on. I have mentioned the issue with extract working a
    little inefficiently and file sizes, but my customer states the file
    sizes are not big (how big I don't know).
    
    I have told my customer that V1.6 of PCM is the way to go, and to even
    apply ECO2 if need be which he agrees to doing, but he would like a bit
    more on the reason behind this current problem as it has only just
    happened recently on a system he has been running for allmost a year
    now.
    
    Thanks in advance.
    Kevin Symonds
    (CSC - Basingstoke)
                       

    I assume you read the base note and that you need write access to the 
    CONSOLE$ARCHIVE location. Knowing this then I would say that someone
    changed the protection on the directory. PCM doesn't contain the logic
    to do that.
    
    Regs,
      Dan