This article expains the syslog messge , "ifinfo: PVIDB: Attribute 'xxxxx' not present in Db"
, "ifinfo: PVIDB: Attribute 'xxxxx' not present in Db"
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
If ' any any ' is configured in the system, these debug messages may appear.
any any
system { syslog { file messages { any any; 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.
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.