02-27-2019 04:35 PM - edited 02-27-2019 05:04 PM
< Symptom >
Reloading NED packages failed.
root@ncs# packages reload
reload-result {
package alu-sr
result false
info --ERROR--
}
reload-result {
package cisco-iosxr
result false
info --ERROR--
}
reload-result {
package l3vpn
result true
}
reload-result {
package huawei-vrp
result false
info --ERROR--
root@ncs# show packages package oper-status
PACKAGE
PROGRAM META FILE
CODE JAVA BAD NCS PACKAGE PACKAGE CIRCULAR DATA LOAD ERROR
NAME UP ERROR UNINITIALIZED VERSION NAME VERSION DEPENDENCY ERROR ERROR INFO
------------------------------------------------------------------------------------------------------------
alu-sr - - X - - - - - - -
cisco-iosxr - - X - - - - - - -
huawei-vrp - - X - - - - - - -
l3vpn X - - - - - - - - -
< troubleshoot >
After java path was changed by any reason, once the nso restarts, java-vm doesn’t come up with this error msg in the ncs-java-vm.log,
02-28-2019 12:39 PM
Is /usr/local/java/bin in your PATH when you start NSO?
You cannot change the env variables of an already running Linux process.
02-28-2019 03:29 PM
The environment is applied once the process is restarted.
When the NSO started, the /usr/local/java/bin was not in the PATH.
While the NSO was running, someone installed new jdk and the PATH was chagned.
So I restarted the NSO, but the new PATH was not applied.
I think you could reproduce this.
0) in the system installation,
1) remove the /usr/bin/java which should be symbolic link.
2) create the the symbolic link under the other directory which is in the PATH
3) restart the NSO (/etc/init.d/ncs restart)
4) Java VM is not running.
In case of local installation, the Java VM is running.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide