Guest

Preview Tool

Cisco Bug: CSCur04964 - QNS Restart fails to start QNS Processes

Last Modified

Dec 26, 2016

Products (1)

  • Cisco Mobility Services Engine

Known Affected Releases

7.0.0

Description (partial)

Symptom:
[root@rtpclabqps1g-cc01a ~]# diagnostics.sh
QNS Diagnostics
INSTALL TYPE: general
Checking basic ports (80, 7070, 27717-27720, 27749, 8080, 9091)...
Could not connect to port 8080 on qns23 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns25 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns29 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns30 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns33 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns34 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns36 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns38 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns39 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns40 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns42 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns43 (QNS APIs)...[FAIL]
Could not connect to port 8080 on qns44 (QNS APIs)...[FAIL]
Could not connect to port 9091 on qns23 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns23 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns23  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns23.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns25 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns25 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns25  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns25.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns29 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns29 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns29  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns29.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns30 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns30 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns30  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns30.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns33 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns33 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns33  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns33.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns34 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns34 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns34  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns34.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns36 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns36 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns36  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns36.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns38 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns38 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns38  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns38.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns39 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns39 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns39  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns39.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns40 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns40 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns40  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns40.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns42 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns42 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns42  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns42.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns43 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns43 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns43  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns43.  To fix, edit the firewall configuration and rerun puppet


Could not connect to port 9091 on qns44 (QNS Admin port)...[FAIL]
Corrective Action(s):
 1. Ensure qns is running with: runonone.sh qns44 /etc/init.d/qns status
 2. If QNS is not running.  Attempt to start it with: startqns.sh qns44  and monitor the logs for errors.
 3. If QNS is running, the port may not be open in the firewall on qns44.  To fix, edit the firewall configuration and rerun puppet


Checking qns passwordless logins on all boxes...[PASS]

Conditions:
[  OK  ]
Connection to qns22 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Connection to qns23 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns24 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Connection to qns25 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns26 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns27 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns28 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Connection to qns29 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Connection to qns30 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns31 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns32 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Connection to qns33 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Connection to qns34 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
                                                           [  OK  ]
Connection to qns35 closed.
Stopping QNS Instance(s):
Stopping QNS (1 - pcrf): checking JMX port 9045 ....
/opt/broadhop/qns-1/bin/jmxcmd.sh: connect: Connection refused
/opt/broadhop/qns-1/bin/jmxcmd.sh: line 6: /dev/tcp/localhost/9045: Connection refused
Service is not running
                                                           [FAILED]
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.