During commit on ACX7024 we observe following errors:

DUT# commit
error: Failed to get RE list <<<
commit complete

Customer might notice error message while performing commit on the device. 

DUT# commit
error: Failed to get RE list <<<
commit complete

log messages similar to below are seen:

13:00:17 DUTkernel - systemd 250.5+ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR -IMA -SMACK -SECCOMP -GCRYPT -GNUTLS -OPENSSL -ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -BZIP2 -LZ4 +XZ -ZLIB -ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP -SYSVINIT default-hierarchy=hybrid)
4:28 13:00:17 DUTsystemd[1] - Stopping D-Bus System Message Bus...
4:28 13:00:17 DUTsystemd[1] - Stopped D-Bus System Message Bus.

messages.5.gz:Nov 1 06:26:26.145 test mgd[29014]: UI_CMDLINE_READ_LINE: User 'test', command 'commit '
messages.5.gz:Nov 1 06:26:26.150 test mgd[29014]: UI_COMMIT: User 'test' requested 'commit' operation (comment: none)

messages.5.gz:Nov 1 06:27:33.467 test mgd[29014]: UI_COMMIT_PROGRESS: Commit operation in progress: commit complete
messages.5.gz:Nov 1 06:27:33.467 test mgd[29014]: UI_COMMIT_COMPLETED: : commit complete
2877470 2025-10-01 16:28:11.460967557 re0:sysman:3590:TRACE_INFO libevoinfra_INFO_APP Function = "evoapp_init_commons", node_type = "RE", node_slot = 0,
node_name = "re0", app_name = "sysman", app_id = 0

journalctl.txt

1591552 Nov 01 06:26:32 test systemd[1]: Received SIGUSR1 from PID 10782 (sysman).
1591553 Nov 01 06:26:32 test systemd[1]: Trying to reconnect to bus...
1591554 Nov 01 06:26:32 test systemd[1]: Received SIGTERM from PID 10782 (sysman).

1591785 Nov 01 06:28:07 test systemd[1]: sysman.service: State 'stop-sigterm' timed out. Killing.
1591786 Nov 01 06:28:07 test systemd[1]: sysman.service: Killing process 10782 (sysman) with signal SIGKILL.

1591787 Nov 01 06:28:07 test systemd[1]: sysman.service: Main process exited, code=killed, status=9/KILL
1591788 Nov 01 06:28:07 test exit_handler.sh[2947]: Notice: PID found for app sysman in /var/run/pid/sysman.pid is 10782.Executing command:(CLEANZK_LOGTOFILE=1 /sbin/ip vrf exec iri /usr/sbin/cleanzk -c /var/run/zkid/10782.id;rm /var/run/zkid/10782.id 2>/dev/null)
1591789 Nov 01 06:28:07 test audit: BPF prog-id=225 op=LOAD

This issue is resolved in following releases- evo:24.2R2-S3-EVO evo:24.4X200-D30-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R2 junos:25.4R1.

In Evo, in the commit path, the "show system nodes" command is executed to fetch the information about other RE.
This command is executed via the libsystem-api library, which directly interfaces with cmdd (bypassing mgd) to run the command.
The library invokes the command with a 30-second timeout and includes one retry attempt.

Workaround: 
With root user login to the system, execute the following command to restart the sysman. sysman is management daemon. Usually no impact to traffic should be seen but always recommended to perform under Maintenance window to avoid any anomaly. 

# systemctl restart sysman

2025-11-06 : Article Created

22 nov:  modified article - added workaround and udpated all the fields with clear details. added PR 1909995.