[Xorp-users] Starting and Killing xorp_rtrmgr

Pavlin Radoslavov pavlin at icir.org
Tue Jul 24 10:49:11 PDT 2007


> One other question:
> 
> Sometimes I 'quit' xorpsh and send a 'CTRL + d' signal to xorp_rtrmgr to
> kill the process .
> 
> - Is there an other way of killing xorp_rtrmgr ?

Hmmm, "CTRL + c" :)

> Moreover, when I want to start it again, I get the messages : 
> 
> Commit failed: 102 Command failed
> 
> Module killed during shutdown: rip
> Module killed during shutdown: interfaces
> Module killed during shutdown: rib
> .
> 
> And the process does not start .. Until I reboot!
> 
> Is there something I can clean ?

Are there any XORP leftover processes running after you kill
xorp_rtrmgr?

During shutdown the xorp_rtrmgr process should have killed all other
XORP processes, but if any remained please kill them by hand before
restarting XORP. E.g., "kill -9 <pid>" is your safest bet :)
If there are no leftover processes, please check that the loopback
interface is UP and configured. The XORP IPC mechanism uses the
loopback interface so it should be always UP and running.

If none of the above is the issue, then please send your
configuration file, and your complete log messages: the first
message when you run XORP for the first time when you kill the
xorp_rtrmgr and the second message when XORP fails to start.
If they contain any sensitive information that shouldn't go to the
public (e.g., IP addresses, you could mask them because the
particular values shouldn't be related to the
problem. Alternatively, you could send me the info in a private
email.
FYI, to save the log messages it is best to run "script" before
starting XORP in foreground, and then all the printed output will go
to file "typescript".

Regards,
Pavlin



More information about the Xorp-users mailing list