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

[EOL/EOE] NSM - Meaning of Red Triangle Error - "Could not get day list"

0

0

Article ID: KB16655 KB Last Updated: 18 Oct 2020Version: 2.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.


This article describes the possible causes for the "Could not get day list" error message sometimes seen in the lower right corner of NSM window.

Symptoms:
Symptoms & Errors:
  • In some cases, NSM may display the red triangle error in the lower right corner of the window. 
  • The text "Could not get day list" will appear when hovering the mouse over the error indicator.
  • No logs (or no recent logs) will display in the NSM log viewer. 
  • Log display is extremely slow.
Solution:
This message indicates a problem with the devSvrLogWalker process, wherein the devSvrLogWalker process cannot index the logs properly.

Device logs are stored in "day" directories under /var/netscreen/DevSvr/logs.
For example:
20091231
2010010
and so on.

In addition, in this directory are four ".mark" files:
action1.mark
action2.mark
index1.mark
index2.mark


The index mark files are the overall index files for all the logs stored in /var/netscreen/DevSvr/logs.  In addition, each of the day directories contain some individual index files.  Part of the job of the logWalker process is to maintain these index files.

Among the reasons for "Could not get day list" include:
  • Corrupt log data within a particular day's log directory
  • Log day directories not readily available for scanning by log walker. (Some day's logs stored on local disk/partition and some on remote disk/partition).
  • Other disk related problems that prevent log walker from getting good data during indexing scans.

To help ensure good log data:
  • Make use of NSM log purging and archive methods available since version 2007.1 (Server Manager > Servers > Edit device server > Disk and log management tab)
  • Keep all "online" log data on the same disk/partition.
  • Keep logging levels within policies to a reasonable level. (Logging all permitted traffic, for instance, will dramatically increase the size of the logs directory, could increase the likelihood of error and will diminish performance of the log walker process and thus, the log viewer in NSM.)
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