Forum Discussion
Check this out, might be the same thing:
http://www.symantec.com/docs/TECH191292
Also, I've had similar where the installation was interrupted for some reason and the java security file got corrupted.
- Verify whether the appliance hostname is correct in the security certificate file:
In the example below the appliance real hostname is missing, say the real hostname is 'abc', the hostname indeed appears as the appliance default name nb-appliance:
/opt/SYMCnbappws/Security # strings keystore
netbackupapplianceui
nb-appliance1
NetBackupApplianceUI1
nb-appliance0
nb-appliance1
NetBackupApplianceUI1
nb-appliance0
- Save the original security certificate file:
/opt/SYMCnbappws/Security # cp keystore keystore.org
- Stop appliance webserver services:
/opt/SYMCnbappws/bin # sh /opt/SYMCnbappws/bin/appwebadmin.sh stop
Stopping NetBackup Appliance Web Server
Stopping NetBackup Appliance Web Server Service
Stopping Authentication Service
- Make sure the appliance webserver services are down:
/opt/SYMCnbappws/bin # sh /opt/SYMCnbappws/bin/appwebadmin.sh monitor
Authentication service is down
Private Branch Exchange service is up
NetBackup Appliance Web Server is down
- Generate a new certificate:
/opt/SYMCnbappws/Security # /usr/java/latest/bin/keytool -genkeypair -alias NetBackupApplianceUI -keyalg RSA -keypass appliance -validity 3650 -dname "CN=<appliance hostname>, ou=NetBackupApplianceUI, o=<appliance hostname>" -storepass appliance -keystore /opt/SYMCnbappws/Security/keystore
- Now view the security certificate file, this time appliance hostname 'abc' should be present:
/opt/SYMCnbappws/Security # strings keystore
netbackupapplianceui
abc1
NetBackupApplianceUI1
abc0
abc1
NetBackupApplianceUI1
abc0
- Start appliance webserver services:
sh /opt/SYMCnbappws/bin/appwebadmin.sh start
- Login to the appliance WEB UI now should be successful.
Related Content
- 4 months ago