| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1548.1 | recreate serevr | EVTAI1::GODARD | | Tue Feb 25 1997 10:50 | 6 |
| Delete the server muas$server_000 then create the server
muas$server_000 on each node
==> ALL IS WORKING
Monique
|
| 1548.2 | Same Problem | WOODY::FABBRI | | Wed Feb 26 1997 04:39 | 14 |
| Hi,
This morning we have again the problem on two nodes where we didn't delete and
re-create the muas$server_000.
After re-creating the muas$server_000 everything works well. So I have
recommended to the customer to do the same on all the systems but I'm not able
to explain why .
I have seen this with many customers.
So does somebody have an idea ?
Thank you
Michel
|
| 1548.3 | | KOALA::LAVASH | | Thu Feb 27 1997 07:53 | 19 |
| There is not enough information to completely understand the
problem. To analyze the access violation in the MUAS Server
the information from ANALYZE needs to be provided. Also, were
any errors logged in any of the MUAS log files? Did anything
change recently on the system? How long was this cofiguration
working before the problem occurred?
If this is an issue for your custoemr, I would recommend the
following actions to be taken the next time the problem occurs:
- restart MUAS Servers
- run DMW$COLLECT_INFO.COM
- create a Severity 3 level IPMT and include the saveset as
part of the supporting data. Also include information such
as: How often does the problem occurs?
When did this problem start?
What changed on the system between the time the product
did not see this problem and when the problem started?
-diana
|
| 1548.4 | DMW$COLLECT_ERROR | EVTAI1::GODARD | | Fri Feb 28 1997 09:45 | 55 |
|
Even the DMW$COLLECT_INFO give an ACCESS VIOLATION !!
I'm connected at customer :
@DMW$COLLECT_INFO creates 2 files :
DMW$COLLECT_INFO.DAT and
DMW$COLLECT_INFO.ERROR
but not the save-set.
This is the DMW$COLLECT_INFO.ERROR
%A1MAIL-I-CREATED, []MUAS$CWF_JNL_SNAPSHOT.DAT created
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=06FFFFFC, PC
=8041A004, PS=0000001B
Improperly handled condition, image exit forced.
Signal arguments: Number = 00000005
Name = 0000000C
00000000
06FFFFFC
8041A004
0000001B
Register dump:
R0 = 000000007FBC8000 R1 = 0000000007000000 R2 =
000000007FEBC250
R3 = 0000000007000000 R4 = 0000000000000003 R5 =
0000000000074078
R6 = 0000000000000000 R7 = 0000000000000001 R8 =
000000007FF9C1F8
R9 = 000000007F963660 R10 = 000000007FF9D228 R11 =
000000007FFBE3E0
R12 = 0000000000000000 R13 = 000000007F9F56C8 R14 =
0000000000000000
R15 = 0000000007000000 R16 = 0000000007000000 R17 =
000000007FBC8008
R18 = 0000000000CE8673 R19 = 000000007FBC8818 R20 =
0000000077770000
R21 = 0000000000070000 R22 = FFFFFFFF84180000 R23 =
000000007FBC80E4
R24 = 0000000000000001 R25 = 0000000000000001 R26 =
FFFFFFFF805B8054
R27 = 000000007FB8A8C0 R28 = 0000000000000030 R29 =
000000007F963000
SP = 000000007F962FE0 PC = FFFFFFFF8041A004 PS =
200000000000001B
I create the IPMT and join the 2 files.
Thanks
Monique
|
| 1548.5 | | KOALA::LAVASH | | Mon Mar 03 1997 07:11 | 22 |
| Comment out the lines that are causing the problem.
In this case, it looks like the following group of commands
are causing the problem:
MANAGE WORK_FILE
SNAPSHOT
START []MUAS$CWF_JNL_SNAPSHOT.DAT /NOLOCK
LIST
CANCEL
SPAWN DELETE/NOCONFIRM/NOLOG []MUAS$CWF_JNL_SNAPSHOT.DAT;
Try just commenting out the lines:
SNAPSHOT
and
SPAWN DELETE/NOCONFIRM/NOLOG []MUAS$CWF_JNL_SNAPSHOT.DAT;
If there is still a access violoation, comment out the
other four lines. Make a note of this when submitting the
IPMT case.
-diana
|
| 1548.6 | same problem again | EVTAI1::GODARD | | Fri Mar 21 1997 11:08 | 11 |
| The same problem reappears... the customer must recreated the server on
5 nodes.
the ECSO is logged n0 7381
When the problem appears on one node, the situation seems to
deteriorate on several nodes..
The customer have noticed the problem appears on ALPHA
thanks for help
Monique
|