[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

924.0. "osf pcm dies with write error on local socket - interrupted system call 94310" by 42326::COFFEYJ (The Uk CSC Unix Girlie.) Tue Aug 15 1995 06:42



Hi all.... 

I have a customer who has OSF V2.1 and PCM V1.5

He is seeing an increasing occurence of console manager dying off 
and in the log file it says: 

write error on local socket /var/opt/console/tmp/console.ctrl
interrupted system call - console manager shutting down.

I have suggested he may want V1.6 but firstly that doesn't list 
V2.1 as a supported operating system version and secondly he 
would like to know if installing V1.6 is actually going to stop 
console from dying off like this. 

I can't see anyone else having had this error with 1.5 (not noted in here 
anyway) so given the version of O/S I'm tempted to say it's more likely
to be a configuration issue which we should check out anyway (since 
engineering are still providing support/patches for V2.1 it makes it 
arkward for us to refuse to support it because it's an old version).

Has anyone else seen this behaviour on 1.5 or 1.6?

Does it appear to be configuration to anyone else? 

What should the permissions on /var/opt/console/tmp/console.ctrl be?

Will V1.6 install on V2.1 even though it's not SPD listed?

What else can I check that might be interfering with this?


thanks in advance... 

Jo Coffey
unix, uk csc. 
T.RTitleUserPersonal
Name
DateLines
924.142326::COFFEYJThe Uk CSC Unix Girlie.Tue Aug 15 1995 07:0112
Oh incidentally - 

*any* help on this greatly appreciated - 

customer just chased to say he's had to reboot the system 
5 times this morning already and they're not amused. 

They will try to get to upgrade to 3.0 and 1.6 asap but want it 
worked on in the mean time since 1.6 might not fix it!

I'm spinning the 1.6 kit onto a dat as I type... 

924.229067::BUTTERWORTHGun Control is a steady hand.Tue Aug 15 1995 14:5313
    I doubt the 1.6 code will even run on 2.1 as it was built on 3.*. I'm
    not familiar with the problems of downward compatibility on U*x as I am
    on OpenVMS.
    
    Since the customer is experiencing the problem so often what I think
    you should do is define the environment variable CONSOLE_DEBUG to
    
    "IPC,DAEMON" 
    
    export it a restart PCM. We'll get a*lot* more debugging info.
    
    Regs,
      Dan
924.342326::COFFEYJThe Uk CSC Unix Girlie.Wed Aug 16 1995 03:4914
Cheers, 


I'll call him this morning and get him to do that. 

Hopefully V1.6 should arrive with him sometime today and 
we can push him up to V3.0 of the operating system at the 
same time. 


Thanks for the support....  


Jo