Re: (ASCEND) Fatal Index: 2

[Jason Nealis <nealis@babylon.erols.com>]

 From what I remember Fatal Error #2's usually meant some sort of memory
leak, or allocation error. From time to time do a pools -v to see if your
box is loosing memory.

Jason Nealis
Director Internet Operations / Network Access
Erols Internet


On Sun, 3 May 1998, Brett Hawn wrote:

> Today one of our Ascend 4004 boxes went into a reboot cycle and when we
> finally got into the beastie this is what our fatal error log showed. I'm
> not entirely sure what Index: 175 and Index: 2 are.. any ideas?
> 
> 
> WARNING:  Index: 175  Load: tik.m40 Revision: 5.0Ap36        Date:
> 05/03/1998.       Time: 15:23:39        Location: b0079bf0 b010fcec b0116c6c
> b010eb74 b0207ef0 b00ce968
> 
> FATAL ERROR:  Index: 2  Load: tik.m40 Revision:
> 5.0Ap36        Date: 05/03/1998.       Time: 15:24:29        Location:
> b018001c b011c730 b01e0950 b01eb0f8 b01e9e78 b01e0afc
> 
> SYSTEM IS UP:  Index:
> 100  Load: tik.m40 Revision: 5.0Ap36        Date: 05/03/1998.       Time:
> 15:27:18
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:	<http://www.nealis.net/ascend/faq>
> 

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

References:

• (ASCEND) Fatal Index: 2
• From: Brett Hawn <blh@staff.texas.net>

---

• Prev by Date: (ASCEND) NAT works! but not through RADIUS
• Next by Date: Re: (ASCEND) user passwords in radius file (fwd)
• Prev by thread: (ASCEND) Fatal Index: 2
• Next by thread: (ASCEND) NAT works! but not through RADIUS
• Index(es):
  • Main
  • Thread