Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Northstar System Health Monitor and Analytics Times Out due to Expired Certificate



Article ID: TSB17645 TECHNICAL_BULLETINS Last Updated: 03 Oct 2019Version: 2.0
Alert Type:
PSN - Product Support Notification
Product Affected:
NorthStar Controller (versions 3.1 through 5.0)
Alert Description:

The original NorthStar installation scripts did not properly generate SSL certificates for the health monitoring and analytics packages.  As a result, the certificates will prematurely expire (or have become expired) and need to be updated immediately.

Impacted Versions:
All versions of NorthStar 3.1 through 5.0

                Web -- Health monitor erroneously reports the application nodes as unreachable (because the SSL certificate expired).
                Charts -- Queries will fail (because the SSL certificate expired).
                Telemetry -- Data will not be stored into Elastic Search (because the SSL certificate expired).

NorthStar customers can confirm if the certificate is invalid by issuing the following command:

[root@pcs-q-pod03 NodeJS]# openssl x509 -enddate -noout -in /opt/northstar/web/routes/v1/health/certs/server/server-crt.pem
notAfter=Sep 24 21:51:07 2019 GMT
Note: The date listed in the response is the date when the certificate expires.
Please find the procedure to generate the new certificate attached to this TSB.  Processes that need to be restarted will vary depending on how the NorthStar Controller is implemented.

This patch is for versions 3.1 - 5.0.  A separate patch will be made available for 3.0.

Patch Instructions (NorthStar versions 3.1-5.0):
  1. Extract the archive nsCertPatch_2019_09_26.tar.gz on the the main application server only.
  2. Execute
  3. On all servers (apps and analytics) identify the RUNNING processes
         supervisorctl status
  4. Restart the below processes on all servers (if it exists) and if the status is RUNNING


Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search