PPDM host: SYS0052 Component UI is restarting
Summary: Critical alerts are generated on PPDM with below message SYS0052 This component was detected as not running on the PowerProtect Data Manager system, and has been restarted automatically on the specified host. If the component was stopped manually, you can ignore this alert. If the component stopped without user intervention and this alert continues to appear, contact Dell Customer Support. ...
Symptoms
System UI service on the PPDM server is crashing and will sysmgr will restart the service. User does not experience any issue as service is restarted automatically.
Below is logged in sysmgr log
025-03-04T15:11:10.618Z INFO [] [Thread-17] [][][][][] [c.d.p.c.c.s.c.SMStateListener.stateEntered(51)] - Updated config file and catalog with the new node state PARTIALLY_OPERATIONAL 2025-03-04T15:11:10.682Z ERROR [] [Thread-17] [][ALERT:SYS0052][][][] [c.e.d.e.c.s.m.DefaultMessageResourceModifier.printAlertLog(143)] - Date: Mar 4, 2025 10:11:10 AM; Summary: Component UI is restarting on host dc-ppdm-01.ccf.org.; Details: This component was detected as not running on the PowerProtect Data Manager system, and has been restarted automatically on the specified host.; Recommended Action: If the component was stopped manually, you can ignore this alert. If the component stopped without user intervention and this alert continues to appear, contact Dell Customer Support.; Detail Summaries: null; Status: UNACKNOWLEDGED 2025-03-04T15:11:10.690Z WARN [] [Thread-17] [][][][][] [c.e.b.s.s.m.ComponentMonitorServiceImpl.startComponent(413)] - Component UI is down. 2025-03-04T15:11:10.690Z INFO [] [Thread-17] [][][][][] [c.e.b.s.s.m.ComponentMonitorServiceImpl.startComponent(414)] - Restarting UI : 5 attempts left
At the same time, below is logged in UI log
2025-03-04T15:09:21.646Z info: /configType Formfactor is standalone2025-03-04T15:09:21.759Z warn: [sid=s:ZSApCuLs...UKiybUJrbY] /user is denied: no session token2025-03-04T15:09:21.770Z warn: [sid=s:ZSApCuLs...UKiybUJrbY] /user is denied: no session token2025-03-04T15:10:58.694Z info: [sid=s:ZSApCuLs...UKiybUJrbY] emc.login POST /login2025-03-04T15:10:58.695Z info: [sid=s:ZSApCuLs...UKiybUJrbY] authentication login POST url username: <user> tenant: undefined domain: undefined2025-03-04T15:11:12.327Z info: app-startup arguments are {
2025-03-04T15:09:21.770Z warn: [sid=s:ZSApCuLs...UKiybUJrbY] /user is denied: no session token2025-03-04T15:10:58.694Z info: [sid=s:ZSApCuLs...UKiybUJrbY] emc.login POST /login2025-03-04T15:10:58.695Z info: [sid=s:ZSApCuLs...UKiybUJrbY] authentication login POST url username: <user> tenant: undefined domain: undefined
Cause
After user login, a request is made to /authorization-token to get user information. For specific users (that cause this issue), the data returned is missing information and a section of code assumes there is always at least one element in an array present (the array is actually null) causing a memory access error which results in component failing ungracefully and killing itself then restarting as designed
Resolution
This is a software bug as documented in PPDMESC-7105 / PPDM-335427. This issue will be fixed in PPDM version 19.19 and above