| 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 |
Hi ,
a customer of mine is complaining about a Polycenter Console Manager behaviour .
First of all his software version products :
Digital Unix , V3.2a
Polycenter Console Manager , V1.6 and patch 311 installed
And now the behaviour:
When he selects "EXTRACT/REVIEW" PCM function (using graphic interface of PCM),
the 2 processes generated by the above function take 90% of CPU . The size of
file where the informations should be contained remains 0 .
Here is how the above mentionated processes are seen with "ps -ax" command:
/usr/opt/VCR160/bin/OSF/console_extract -s 9705071138 -b 9705091138
-o /tmp/pippo -tt node_name
sh -c /usr/opt/VCR160/bin/OSF/console_extract -s 9705071138 -b 9705091138
-o /tmp/pippo -tt node_name
has anyone ever face this behaviour/problem ?
Could anyone give me any tip to find out the cause of the behaviour/problem ?
Many thanks in advance
Regards
Paolo
(CSC, Milan)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1531.1 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri May 09 1997 11:54 | 11 | |
I'd bet the .EVENTS file for the system in question has some "junk"
between two real event records. I have seen this problem on VMS systems
occasionally but not with ECO 4. You might want to do a
console -v (I think thats the switch anyway. On VMS it's CONSOLE
VERIFY). This is will analyze the logfile set for any particular node
or all nodes. The solution will probably require that you shutdown
pcm, rename the logfile sets for the node in question and then restart
PCM so that it can create new logfiles.
REgs,
Dan
| |||||
| 1531.2 | processes created by EXTRACT take 90% of cpu | MLNCSC::ZAGHI | Fri May 30 1997 08:41 | 23 | |
Hi Dan,
First of all , excuse me for the late of this reply .
>>You might want to do a console -v
We tried the above command but no problems were found
>>The solution will probably require that you shutdown
>>pcm, rename the logfile sets for the node in question and then restart
>>PCM so that it can create new logfiles.
We applied the above advice too , but the problem remain.
Moreover we installed V1.6-312 patch , but the problem remain.
Do you have any other tip ?
Many thanks too
Paolo Zaghi
| |||||