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

Syslog message: ifinfo: PVIDB: Attribute 'xxxxx' not present in Db

0

0

Article ID: KB32862 KB Last Updated: 28 Jun 2018Version: 1.0
Summary:

This article expains the syslog messge, "ifinfo: PVIDB: Attribute 'xxxxx' not present in Db"

Symptoms:

The following syslog messages are seen:

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.ingress_stats_supported' not present in Db

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.print_qc_queue_stats' not present in Db

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.print_qc_trans_rate' not present in Db

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.print_qc_tail_drop_packet_rate' not present in Db

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.print_qc_rate_limit_drop_rate' not present in Db

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.print_qc_red_rate' not present in Db

Jan 29 08:15:01  re0 ifinfo: PVIDB: Attribute 'global.print_qc_queued_rate' not present in Db

Cause:

If 'any any' is configured in the system, these debug messages may appear.

system {
    syslog {
        file messages {
            any notice;
            authorization info;
        }
    }
}

These syslog messages are part of a common PVI DB library that is used by multiple daemons. The logs are meant to indicate a failure in case the application expects an attribute in the database and its is not present. This however, does not translate into an error directly. ​

For some platforms, certain PVI DB attributes are not supported, but reading these attributes does exist as a part of a common code (common for different platforms). Hence, while trying to read these PVI DB attributes, these debug logs will appear.

Solution:

These messages are informational and can safely be ignored. They will not be seen if the severity level for "system syslog file messages" configuration is changed to something else other than "any".

Example:

root@re0# set system syslog file messages any error


These messages can also be filtered out by using the match command under the [system syslog] hierachy.

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