Conference csc32::consolemanager

Hi,

how do I get the debug procedure running under Digital UNIX?
In VMS its CONSOLE$DEBUG isnt it? I want to see if I can track down their fault
as I am able to dial in a fiddle around.

Thanks,

Ian.

    Ian,
       The environment variable is CONSOLE_DEBUG.
    
    Regs,
      Dan

It turns out that i'd gotten things the wrong way round with patch305 installed
if you try and connect it gives you the message saying CM is not running and the
console -d display zeroes out but the processes are still there.
I have returned the shared memory problem to engineering that this patch was
supposed to fix.

Ian.

Patch307 seems to be showing exactly the same symptoms.
Has anyone actually been able to connect to ANY systems while having patch305 or
307 installed? maybe its something i'm doing wrong?

Ian.

    All of this concerns me very much. My biggest concern is that none of
    these 3xx builds is going through some kind of quality review by a
    3rd party. This includes the V1.6-300 build that was supposed to have
    been the long awaited ECO 3. Based on the last few notes I would say
    that these recent "kits" are causing more problems than they are
    fixing. 
    
    My support team and I are sticking with ECO 2 for the time being. Until
    we get some real direction from CA as to what the quality review
    process will be I and my team are in a "holding pattern".
    
    This is only my $.02 worth. Your mileage may vary.
    
    
    Regards,
        Dan

Ian,

We hope that your problems will disappear when you install
the PATCH307A. It is located on the node ALEXWS in the directory
DISK$PUBLIC:[PCM.UNIX307A].

$ dir ALEXWS::DISK$PUBLIC:[PCM.UNIX_307A]

Directory ALEXWS::DISK$PUBLIC:[PCM.UNIX_307A]

PATCH307A.TAR;1        14540   3-SEP-1996 11:59:01.00  (RWED,RWED,RE,RE)
README.FIRST;3             2   3-SEP-1996 12:02:22.00  (RWED,RWED,RE,RE)

Total of 2 files, 14542 blocks.

Please, install it according to the README.FIRST file and let us know
the results.

Regards,
	Igor.

307A has fixed this problem. Its currently under testing to see if its fixes the
shared memory problem.

thanks guys,

Ian.

307A seems to have introduced another problem.
PCM cannot be started from the command line, the following illustrates the
behaviour:

# console_startup clean

console_startup already running cannot continue



if you fire up the C3 and start it from there it works.


Ian.

by the way, none of the processes are running on the system, i checked this:

# ps auxw | grep cons
root      1205  0.0  0.1  288K  64K console  I  + 16:36:30     0:00.13
/usr/sbin/getty console console vt100
root      1257  0.0  1.3 6.32M 608K ??       I    16:36:59     0:00.20
/usr/bin/X11/dxconsole -geometry 480x150-0-0 -daemon -nobutt
root      1341  0.0  0.4 1.32M 168K ttyp0    S  + 16:41:02     0:00.03 grep cons
# 


# console -d

                       POLYCENTER Console Manager Summary
                                     Totals


Configured Systems:   0 User disabled:   0
Active Systems    :   0 (D:000 P:000 L:000 T:000)   Unreachable: 000
Active Users      :   0 (Connect/Monitor: 000 C3: 000 Event sources: 000)

CM pid ........: 0        <Unknown>        Uptime:   0 00:00:00 (Not Running)
ENS pid .......: 0        <Unknown>        Uptime:   0 00:00:00 (Not Running)

Total bytes ...: 0            (0)
Total lines ...: 0            (0)
Total events ..: 0            (0)
Total actions .: 0            (0)
Active actions : 0                 Failed actions : 0

   Crit: 0  Maj: 0  Min: 0  Warn: 0  Clr: 0  Ind: 0

Ian,

307A could not introduce this problem because it did not changed the
console_startup script.

This message says that console_startup script is already running. It can
occure if for some reason console_startup has been interrupted and
the file /tmp/cm_startup.lk has not been deleted.

We changed the console_startup file. It is located on the node ALEXWS
in the directory DISK$PUBLIC:[PCM.UNIX_307A].

We did the following changes in it:

- It removes the startup lock file ( /tmp/cm_startup.lk ) if the startup
  is interrupted.

- The old console_startup file just killed CM processes
  (consoled and console_ensd) if user choose the 'clean' option.

  Now in the case of the 'clean' the shutdown of the CM is performed.
  If after that, for some reason, there are CM processes running
  these processes will be 'killed' and the CM software will be
  restarted.

Regards,
	Igor.

Thanks Igor,

I think I know what happened. Ive got 307a at a couple of customer sites now and
will report later on how its going.

thanks,

Ian.

So far it looks good :) ... no more shmem problems, console_startup ok,
uid files ok, and reconnect to console after quitting "connect window" ok.

Are there any plans to release an eco3 (DCROSF163) for Digital UNIX ?

Thanks for your help !
  Miguel
[Posted by WWW Notes gateway]

    >Are there any plans to release an eco3 (DCROSF163) for Digital UNIX ?
    
    As soon as the powers that be decide on what the process will be then
    it'll happen. Same problem exists for the existing ECO 3 for
    OpenVMS - it really ins't an "official" kit even today.
    
    Regs,
       Dan