[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

652.0. "PCM internals info needed" by BACHUS::WILLEMSG (Geert Willems MCS-Belgium) Fri Mar 17 1995 15:44


	Hi,

	PCM V1.5 + MUP, OpenVMS VAX V6.1, PSW V2.2.

	Has anyone tested this out ?
	I have a customer that is trying to write an action routine to restart 
	missing processes.
	In his case it's specific for PCM processes(Console Notify, Console Deamon, 
	Console Ctrl 01,...,Console Ctrl 08).
	Polycenter System Watchdog's profile contains the list of processes to monitor 
	and have an action routine associated to restart the process(es).
	
	But there is a problem. The customer claims that when he does a stop/id of
	'Console Daemon' almost every 'Console Ctrl xx' vanishes.
		-->I should suspect that every 'Console Ctrl xx' disappear. These
	           processes are the slaves(children) of 'Console Deamon'.
	The result is that the missing process action routine gets triggered 9 times.
	Of course we can build in some logic to test if the processes aren't already
	restarted and take action on that. But is there a simpler way ?

	Another problem is :
	I have on my system one 'Console Deamon' and 4 'Console Ctrl xx' processes.
	If a kill(via stop/id) one of my 'Console Ctrl xx' processes, all my other
	'Console Ctrl xx' processes and my 'Console Deamon' process vanish.
		-->Is this intended behaviour ?

	Any help/feedback is welcome.

	Thanks in advance.

	Rgds,

	Geert
T.RTitleUserPersonal
Name		DateLines
652.1OSCint v2SUPER7::HUGHESASwimming against the tide @#%*Fri Mar 17 1995 16:256
Geert,

	The OXF module in Oscint v2 allows you to simply and easily create rules that can
	handle this type situation with parent/child processes.

Andy.
652.2strange behaviourBACHUS::WILLEMSGGeert Willems MCS-BelgiumMon Mar 20 1995 09:5810
    
    
    	Hi,
    
    	Is it normal when you stop one of the Console Ctrl xx processes,
    	all the other Console Ctrl xx and also the Console Daemon vanish ?
    
    	Rgds,
    
    	Geert
652.3OPG::PHILIPAnd through the square window...Mon Mar 20 1995 10:4117
Geert,

  Yes, you should never stop one of these, the parent "Console Daemon"
  process will see that it has disappeared and shut down everything else!

  If your customer wants to check for missing processes, what they should
  do is check for one of them missing and if it is, shut the product down
  and restart it.

  Plus, stop/id'ing one of the processes could cause loss of data! I know
  this is unavoidable if the process has hung, but that situation should
  never occur and we would be interested in situations which cause it to
  happen.

Cheers,
Phil
652.4BACHUS::WILLEMSGGeert Willems MCS-BelgiumMon Mar 20 1995 14:1433
    
    
	Hi Phil,
    
>  Yes, you should never stop one of these, the parent "Console Daemon"
>  process will see that it has disappeared and shut down everything else!
 	Including himself(Console Daemon) ?
>  If your customer wants to check for missing processes, what they should
>  do is check for one of them missing and if it is, shut the product down
>  and restart it.
 	Based on what you said, the customer only has to monitor for
    	Console Daemon as missing process.
>  Plus, stop/id'ing one of the processes could cause loss of data! I know
>  this is unavoidable if the process has hung, but that situation should
>  never occur and we would be interested in situations which cause it to
>  happen.
 	He used the STOP/ID for test purpose. Just to see if the action
    	routine in PSW functions.
    
    	Is there an easy way to stop/restart the Console Notify process ?
    	Do we have to stop/restart PCM also when this process disappears ?
    
    	May I conclude : if any PCM process stops, the best way to recover
    			 via a PSW action routine is :
    			 1)CONSOLE SHUTDOWN/NOCONFIRM
    			 2)@SYS$STARTUP:CONSOLE$STARTUP RESTART
    
    	Thanks for your help.
    
    	Rgds,
    
    	Geert
652.5OPG::PHILIPAnd through the square window...Mon Mar 20 1995 17:0529
Geert,

>> 	Including himself(Console Daemon) ?

  yes.

>> 	Based on what you said, the customer only has to monitor for
>>    	Console Daemon as missing process.

  yes.



>>    	Is there an easy way to stop/restart the Console Notify process ?
>>    	Do we have to stop/restart PCM also when this process disappears ?
 
  no, although you could look in the PCM startup.com and use the commands
  there to restart the ENS daemon, after it is restarted, the controller
  daemons should connect to it after their check interval.

>>    	May I conclude : if any PCM process stops, the best way to recover
>>    			 via a PSW action routine is :
>>    			 1)CONSOLE SHUTDOWN/NOCONFIRM
>>    			 2)@SYS$STARTUP:CONSOLE$STARTUP RESTART

  This is the supported mechanism.

Cheers,
Phil