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

No Logs in NSM UI - Could not get day list. How to reindex the traffic logs.

0

0

Article ID: KB10965 KB Last Updated: 23 Nov 2010Version: 11.0
Summary:
There are no traffic logs in the NSM UI or the log files are not getting refreshed.  This could be caused by a corrupt log index.
Symptoms:

Symptoms & Errors:

  • Traffic logs in NSM UI are not refreshed.
  • There is Red Icon at the bottom right hand corner, you get error "could not get day list"
For more information about the cause of  "could not get day list" see KB16655
Solution:

This problem happens if the index for traffic logs is corrupt. The log index needs to be rebuilt.

Follow these steps to rebuild the index:

  1. Login to NSM Device Server
  2. Stop All NSM Server Services (If you have HA environment stop NSM Services on both primary and Secondary Server)
  3. To Stop and Start NSM Server Services refer to  KB11263 How to Start & Stop NSM Services
  4. Enter:  #cd /usr/netscreen/DevSvr/var/logs
  5. Delete all the index*.mark files  #rm -f index*.mark  
  6. For the  action*.mark files: 

    • If you do not have any Device Log Actions configured:
      Delete the action*.mark files #rm -f action*.mark
    • If you do have Device Log actions configured, deleting the action*.mark files will perform any configured actions on the logs as they are reindexed.  If you do not want this to happen: You can do one of the following:

      • Leave the action*.mark files intact
        OR
      • Disable all Device log Action criteria before removing the action*.mark files

  7. Restart NSM Services.  Once the Device Server starts the log index is rebuilt - you can verify this by tailing the file newLogwalker.0.  Enter:

    #tail -f /usr/netscreen/DevSvr/var/errorLog/newLogWalker.0

  8. Login to NSM UI and verify the logs are getting refreshed.
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