>> Customer evo-junos version

Model: ptx10004
Junos: 22.2R3-S2.5-EVO
Yocto: 3.0.2
Linux Kernel: 5.2.60-yocto-standard-gc37311f
JUNOS-EVO OS 64-bit [junos-evo-install-ptx-x86-64-22.2R3-S2.5-EVO]

>> You will see license subsystem not running

Router> show system license
error: the license-service subsystem is not running

>> Application alarm will be seen

Router> show system alarms
4 alarms currently active
Alarm time Class Description
2024-03-05 03:57:03 UTC Major Application license-check fail on node Re0
2024-03-05 03:46:52 UTC Minor Host 1 Disk 2 Labelled incorrectly
2024-03-05 03:53:09 UTC Major Application config-sync fail on node Re1

>> You will also see core files

Router> show system core-dumps no-forwarding
re0:
--------------------------------------------------------------------------
-rw-r--r-- 1 root root 8333220 Mar 5 01:17 /var/core/re0/license-check.re.re0.17461.2024_03_05.01_17_03.tar.gz
-rw-r--r-- 1 root root 126238737 Mar 6 22:06 /var/core/re0/license-check.re.re0.2600.2024_03_06.22_05_27.tar.gz
-rw-r--r-- 1 root root 10969486 Mar 5 03:58 /var/core/re0/license-check.re.re0.7581.2024_03_05.03_56_55.tar.gz

>> Above all three will be seen after reboot

On Junos OS Evolved platforms, when license with unknown feature ID/platform reserved feature ID is added via configuration, set system license keys key <xx> and then if License-service is restarted, the system is rebooted or software upgrade is done, then license service crashes and crash files are seen. This is a non service impacting issue.

license key contains feature IDs. If a feature ID is not applicable to the platform, it is treated as unknown feature ID. While adding the license with unknown feature ID via 'set system license keys key <xx>, the commit goes through, but the license service is not running. License-service crashes when unknown feature ID notification is called. CLI show system license" can be used to check the status of license check process. below error will be seen while checking the 

license:root@device-re0> show system license error: the license-service subsystem is not running


It auto recovers. below error is expected as license-service takes time to come up. It needs to be checked after 1 or 2 minutes when license-service is up.

If not, then we have to manually delete the license and follow the shared procedure to recover.


There is no service impact but your license will not be enabled

Fix:-
For permanent PR 1759618 fix, you need to upgrade the evo-junos to fixed version:

Work Around:-
Please remove the license and reboot the router. Once the device is up and the license-service running, please add the license again, apply the license and reboot the router.