Troubleshooting

Troubleshooting
Troubleshooting
This chapter provides procedures for troubleshooting the problems encountered during RMS Installation.
• Regeneration of Certificates, page 1
• Deployment Troubleshooting , page 5
Regeneration of Certificates
Following are the scenarios that requires regeneration of certificates:
• Certificate expiry (Certificate will have a validity of one year.)
• If importing certificates are not successful.
Follow the steps to regenerate self-signed certificates:
Certificate Regeneration for DPE
To address the problems faced during the certificate generation process in Distributed Provisioning Engine
(DPE), complete the following steps:
Procedure
Step 1
Remove the root.ca.cer, server.ca.cer and client.ca.cer certificates that are installed in DPE.
Enter:
ssh login to Serving_Node_1
Change to root user
Navigate to the conf folder
cd /rms/app/CSCObac/dpe/conf/
ls -lrt
Output:
[root@blr-rms11-serving conf]# ls -lrt
total 88
RAN Management System Installation Guide, Release 4.0
February 9, 2015
1
Troubleshooting
Certificate Regeneration for DPE
-rwxr-xr-x
-rwxr-xr-x
-rwxr-xr-x
-rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--
1
1
1
1
1
1
1
1
1
1
1
1
1
1
bacservice
bacservice
bacservice
root
root
root
root
root
bacservice
bacservice
admin1
admin1
admin1
bacservice
bacservice 2708 Jan 9 12:57 server-certs
bacservice 3630 Jan 9 12:57 AuthResponse.xsd
bacservice 11760 Jan 9 12:57 AuthRequest.xsd
root
17094 Feb 11 13:53 dpeextauth.jar
root
177 Feb 11 13:53 dpe-genericfemto.properties
root
471 Feb 11 13:53 dpe-femto.properties
root
2932 Feb 11 13:53 dpe-TR196v2.parameters
root
2788 Feb 11 13:53 dpe-TR196v1.parameters
bacservice 1096 Feb 11 13:55 dpe.csr
bacservice 4577 Feb 11 14:00 dpe.properties
ciscorms
1226 Feb 12 06:26 server-ca.cer
ciscorms
819 Feb 12 06:26 root-ca.cer
ciscorms
1626 Feb 12 06:26 client-ca.cer
bacservice 4562 Feb 12 06:28 dpe.keystore
Enter:
rm root-ca.cer
Output:
[root@blr-rms11-serving conf]# rm root-ca.cer
rm: remove regular file `root-ca.cer'? Y
Enter:
rm server-ca.cer
Output:
[root@blr-rms11-serving conf]# rm server-ca.cer
rm: remove regular file `server-ca.cer'? Y
Enter:
rm client-ca.cer
Output:
[root@blr-rms11-serving conf]# rm client-ca.cer
rm: remove regular file `client-ca.cer'? Y
Enter:
ls –lrt
Output:
[root@blr-rms11-serving
total 88
-rwxr-xr-x 1 bacservice
-rwxr-xr-x 1 bacservice
-rwxr-xr-x 1 bacservice
-rw-r--r-- 1 root
-rw-r--r-- 1 root
-rw-r--r-- 1 root
-rw-r--r-- 1 root
-rw-r--r-- 1 root
-rw-r--r-- 1 bacservice
conf]# ls -lrt
bacservice 2708 Jan 9 12:57 server-certs
bacservice 3630 Jan 9 12:57 AuthResponse.xsd
bacservice 11760 Jan 9 12:57 AuthRequest.xsd
root
17094 Feb 11 13:53 dpeextauth.jar
root
177 Feb 11 13:53 dpe-genericfemto.properties
root
471 Feb 11 13:53 dpe-femto.properties
root
2932 Feb 11 13:53 dpe-TR196v2.parameters
root
2788 Feb 11 13:53 dpe-TR196v1.parameters
bacservice 1096 Feb 11 13:55 dpe.csr
RAN Management System Installation Guide, Release 4.0
2
February 9, 2015
Troubleshooting
Certificate Regeneration for DPE
-rw-r--r-- 1 bacservice bacservice
-rw-r--r-- 1 admin1
ciscorms
-rw-r--r-- 1 bacservice bacservice
Step 2
4577 Feb 11 14:00 dpe.properties
1626 Feb 12 06:26 client-ca.cer
4562 Feb 12 06:28 dpe.keystore
Take a backup of old DPE Keystore and CSR:
Enter:
rms/app/CSCObac/dpe/conf/dpe.keystore.bkup
Output:
System returns with command prompt
Enter:
mv /rms/app/CSCObac/dpe/conf/dpe.csr /rms/app/CSCObac/dpe/conf/dpe.csr.bkup
Output:
System returns with command prompt
Step 3
Remove the existing Server and Root ca from cacerts file:
Enter:
/rms/app/CSCObac/jre/bin/keytool -delete -alias server-ca -keystore
/rms/app/CSCObac/jre/lib/security/cacerts
Output:
Enter keystore password:
Enter:
/rms/app/CSCObac/jre/bin/keytool -delete -alias root-ca -keystore
/rms/app/CSCObac/jre/lib/security/cacerts
Output:
Enter keystore password:
Step 4
Regenerate the keystore and CSR for DPE node. Ensure that CN field matches the FQDN or eth1 IP-Address
of DPE).
Enter:
/rms/app/CSCObac/jre/bin/keytool -keystore /rms/app/CSCObac/dpe/conf/dpe.keystore
-alias dpe-key -genkey -keyalg RSA
Output:
Note
The values must be as specified in OVA descriptor
file
Enter keystore password:
Re-enter new password:
What is your first and last name?
[Unknown]: 10.5.2.217
What is the name of your organizational unit?
[Unknown]: CISCO
What is the name of your organization?
[Unknown]: CISCO
RAN Management System Installation Guide, Release 4.0
February 9, 2015
3
Troubleshooting
Certificate Regeneration for Upload Server
What is the name of your City or Locality?
[Unknown]: BLR
What is the name of your State or Province?
[Unknown]: KA
What is the two-letter country code for this unit?
[Unknown]: IN
Is CN=10.5.2.217, OU=CISCO, O=CISCO, L=BLR, ST=KA, C=IN correct?
[no]: yes
Enter key password for <dpe-key>
(RETURN if same as keystore password):
Re-enter new password:
Enter:
/rms/app/CSCObac/jre/bin/keytool -keystore /rms/app/CSCObac/dpe/conf/dpe.keystore
-alias dpe-key -certreq -file dpe.csr
Output:
Enter keystore password:
It is important to use the keytool utility provided by DPE instead of the default java keytool as per
BAC documentation.
Set ownership
Enter:
Note
Step 5
chown bacservice:bacservice /rms/app/CSCObac/dpe/conf/dpe.keystore
Output:
System returns with command prompt
Enter:
chown bacservice:bacservice /rms/app/CSCObac/dpe/conf/dpe.csr
Output:
System returns with command prompt
Step 6
Get the CSR signed by the signing authority and get the signed certificates and CA certificates (client-ca.cer,
root-ca.cer and server-ca.cer).
Step 7
Reinstall the certificates. Follow the steps 4 and 5 in the “Installing RMS Certificates” section.
Step 8
Reload the server process. Follow the step 7 in “Installing RMS Certificates" section.
Certificate Regeneration for Upload Server
Following are the Keystore regeneration steps to be performed manually if something goes wrong with the
certificate generation process in LUS:
RAN Management System Installation Guide, Release 4.0
4
February 9, 2015
Troubleshooting
Deployment Troubleshooting
Procedure
Step 1
Step 2
Open /opt/CSCOuls/bin/generate_keystore.sh as root.
Edit the below lines as per OVA descriptor settings:
Cert_C="US"
Cert_ST="NC"
Cert_L="RTP"
Cert_O="Cisco Systems, Inc."
Cert_OU="SCTG"
Upload_SB_Fqdn="rtpfga-ova-upload"
Upload_Keystore_Password="Ch@ngeme1"
Upload_Node_Eth1_Address="10.5.2.17"
Step 3
Run the script:
Enter:
./generate_keystore.sh
Output:
[root@blr-rms14-upload bin]# ./generate_keystore.sh
create uls keystore, private key and certificate request
Enter keystore password: Re-enter new password: Enter key password for <uls-key>
(RETURN if same as keystore password): Re-enter new password: Enter destination
keystore password: Re-enter new password: Enter source keystore password: MAC
verified OK
Changing permissions
fix permissions on secure files
The uls.keystore and uls.csr would be regenerated under /opt/CSCOuls/conf.
Step 4
Step 5
After getting the uls.csr file , get it signed by the signing authority to get client, server, and root certificates.
Step 6
Reload the server process. Follow the step 7 in “Installing RMS Certificates" section.
Reinstall the certificates. Follow the steps 4 and 5 in the “Installing RMS Certificates” section.
Deployment Troubleshooting
To address the problems faced during RMS deployment, complete the following steps.
For more details to check the status of CN, ULS and SN seeRMS Installation Sanity Check .
Unable to Access BAC and DCC UI
Issue
Not able to access BAC UI and DCC UI due to expiry of certificates in browser.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
5
Troubleshooting
DHCP Server Not Functioning
Cause
Solution
Certificate added to the browser just has three months validity.
1 Delete the existing certificates from the browser.
Go to Tools > Options. In the Options dialog, click Advanced > Certificates
> View Certificates.
2 Select RMS setup certificate and delete.
3 Clear the browser history.
4 Access DCC UI/BAC UI again. The message "This Connection is Untrusted"
appears. Click Add Exception and click Confirm Security Exception from Add
Security Exception dialog.
DHCP Server Not Functioning
For details on Verifying Application Processes
Issue
DHCP server is not functioning.
During login to nrcmd with user name 'cnradmin' and proper password, it shows
groups and roles as 'superuser'; but if any command related to DHCP is entered,
the following message is displayed.
"You do not have permission to perform this action."
Cause
The property, "prop:Cnr_License_IPNode" is set incorrectly in the descriptor file.
RAN Management System Installation Guide, Release 4.0
6
February 9, 2015
Troubleshooting
DHCP Server Not Functioning
Solution
1 Edit the following product.license file with proper license key for PNR by
logging into central node.
/rms/app/nwreg2/local/conf/product.licenses
Sample license file for reference:
INCREMENT count-dhcp cisco 8.1 permanent uncounted
VENDOR_STRING=<Count>10000</Count>
HOSTID=ANY
NOTICE="<LicFileID>20130715144658047</LicFileID><LicLineID>1</LicLineID>
<PAK></PAK><CompanyName></CompanyName>" SIGN=176CCF90B694
INCREMENT base-dhcp cisco 8.1 permanent uncounted
VENDOR_STRING=<Count>1000</Count>
HOSTID=ANY
NOTICE="<LicFileID>20130715144658047</LicFileID><LicLineID>2</LicLineID>
<PAK></PAK><CompanyName></CompanyName>" SIGN=0F10E6FC871E
INCREMENT base-system cisco 8.1 permanent uncounted
VENDOR_STRING=<Count>1</Count>
HOSTID=ANY
NOTICE="<LicFileID>20130715144658047</LicFileID><LicLineID>3</LicLineID>
<PAK></PAK><CompanyName></CompanyName>" SIGN=9242CBD0FED0
2 Log in to PNR GUI.
http://<central nb ip>:8090
User Name: cnradmin
Password: <prop:Cnradmin_Password> (Property value from the descriptor
file)
3 Click Administration > Licenses from Home page.
The following three types of license keys should be present. If not present, add
them using browser.
1 Base-dhcp
2 Count-dhcp
3 Base-system
4 Click Administration > Clusters.
5 Click Resynchronize.
Go to Serving Node Console and restart PNR server using the following
command:
/etc/init.d/nwreglocal stop
/etc/init.d/nwreglocal start
After restarting the PNR server, check the status using the following command:
/rms/app/nwreg2/local/usrbin/cnr_status
Output:
DHCP Server running
(pid:
Server Agent running
(pid:
CCM Server running
(pid:
WEB Server running
(pid:
CNRSNMP Server running
(pid:
RIC Server Running
(pid:
TFTP Server is not running
DNS Server is not running
DNS Caching Server is not running
8056)
8050)
8055)
8057)
8060)
8058)
.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
7
Troubleshooting
DPE processes are not running
DPE processes are not running
DPE Installation Fails with error log:
Issue
This DPE is not licensed. Your request cannot be serviced"
Cause
Configure the property prop:Dpe_Cnrquery_Client_Socket_Address=NB IP
address of serving node in the descriptor file. If other than NB IP address of
serving node is given then "DPE is not licensed error" will appear in OVA first
boot log.
Solution
1 Log in to DPE CLI using the command [admin1@blr-rms11-serving ~]$
2 Execute the command telnet localhost 2323.
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
blr-rms11-serving BAC Device Provisioning Engine
User Access Verification
Password:
blr-rms11-serving>
Password:
blr-rms11-serving#
blr-rms11-serving#
blr-rms11-serving#
en
dpe cnrquery giaddr x.x.x.x
dpe cnrquery server-port 61610
dhcp reload
.
Connection to Remote Object Unsuccessful
Issue
A connection to the remote object could not be made. OVF Tool does not support
this server.
Completed with errors
Cause
The errors are triggered by ovftool command during ova deployment. the errors
can be found in both Console and vCenter logs.
Solution
User must have Administrator privileges to VMware vCenter and ESXi.
VLAN Not Found
Issue
VLAN not found.
RAN Management System Installation Guide, Release 4.0
8
February 9, 2015
Troubleshooting
Unable to Get Live Data in DCC UI
Cause
The errors are triggered by ovftool command during ova deployment. the errors
can be found in both Console and vCenter logs.
Solution
Check for the appropriate "portgroup" name on virtual switch of Elastic Sky X
Integrated (ESXi) host or Distributed Virtual Switch (DVS) on VMware vCenter.
Unable to Get Live Data in DCC UI
Issue
Cause
Solution
Live Data of an AP is not coming and Connection request fails.
1 Device is offline.
2 Device is not having its radio activated/ device is registered but not activated.
1 In the Serving Node, add one more route with Destination IP as HNB-GW
SCTP IP and Gateway as Serving Node North Bound IP as in the following
example:
Serving NB Gateway IP-10.5.1.1
HNBGW SCTP IP- 10.5.1.83
Add the following route in Serving node:
route add -net 10.5.1.83 netmask 255.255.255.0 gw 10.5.1.1
2 Activate the device from DCC UI post registration.
3 Verify trouble shooting logs in bac.
4 Verify DPE logs and ZGTT logs from ACS simulator.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
9
Troubleshooting
Installation Warnings about Removed Parameters
Installation Warnings about Removed Parameters
RAN Management System Installation Guide, Release 4.0
10
February 9, 2015
Troubleshooting
Installation Warnings about Removed Parameters
Note
Below properties have been completely removed from 4.0 OVA installation. Warning would be thrown
by the installer, if these properties are found in OVA descriptor. However, installation should still go fine.
prop:vami.gateway.Upload-Node
prop:vami.DNS.Upload-Node
prop:vami.ip0.Upload-Node
prop:vami.netmask0.Upload-Node
prop:vami.ip1.Upload-Node
prop:vami.netmask1.Upload-Node
prop:vami.gateway.Central-Node
prop:vami.DNS.Central-Node
prop:vami.ip0.Central-Node
prop:vami.netmask0.Central-Node
prop:vami.ip1.Central-Node
prop:vami.netmask1.Central-Node
prop:vami.gateway.Serving-Node
prop:vami.DNS.Serving-Node
prop:vami.ip0.Serving-Node
prop:vami.netmask0.Serving-Node
prop:vami.ip1.Serving-Node
prop:vami.netmask1.Serving-Node
prop:Debug_Mode
prop:Server_Crl_Urls
prop:Bacadmin_Password
prop:Dccapp_Password
prop:Opstools_Password
prop:Dccadmin_Password
prop:Postgresql_Password
prop:Central_Keystore_Password
prop:Upload_Stat_Password
prop:Upload_Calldrop_Password
prop:Upload_Demand_Password
prop:Upload_Lostipsec_Password
prop:Upload_Lostgwconnection_Password
prop:Upload_Nwlscan_Password
prop:Upload_Periodic_Password
prop:Upload_Restart_Password
prop:Upload_Crash_Password
prop:Upload_Lowmem_Password
prop:Upload_Unknown_Password
prop:Serving_Keystore_Password
prop:Cnradmin_Password
prop:Caradmin_Password
prop:Dpe_Cli_Password
prop:Dpe_Enable_Password
prop:Fc_Realm
prop:Fc_Log_Periodic_Upload_Enable
prop:Fc_Log_Periodic_Upload_Interval
prop:Fc_On_Nwl_Scan_Enable
prop:Fc_On_Lost_Ipsec_Enable
prop:Fc_On_Crash_Upload_Enable
prop:Fc_On_Call_Drop_Enable
prop:Fc_On_Lost_Gw_Connection_Enable
prop:Upload_Keystore_Password
prop:Dpe_Keystore_Password
prop:Bac_Secret
prop:Admin2_Username
prop:Admin2_Password
prop:Admin2_Firstname
prop:Admin2_Lastname
prop:Admin3_Username
prop:Admin3_Password
prop:Admin3_Firstname
prop:Admin3_Lastname
prop:Upgrade_Mode
prop:Asr5k_Hnbgw_Address
RAN Management System Installation Guide, Release 4.0
February 9, 2015
11
Troubleshooting
Upload Server is Not Up
Upload Server is Not Up
The upload server fails with java.lang.ExceptionInInitializerError in the following scenarios.
The errors can be seen in opt/CSCOuls/logs/uploadServer.console.log file.
Scenario 1:
RAN Management System Installation Guide, Release 4.0
12
February 9, 2015
Troubleshooting
Upload Server is Not Up
Issue
Upload Server failed with java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at com.cisco.ca.rms.upload.server.UlsSouthBoundServer.getInstance
(UlsSouthBoundServer.java:58)
at com.cisco.ca.rms.upload.server.UlsServer.<init>(UlsServer.java:123)
at com.cisco.ca.rms.upload.server.UlsServer.<init>(UlsServer.java:25)
at
com.cisco.ca.rms.upload.server.UlsServer$SingleInstanceHolder.<clinit>
(UlsServer.java:70)
at
com.cisco.ca.rms.upload.server.UlsServer.getInstance(UlsServer.java:82)
at com.cisco.ca.rms.upload.server.UlsServer.main(UlsServer.java:55)
Caused by: org.jboss.netty.channel.ChannelException: Failed to bind
to: /10.6.22.12:8080
at
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:298)
at com.cisco.ca.rms.upload.server.UlsSouthBoundServer.<init>
(UlsSouthBoundServer.java:109)
at com.cisco.ca.rms.upload.server.UlsSouthBoundServer.<init>
(UlsSouthBoundServer.java:22)
at
com.cisco.ca.rms.upload.server.UlsSouthBoundServer$SingleInstanceHolder.<clinit>
(UlsSouthBoundServer.java:46)
... 6 more
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind
(NioServerSocketPipelineSink.java:140)
at
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket
(NioServerSocketPipelineSink.java:90)
at
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk
(NioServerSocketPipelineSink.java:64)
at org.jboss.netty.channel.Channels.bind(Channels.java:569)
at
org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(
ServerBootstrap.java:343)
at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>
(NioServerSocketChannel.java:80)
at
org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel
(NioServerSocketChannelFactory.java:158)
at
org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel
(NioServerSocketChannelFactory.java:86)
at
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:277)
... 9 more
Cause
The server failed to bind to the IP /10.6.22.12:8080 because the requested address
was unavailable.
Solution
Navigate to /opt/CSCOuls/conf and modify the UploadServer.properties file with
proper SB and NB IP address.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
13
Troubleshooting
Upload Server is Not Up
Scenario 2:
Issue
Upload Server failed with java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at
com.cisco.ca.rms.upload.server.security.UlsSbSslContextMgr.getInstance
(UlsSbSslContextMgr.java:65)
at com.cisco.ca.rms.upload.server.UlsSouthBoundPipelineFactory.<init>
(UlsSouthBoundPipelineFactory.java:86)
at com.cisco.ca.rms.upload.server.UlsSouthBoundServer.<init>
(UlsSouthBoundServer.java:102)
at com.cisco.ca.rms.upload.server.UlsSouthBoundServer.<init>
(UlsSouthBoundServer.java:22)
at
com.cisco.ca.rms.upload.server.UlsSouthBoundServer$SingleInstanceHolder.<clinit>
(UlsSouthBoundServer.java:46)
at com.cisco.ca.rms.upload.server.UlsSouthBoundServer.getInstance
(UlsSouthBoundServer.java:58)
at com.cisco.ca.rms.upload.server.UlsServer.<init>(UlsServer.java:123)
at com.cisco.ca.rms.upload.server.UlsServer.<init>(UlsServer.java:25)
at
com.cisco.ca.rms.upload.server.UlsServer$SingleInstanceHolder.<clinit>
(UlsServer.java:70)
at
com.cisco.ca.rms.upload.server.UlsServer.getInstance(UlsServer.java:82)
at com.cisco.ca.rms.upload.server.UlsServer.main(UlsServer.java:55)
Caused by: java.lang.IllegalStateException: java.io.IOException:
Keystore was tampered with, or password was incorrect
at com.cisco.ca.rms.commons.security.SslContextManager.<init>
(SslContextManager.java:79)
at com.cisco.ca.rms.upload.server.security.UlsSbSslContextMgr.<init>
(UlsSbSslContextMgr.java:72)
at com.cisco.ca.rms.upload.server.security.UlsSbSslContextMgr.<init>
(UlsSbSslContextMgr.java:28)
at
com.cisco.ca.rms.upload.server.security.UlsSbSslContextMgr$SingleInstanceHolder.<clinit>
(UlsSbSslContextMgr.java:53)
... 11 more
Caused by: java.io.IOException: Keystore was tampered with, or password
was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(Unknown Source)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(Unknown Source)
at java.security.KeyStore.load(Unknown Source)
at
com.cisco.ca.rms.upload.server.security.UlsSbSslContextMgr.loadKeyManagers
(UlsSbSslContextMgr.java:91)
at
com.cisco.ca.rms.commons.security.SslContextManager.<init>(SslContextManager.java:48)
... 14 more
Caused by: java.security.UnrecoverableKeyException: Password
verification failed
... 19 more
Cause
The Keystore was tampered with, or password entered is incorrect resulting in a
password verification failure.
This occurs when the password used to generate the Keystore file is different than
the one given for the property “Upload_Keystore_Password” in descriptor file.
RAN Management System Installation Guide, Release 4.0
14
February 9, 2015
Troubleshooting
Upload Server is Not Up
Solution
1 Navigate to /opt/CSCOuls/conf and execute the below command to change the
password of the Keystore file.
"[root@rtpfga-s1-upload1 conf]# keytool -storepasswd -keystore
uls.keystore"
Output:
Enter keystore password:
New keystore password:
Re-enter new keystore password
The new Keystore password should be same as given in the descriptor
file.
2 Restart the server process.
Note
[root@rtpfga-s1-upload1 conf]# service god restart
[root@rtpfga-s1-upload1 conf]# service god status
UploadServer: up
Scenario 3:
RAN Management System Installation Guide, Release 4.0
February 9, 2015
15
Troubleshooting
Upload Server is Not Up
Issue
Upload Server failed with java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at com.cisco.ca.rms.dcc.lus.server.LusNorthBoundServer.getInstance
(LusNorthBoundServer.java:65)
at com.cisco.ca.rms.dcc.lus.server.LusServer.<init>(LusServer.java:98)
at com.cisco.ca.rms.dcc.lus.server.LusServer.<init>(LusServer.java:17)
at
com.cisco.ca.rms.dcc.lus.server.LusServer$SingleInstanceHolder.<clinit>
(LusServer.java:45)
at
com.cisco.ca.rms.dcc.lus.server.LusServer.getInstance(LusServer.java:57)
at com.cisco.ca.rms.dcc.lus.server.LusServer.main(LusServer.java:30)
Caused by: org.jboss.netty.channel.ChannelException: Failed to bind
to: /0.0.0.0:8082
at
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:298)
at com.cisco.ca.rms.dcc.lus.server.LusNorthBoundServer.<init>
(LusNorthBoundServer.java:120)
at com.cisco.ca.rms.dcc.lus.server.LusNorthBoundServer.<init>
(LusNorthBoundServer.java:30)
at
com.cisco.ca.rms.dcc.lus.server.LusNorthBoundServer$SingleInstanceHolder.<clinit>
(LusNorthBoundServer.java:53)
... 6 more
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind
(NioServerSocketPipelineSink.java:140)
at
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket
(NioServerSocketPipelineSink.java:92)
at
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk
(NioServerSocketPipelineSink.java:66)
at org.jboss.netty.channel.Channels.bind(Channels.java:462)
at
org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:186)
at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen
(ServerBootstrap.java:343)
at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>
(NioServerSocketChannel.java:77)
at
org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel
(NioServerSocketChannelFactory.java:137)
at
org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel
(NioServerSocketChannelFactory.java:85)
at
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:277)
... 9 more
Cause
The server failed to bind to the IP /0.0.0.0:8082 because the requested address is
already in use.
RAN Management System Installation Guide, Release 4.0
16
February 9, 2015
Troubleshooting
Upload Server is Not Up
Solution
Execute the command:
netstat –anp |grep <port number>
For example:
[root@rtpfga-s1-upload1 conf]# netstat -anp |grep 8082
tcp
0
0 10.6.23.16:8082
0.0.0.0:*
LISTEN
26842/java
Kill the particular process.
[root@rtpfga-s1-upload1 conf]# kill -9 26842
Start the server.
“[root@rtpfga-s1-upload1 conf]# service god start
[root@rtpfga-s1-upload1 conf]# service god status
UploadServer: up”
RAN Management System Installation Guide, Release 4.0
February 9, 2015
17
Troubleshooting
Upload Server is Not Up
RAN Management System Installation Guide, Release 4.0
18
February 9, 2015
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising