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

[Subscriber Management] pppoed reports "sdb_get_client_dyn_internal: client_session_record is NULL" error log

0

0

Article ID: KB31288 KB Last Updated: 16 Dec 2016Version: 1.0
Summary:

This article explains the error message:

pppoed: %USER-3: sdb_get_client_dyn_internal: client_session_record is NULL

This is a temporary error and there is no service impact.
Symptoms:

After upgrading to Junos OS  version 13.3R9,  MX subscriber management device reports error:

pppoed: %USER-3: sdb_get_client_dyn_internal: client_session_record is NULL

when the following command is run:
user@MX240> show log messages|no-more
Nov 9 09:00:00 MX240 newsyslog[5890]: logfile turned over due to size>1024K
Nov 9 09:00:01 2016 MX240 pppoed: %USER-3: sdb_get_client_dyn_internal: client_session_record is NULL
Nov 9 09:00:01 2016 MX240 pppoed: %USER-3: sdb_get_client_dyn_internal: client_session_record is NULL
Nov 9 09:00:02 2016 MX240 pppoed: %USER-3: sdb_get_client_dyn_internal: client_session_record is NULL
Cause:

This error message might occur during normal processing.

For example, when a subscriber receives a Deny during the authentication phase, since this subscriber never progresses beyond the Authentication phase to Network Control Protcol (NCP) negotiation in jpppd, the Logical Device (IFL) never transitions to the Up state in the kernel. This means that jpppd and pppoed must both look at the Session Database (SDB) entry to determine which daemon does the cleanup of the subscriber. By the time pppoed requests the updated SDB entry, jpppd has already looked at it and done the cleanup, so the SDB entry is no longer available.

This is not an error, but just normal processing for a subscriber that receives an authentication Deny.

Solution:

The error message is produced by the libsdb implementation, so that team will need to make the change to lower the level of the message.

Until this change is made, this error message can be ignored and filtered safely.

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