T.R | Title | User | Personal Name | Date | Lines |
---|
2371.1 | | OSOSPS::KAGEYAMA | Trust, but Verify | Fri Jan 10 1997 00:40 | 7 |
2371.2 | I supose you are right... | VAXRIO::MAURO | | Fri Jan 10 1997 10:21 | 5 |
2371.3 | | BSS::JILSON | WFH in the Chemung River Valley | Fri Jan 10 1997 14:20 | 6 |
2371.4 | IPMT? | VAXRIO::MAURO | | Mon Jan 13 1997 10:20 | 11 |
2371.5 | | BSS::JILSON | WFH in the Chemung River Valley | Mon Jan 13 1997 12:51 | 4 |
2371.6 | no graph, but CPU is mostly idle | OSOV03::KAGEYAMA | I Got Rhythm | Fri Apr 25 1997 04:36 | 15 |
|
re>.4 -< IPMT? >-
Are there any progress in this problem?
> I supose this is the problem you think it is. I got the DUMP_CPU and
> when the problem happens the "Uptime in Seconds" goes from 120 until
> 480, with no idle time in these periods.
I got the no graph period which caused by the record whose uptime is
1270 seconds while the idle time is 96.2%. It looks like the CPU is not
saturated in my case. Hmmm... Raise an IPMT? DC version is V2.2-50
instead of -51.
- Kazunori
|
2371.7 | | BSS::JILSON | WFH in the Chemung River Valley | Fri Apr 25 1997 12:44 | 4 |
| Do the IPMT and include the records immediately before and after the long
record (so just 3 records) and be prepared to supply the entire CPD file.
Jilly
|
2371.8 | Probably audit server suspension | OSOV03::KAGEYAMA | I Got Rhythm | Mon Apr 28 1997 04:48 | 11 |
|
re>.-1
Thanks, Jilly.
I've found out my problem was caused by the audit server. There were
messages in the OPERATOR.LOG referring to the insufficent disk space,
RESCRITICAL. And there's a coincidence of regain of free space and PSDC
records got to normal.
- Kazunori
|