Mailing List Archive

error: the routing subsystem is not running
Could anyone please tell me why am getting the following error?

aj@Karlstadd-re0> show route
error: the routing subsystem is not running

Is there any process I should look for? The show chassis routing-engine output is:
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 32 degrees C / 89 degrees F
DRAM 768 MB
Memory utilization 18 percent
CPU utilization:
User 1 percent
Background 0 percent
Kernel 0 percent
Interrupt 76 percent
Idle 22 percent
Model RE-2.0
Serial ID bf000007c78c6201
Start time 2003-01-13 16:57:25 CET
Uptime 52 days, 19 hours, 45 minutes, 33 seconds
Load averages: 1 minute 5 minute 15 minute
4.89 4.87 4.84
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup (default)
Temperature 25 degrees C / 77 degrees F
DRAM 768 MB
Memory utilization 16 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-2.0
Serial ID 5b0000078e2efb01
Start time 2003-01-13 16:56:48 CET
Uptime 52 days, 19 hours, 43 minutes, 40 seconds
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030307/ff5e96dc/attachment.htm
error: the routing subsystem is not running [ In reply to ]
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGPexch.rtf.pgp
Type: application/octet-stream
Size: 2456 bytes
Desc: not available
Url : http://puck.nether.net/pipermail/juniper-nsp/attachments/20030307/5c5ff0f8/PGPexch.rtf-0001.obj
error: the routing subsystem is not running [ In reply to ]
On Fri, 2003-03-07 at 12:48, Ajay Saini wrote:
> Could anyone please tell me why am getting the following error?
>
> aj@Karlstadd-re0> show route
> error: the routing subsystem is not running

That means your rpd process isn't running, which means you won't be
doing a lot of routing on that box. :)

I don't know what your particular problem is, but I've seen this a
couple of times myself, usually related to JunOS upgrades. One
particular case where this has happened that I have seen several times,
is when upgrading boxes we had running JunOS 4.4 to 5.2. During the
upgrade it seems it sometimes fails to install some .conf file (IIRC it
was /var/etc/cos.conf) properly, and rpd would not start up after the
reboot to new JunOS. This was pretty easy to spot from the router logs
(show log messages), and it was only a matter of starting a shell and
getting this file copied in place correctly to make rpd happy again.

/leg