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

[EOL/EOE] How to interpret a stack trace received in an NSM error log

0

0

Article ID: KB9842 KB Last Updated: 18 Oct 2020Version: 7.0
Summary:
Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.
When an NSM process encounters an internal error, it usually records the entry in the log file; marking the error message as a stack trace.
Symptoms:
Need help reading a stack trace received in the NSM log. 
Solution:
When the NSM process encounters an internal error, it is possible that the log file contains an error message which is known as a stack trace.

Sample:
Trace: java.lang.Throwable
        at com.netscreen.utils.WatchDogEvent.<init>(WatchDogEvent.java:31)
        at com.netscreen.utils.DatabaseQueryManager.makeDataBaseQuery(DatabaseQueryManager.java:51)
        at com.netscreen.utils.DatabaseQueryManager.makeDataBaseQuery(DatabaseQueryManager.java:40)
        at com.netscreen.transformation.sharedobjs.AdmDatabaseWrapper.getPartialAdmObjects(AdmDatabaseWrapper.java:365)
        at com.netscreen.transformation.sharedobjs.ConverterManager.preloadPredefinedSharedObjectsForCategory(ConverterManager.java:630)
        at com.netscreen.transformation.sharedobjs.ConverterManager.preloadPredefinedSharedObjects(ConverterManager.java:614)
        at com.netscreen.transformation.sharedobjs.ConverterManager.preloadStaticTables(ConverterManager.java:601)
        at com.netscreen.devicecomm.GUIDirectiveManager.<init>(GUIDirectiveManager.java:207)
        at com.netscreen.devicecomm.GUIDirectiveManager.main(GUIDirectiveManager.java:287)

The trace can indicate the area generating the internal error; such as the policy; the address objects, the device configuration or VPN settings, etc.  The stack trace is read from bottom to top, the order of execution of various functions.  Reading the trace in this direction will lead to the event that generated the error.


Trying to isolate the root cause is the best way to approach this issue depending on the area affected.  If the policy seems affected, one can do a quick test by assigning for a blank policy to the device and trying another delta config.  This would isolate if the problem is with the policy assigned to the device.     It is also recommended to turn on debug mode, if not already enabled, for the affected NSM processes. For assistance, refer to KB9840- How to enable debug mode for NSM processes
Modification History:
2020-10-18: Tagged article for EOL/EOE.
 

Related Links

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