[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
|
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
221.0. "OAMTIERR.LOG problems." by KERNEL::LOAT (Bored....Bored....BORED!!!!) Thu Mar 12 1992 17:15
VMS 5.4-2 ALL-IN-1 2.4 (EASE system) MR 3.1B
This system cannot send any remote mail. An extract fro the
OAMTIERR.LOG follows (Wide screen is needed to view it.)
ALL-IN-1 Mail Local Sender Error Log.
First Entry 25-FEB-1992 14:13:03.
Date Time File ID Error
25-FEB-1992 14:13:03 %MROUTER-F-PROTOFAIL, Protocol violation !AS
25-FEB-1992 14:13:03 -SYSTEM-F-IVCHAN, invalid I/O channel
25-FEB-1992 14:13:03 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:03 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:03 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:03 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:05 %MROUTER-F-PROTOFAIL, Protocol violation !AS
25-FEB-1992 14:13:05 -SYSTEM-F-IVCHAN, invalid I/O channel
25-FEB-1992 14:13:05 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:05 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:05 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:05 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:06 %MROUTER-F-PROTOFAIL, Protocol violation !AS
25-FEB-1992 14:13:07 -SYSTEM-F-IVCHAN, invalid I/O channel
25-FEB-1992 14:13:07 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:07 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:07 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:07 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:08 %MROUTER-F-PROTOFAIL, Protocol violation !AS
25-FEB-1992 14:13:08 -SYSTEM-F-IVCHAN, invalid I/O channel
25-FEB-1992 14:13:09 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:09 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:09 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:09 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:10 %MROUTER-F-PROTOFAIL, Protocol violation !AS
25-FEB-1992 14:13:10 -SYSTEM-F-IVCHAN, invalid I/O channel
25-FEB-1992 14:13:11 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:11 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:13:11 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:13:11 -XPO-E-BAD_ADDR, invalid memory address
The old error log included the following...
25-FEB-1992 08:45:30 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 10:15:48 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 10:30:52 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 10:45:55 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 11:46:08 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 12:16:15 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 14:12:53 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 14:12:53 %EMD-E-UNRECMBX, mailbox not recognized A1_DUST;FREDDIE
25-FEB-1992 14:12:55 %MROUTER-F-PROTOFAIL, Protocol violation !AS
25-FEB-1992 14:12:55 -SYSTEM-F-IVCHAN, invalid I/O channel
25-FEB-1992 14:12:55 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:12:55 -XPO-E-BAD_ADDR, invalid memory address
25-FEB-1992 14:12:55 %XPO-E-FREE_MEM, dynamic memory deallocation error
25-FEB-1992 14:12:56 -XPO-E-BAD_ADDR, invalid memory address
Any ideas what could causing these problems?
Steve.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 221.1 | One possible solution | EEMELI::SALMINEN | Hannu Salminen, PTG -Finland | Wed Apr 22 1992 14:02 | 23 |
| A week ago I helped our local IS with the same error message
"MROUTER-F-POROTOFAIL" which I have not seen before.
We have VMS 5.5A ALL-IN-1 2.4 and MR 3.2
When running ALL-IN-1 Sender the session crashed to DCL-level.
This seemed to happen when dealing mail to one certain account.
This user account had an automatic forward address, which caused
infinite loop because it pointed to the MRMAN Replacement
entry of the same user, which pointed back to his ALL-IN-1
account. Removing this forward address and trying to run Sender
many times the problem vanished (or it was one of these Strange
things happening depending of the position of the stars ;-> )
Anyhow I wrote a TIMA/STARS article, will see whether the PFE
accepts it. Only other article of this error message was one
which reported that a bad disk (NBS directory area) can cause
this message.
(Trouble)shooting into dark, regards
Hannu
|
| 221.2 | | NCBOOT::HARRIS | oooppps | Tue Sep 15 1992 23:41 | 15 |
| i was wondering if anyone knew what these errors mean. from the
oa$mti_err. the day before the errors (9.13) vms was upgraded to 5.5-1
also, the error messages were viewed at 9:30AM, but the time on them
says 10:09AM !
14-SEP-1992 10:09:41 %SYSTEM-F-ACCVIO, access violation,
reason mask=04, virtual address=00000000, pc=7fec3698
PSL=00000000
14-SEP-1992 10:09:41 %SYSTEM-F-ACCVIO, access violation,
reason mask=04, virtual address=00000000, pc=oo140dfd
PSL=20000000
14-SEP-1992 10:09:42 %SYSTEM-F-ACCVIO, access violation,
reason mask=04, virtual address=00000000, pc=00138c98
PSL=000AEB67
|
| 221.3 | Just guessing | SCOTTC::MARSHALL | Do you feel lucky? | Wed Sep 16 1992 11:42 | 19 |
| Hi,
>> i was wondering if anyone knew what these errors mean
They mean that the sender or fetcher crashed. Unfortunately, that's about all
they tell you.
The most commone cause of crashes is corrupt, or weird format, mail messages
arriving on the system. Are there any NBS files created at that time still
in the MR$NBS directories? If so, look (or get someone who knows about the
NBS file format to look) and see if there's anything unusual about them
($ run mb$tools:mrnbsdmp is the beasty you need).
As for the discrepancy in time... when you say 9:30, is that from someone
looking at their watch, or from checking the system time. It's possible that
the system time, and hence the time in the error log, was wrong (particularly
if it had been incorrectly set after the upgrade).
Scott
|
| 221.4 | | IOSG::WDAVIES | There can only be one ALL-IN-1 Mail | Fri Sep 18 1992 11:47 | 12 |
| Or silly things like RMS errors on SDAFs and things...
Its better in V3.0!
Incidentally, if you can back trace it, check that no-one got messages
mixed up - sometimes if the sender crashes, a mail message can pickup
a previous ones address list.... Check out that the SINGLE piece of
mail sent AFTER each crash was delivered to the correct destination.
This procedure isn't neccessary with 3.0
Winton
|