[j-nsp] Strange crash on backup RE after 240 days?
Sean Crandall
sean at megapath.net
Tue Jan 25 11:49:31 EST 2005
Hello Phil,
We had an issue like what you were talking about also. The crashing
turned out to be happening more than we thought. We were running the
6.2 train of code at the time. For us, we could see which routers were
affected because /var/crash was filled up core dump files on that backup
RE. We eventually found there was a fix in 6.3R2.2. Things have been
stable since then.
-Sean
Sean P. Crandall
VP Engineering Operations
MegaPath Networks Inc.
6691 Owens Drive
Pleasanton, CA 94588
(925) 201-2530 (office)
(925) 201-2550 (fax)
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> Phil Rosenthal
> Sent: Tuesday, January 25, 2005 12:44 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Strange crash on backup RE after 240 days?
>
> After 240 days of uptime, the backup RE on an M20 seemed to have
> crashed on it's own:
>
> Jan 25 03:04:58 25b-6-m20-1 /kernel: WARNING: / was not properly
> dismounted
> Jan 25 03:04:58 25b-6-m20-1 savecore: Router crashed.....
> Jan 25 03:04:58 25b-6-m20-1 savecore: reboot after panic:
> rnh_index_alloc: nhindex 670 could not be allocated
> Jan 25 03:04:58 25b-6-m20-1 savecore: system went down at Tue Jan 25
> 03:02:12 2005
> Jan 25 03:04:58 25b-6-m20-1 savecore: Selective dump will be
> saved now
>
> At the time window in question, no one was logged into the juniper
> (either RE).
>
> Anyone see anything like that before?
>
> --Phil Rosenthal
> ISPrime, Inc.
>
More information about the juniper-nsp
mailing list