PowerFlex 4.x: MDM Trace Logs Flooded with INVALID_SESSION Events

Summary: MDM trace logs may show many INVALID_SESSION messages. These messages do not impact system performance or functionality, but can create excessive log noise.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

Scenario

  • MDM is connected to a PowerFlex Manager 4.x system
  • The PowerFlex Core system is on version 4.x

MDM trace logs show the following:

2025/08/11 10:15:14.823907 LOW:7fd7b05b7db0:authSession_GetSessionFromTokenForReadOrWrite:00260: Failed to get session - isWrite: 1, sessionIndex: 0, rc: INVALID_SESSION
2025/08/11 10:15:14.823913 LOW:7fd7b05b7db0:authMgr_GetUserInfoFromToken:00814: Failed to find session for authentication. rc=INVALID_SESSION
2025/08/11 10:15:14.823916 LOW:7fd7b05b7db0:cliMsg_AuthenticateSession:02080: Failed getting user role (INVALID_SESSION) authorized: 0

Impact

  • No functional issue, PowerFlex Gateway (GW) connections, and operations are unaffected.
  • Trace logs are heavily populated with this message, which may contribute to excessive log rotation and the possibility of missing other log entries.
  • No additional processing overhead; these messages do not introduce performance or latency issues for the MDM.
  • The message can be safely ignored from a functional perspective, but log noise may still be an operational consideration.

Cause

In version 4.x, the GW no longer uses session-based authentication when connecting to the MDM. Instead, it authenticates through a newer method that does not send session details.

The MDM, however, still contains legacy code (3.x) that attempts to look up a session for certain incoming requests. When no session is found (as expected for GW 4.x traffic), the MDM logs the INVALID_SESSION event, but the Gateway's request continues to be processed.

This log entry is not an error and does not indicate a problem with GW connectivity or authentication. It is a leftover behavior from older versions.

Resolution

Upgrade the system to a version that includes the fix.

Additional Information

Impacted Versions:

PowerFlex 4.x

Fixed In Version: 

PowerFlex 4.8

Affected Products

PowerFlex rack RCM Software
Article Properties
Article Number: 000355917
Article Type: Solution
Last Modified: 26 Sept 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.