[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1448.0. "problems starting any PCM version on 3.2g. any known issues???" by COMICS::HAWLEYI (668 - the neighbour of the beast!) Tue Dec 17 1996 08:02

Does anyone have PCM running successfully under 3.2G of Digital UNIX?
Since my customer upgraded to 3.2G we havent been able to start any of the
daemons. Messages in daemon.log just say that they are exiting with status 100
(normal successful completion?). I'm going to check the other log files but just
wanted to know if there were any known stickies with 3.2G?

We have tried 1.6, ECO 1,2 + patch 308 and there are no lock files in /tmp.

Also, I keep forgetting how to switch debug on (sorry Dan, ive got a memory like
a string vest!) so if anyone can remind me i'd be grateful.

thanks,

Ian Hawley.
T.RTitleUserPersonal
Name		DateLines
1448.1CSC32::BUTTERWORTHGun Control is a steady hand.Tue Dec 17 1996 11:1811
    >Also, I keep forgetting how to switch debug on (sorry Dan, ive got a
    >memory like a string vest!) so if anyone can remind me i'd be grateful.
    
    Define the environment variable CONSOLE_DEBUG to ALL and export it
    depending on what shell your using. You don't ever want to run PCM
    with this logical on for very long as it causes a *LOT* of output. In
    your case it won't matter as it's not staying up for very long anyway.
    
    Oh, and before I forget,  Beers_Ian_Owes_Dan++;
1448.2COMICS::HAWLEYI668 - the neighbour of the beast!Wed Dec 18 1996 03:447
Thanks Dan,

I have written it on my forehead in reverse so that I see it in the mirror every
morning, so i wont forget it in future!

cheers,
Ian.
1448.3fixedCOMICS::HAWLEYI668 - the neighbour of the beast!Tue Jan 28 1997 04:3510
Just for future reference:

this ones sorted. it was a site specific problem. C++ libraries had not been
loaded properly.


cheers,

Ian.