Support Support Downloads Knowledge Base Juniper 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

[Log Collector] How to delete the Log Collector node from the ECM database



Article ID: KB36218 KB Last Updated: 10 Sep 2020Version: 1.0

This article explains how to delete the Log Collector node from the ECM database.



After upgrading Log Collector to the latest version, the Log Collector node page under Security Director continues to show the older version and the page itself may be stuck under Security Director.



If users do not delete the logging node from Security Director and proceed with the upgrade of the Log Collector, the Security Director logging node page shows the old version even though the logging node has been upgraded to the latest version.



To delete the logging node from the database, perform the following steps:

Note: Before performing any changes in the database, take a snapshot/backup of the Junos Space server. Refer to Backing Up the Junos Space Network Management Platform Database for performing Junos Space backup.

  1. Log in to the ECM database by using the following command:

#  mysql -ujboss -p$(grep mysql.jboss /etc/sysconfig/JunosSpace/pwd | awk -F= '{print $2}') ecm_db -A
  1. Run the following command to find the "id" of the Log Collector node:

# mysql> select * from LogCollectorNode\G; 

Sample Output

mysql> select * from LogCollectorNode\G;
*************************** 1. row ***************************
                    id: ABCXYZ
              domainId: 2
               version: 0
             createdAt: 2020-06-04 05:03:14

In the following sample screenshot, we can identify the Log Collector "id" and "nodeVersion".

  1. Run the following command to delete the Log Collector node.

# mysql> delete from LogCollectorNode where id='<ABCXYZ>';

Note: In case of a multi-node Junos Space setup, you need to perform the above step on the VIP/Primary node where eth0:0 exists.

  1. Now try to add the logging node again in the Security Director WebUI.

Note: If the issue persists, the problem might be due to some other reason. Contact Support for assistance.


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