| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 308.1 | | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Thu Mar 27 1997 16:18 | 6 |
| One of the I18N message routines got called with a message
type of 1355432, which isn't used and a message number of
2132691368, which also isn't used. Either you stumbled upon
a bug for some message or have a very sick system.
What version of MRU are you running?
|
| 308.2 | | SSDEVO::ROLLOW | Dr. File System's Home for Wayward Inodes. | Thu Mar 27 1997 22:30 | 6 |
| The operating system and version would also be useful. If
UNIX, is LANG defined? Since the robot has 12 drives, when
you say "multi-lsm" I assume you MUSL (multi-unit, single
LUN). The values of other MRU_ logical/environment variables
might also be useful. Finally, just to see if the robot
if the robot appears well behaved, the output of "robot show robot".
|
| 308.3 | More Information.... | CX3PST::BSS::SAUL | | Fri Mar 28 1997 10:07 | 36 |
| Sorry, should have given you more information. This is a Alpha Server 8400 running
VMS 6.2-1h3. MRU is version 1.1. I believe MUSL is the correct term here. Its 4
TL820's tied together and we access it through $5$DUA999. Since these configurations
are rather new, I'd expect this may be a bug that has never been run into before.
Ted
STNDBY=>SHOW LOG MRU*
(LNM$PROCESS_TABLE)
(LNM$JOB_87219DC0)
(LNM$GROUP_000001)
(LNM$SYSTEM_TABLE)
"MRU_LOG" = "SLS$ROOT:[MRU]MRU.LOG"
"MRU_ROBOT" = "$5$DUA999:"
"MRU_UNLOAD_DELAY" = "10"
"MRU_WAIT" = "120"
STNDBY=>ROBOT SHOW ROBOT
Message out of range for type 1352232: 2132691368.
Robot Name: $5$DUA999: Type: SCSI
Media Robot Identifier: DEC TL820 (C) DEC2A5A
Slots: 1056
Drives: 12
Inports: 1
Outports: 1
Transports: 5
|
| 308.4 | | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Fri Mar 28 1997 11:29 | 11 |
| We help qualify the MUSL code, so it isn't a bug there. Since
the other things work fine, my first guess is that MRU is trying
to write the messages to the log, failing and then printing an
error for that which is using bad arguments to the I18N code.
As a quick check, deassign MRU_LOG and retry the commands. If
the message doesn't appear that will help me narrow it down
quickly.
Also, check that log file is writeable. And if doesn't exist
create it. We should have, but that may be a sufficient work-
around.
|
| 308.5 | | CX3PST::BSS::SAUL | | Fri Mar 28 1997 13:57 | 4 |
| Sure enough, the log file directory did not exist. I created it and the error
went away. Thanks for your help.
Ted
|
| 308.6 | | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Fri Mar 28 1997 17:26 | 3 |
| By virtue of my putting an "OP:MED" on this note, we'll fix it
in V1.2. If the customer would like it fixed before then, submit
an IPMT case.
|
| 308.7 | Closing, closing... | COOKIE::MRU | | Sun Mar 30 1997 01:10 | 3 |
| Well, V1.2 will have the fix and it was certainly a stupid bug...
I was using the wrong message (out_of_range) for an fopen failure
(correct message was cant_open).
|
| 308.8 | Close. | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Mon Apr 14 1997 12:02 | 0
|