Customer getting the following log being generated, and root cause is required:

Mar 12 14:30:32 SC_13th_SW_AV_ACC_STK_00 secure-dot1xd[29782]: JTASK_SCHED_SLIP: 10 sec scheduler slip, user: 0 sec 56774 usec, system: 0 sec, 63953 usec

Mar 12 14:31:32 SC_13th_SW_AV_ACC_STK_00 secure-dot1xd[29782]: JTASK_SCHED_SLIP: 10 sec scheduler slip, user: 0 sec 74202 usec, system: 0 sec, 45889 usec

Appears on EX4400-MP switches under 24.2R2-S2.5 release.

This is not a critical issue and require no immediate attention.

The log sample captures routine operational telemetry from the 802.1X authentication subsystem (secure-dot1xd daemon) over a brief 1-minute observation window (14:30:32 to 14:31:32). The dominant pattern consists of repetitive task scheduler slip notifications occurring at precise 60-second intervals, indicating active network authentication monitoring with normal scheduling variance.

System resource utilization remains well within acceptable bounds with minimal CPU consumption. No anomalies, hardware failures, control plane issues, or data plane disruptions were detected.

As a summary, The log exhibits expected behavior for a Juniper switch running active 802.1X port authentication services. All observed events fall within normal operational parameters.

In the event you want this logs to be removed from the log file, we suggest applying a syntax like the following:

set system syslog file messages match "!(SECURE_DOT1XD.*JTASK_SCHED_SLIP|JTASK_SCHED_SLIP.*SECURE_DOT1XD)"

!: To exclude the match.

(A.*B|B.*A): This is the regex workaround for an "AND" logic. It matches "A followed by B" OR "B followed by A".

The syslog will only drop the message if both strings are present.

https://supportportal.juniper.net/s/article/Junos-Platform-Example-How-to-prevent-certain-syslog-messages-from-being-written-to-the-log-file