VERITAS Volume Manager Storage Administrator (VMSA) server produces the following error: "JNI panic: JNI received a null class"
Starting VERITAS VMSA Server Thu Sep 27 10:05:33 BST 2001 security enabled rebinding .... rebound file://spatula:2410/vrts.remote.vrtsServer JNI panic: JNI received a null class at vrts.remote.disk.UnixDevices.(UnixDevices.java:321)
VMSA server terminates right after it is started:
Starting RMI Registry Starting VMSA Command Server Starting VMSA Server VERITAS VMSAServer terminated. Stopping VMSA Server 29299 Terminated
and /var/opt/vmsa/logs/server_log contains the following error messages:
Starting VERITAS VMSA Command Server Thu Sep 27 10:05:32 BST 2001 Starting VERITAS VMSA Server Thu Sep 27 10:05:33 BST 2001 security enabled rebinding .... rebound file://spatula:2410/vrts.remote.vrtsServer JNI panic: JNI received a null class at vrts.remote.disk.UNIXDevices.<clinit>(UnixDevices.java:321) at vrts.remote.vm.VxvmServices.getVxvmServices(Compiled Code) at vrts.remote.vm.db.VxvmDB.getVxvmServices(Compiled Code) at vrts.remote.vm.db.VxvmDB.getVoldVersion(Compiled Code) at vrts.remote.vm.db.VxvmDB.getVxvmDB(Compiled Code) at vrts.remote.VMServerImpl.getvmserverimpl(Compiled Code) at vrts.remote.VMServerImpl.main(Compiled Code)
This problem has been observed on systems where:
1. the previous VMSA package (VRTSvmsa) was not removed prior to upgrading 2. some older files are still in /opt/VRTSvmsa after the removal of VRTSvmsa.
To resolve this problem, try the following:
# pkgrm VRTSvmsa\*
Next, check for the existence of /opt/VRTSvmsa. If /opt/VRTSvmsa still exists, then do this:
# mv /opt/VRTSvmsa /opt/VRTSvmsa.orig
Finally, reinstall VRTSvmsa 3.1.1 using pkgadd.
Rate this Article
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.