systemd-journal process on the ACX7100-32C is running high CPU utilization.

During protocol convergence with the below configuration in place for ACX7100-32C FPC0, systemd-journal process spiked above 90 percent.

 
pfe> set trace-options host-path packet state extensive all enable

pfe> set trace-options host-path packet port transport

pfe> set trace-options host-path packet port io

pfe> set trace-options host-path packet port port

labroot@h10-44> show system processes extensive | match system   

17971 root    17971 19  0  25584 260052 R 00:00:42 0.4 94.7 systemd-journal

   1 root        1 19  0  22756  10068 S 00:03:48 0.0 0.0 systemd

5437 root     5437 19  0   2636   5584 S 00:00:04 0.0 0.0 systemd-udevd

6146 root     6146 19  0    532   4396 S 00:00:00 0.0 0.0 systemd-logind

19318 root    19318 19  0   5884  10120 S 00:00:00 0.0 0.0 show_system_pro

23110 labroot 23110 19  0   1280   6952 S 00:00:00 0.0 0.0 systemd

labroot@h10-44> show system processes extensive | match system   

17971 root    17971 19  0  17372 273896 R 00:00:46 0.4 95.0 systemd-journal

   1 root        1 19  0  22756  10068 S 00:03:48 0.0 0.0 systemd

5437 root     5437 19  0   2636   5584 S 00:00:04 0.0 0.0 systemd-udevd

6146 root     6146 19  0    532   4396 S 00:00:00 0.0 0.0 systemd-logind

19455 root    19455 19  0   5848  10172 S 00:00:00 0.0 0.0 show_system_pro

23110 labroot 23110 19  0   1280   6952 S 00:00:00 0.0 0.0 systemd

This may cause an issue for CLI operations on the device and latency for the pings.

Killing or restarting the process will not work. It will continue to run high with a new PID.

During protocol convergence, if we set “host-path” to disable, then system-journal returns to normal

labroot@h10-44> start shell

[vrf:none] labroot@h10-44:~$ vty fpc0

labroot@h10-44:pfe> set trace-options host-path packet state disable

Log level set to [Info]

labroot@h10-44:pfe> exit

[vrf:none] labroot@h10-44:~$ exit

exit

labroot@h10-44> show system processes extensive | match system   

    1 root        1 19  0  22756  10068 S 00:03:48 0.0 0.0 systemd

5437 root     5437 19  0   2636   5584 S 00:00:04 0.0 0.0 systemd-udevd

6146 root     6146 19  0    532   4396 S 00:00:00 0.0 0.0 systemd-logind

17971 root    17971 19  0  35564 269056 S 00:01:22 0.4 0.0 systemd-journal

20767 root    20767 19  0   5872  10144 S 00:00:00 0.0 0.0 show_system_pro

23110 labroot 23110 19  0   1280   6952 S 00:00:00 0.0 0.0 systems

Also, once protocol convergence was completed, system-journal returned to normal.

labroot@h10-44> show bgp summary   

Threading mode: BGP I/O

Default eBGP mode: advertise - accept, receive - accept

Groups: 1 Peers: 1 Down peers: 0

Table         Tot Paths Act Paths Suppressed   History Damp State   Pending

inet.0              

                  995104    995104         0         0         0         0

Peer                    AS     InPkt    OutPkt   OutQ  Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...

1.1.1.2              64402      9956        37      0      4      15:55 Establ

 inet.0: 995104/995104/995104/0

labroot@h10-44> show bgp summary   

Threading mode: BGP I/O

Default eBGP mode: advertise - accept, receive - accept

Groups: 1 Peers: 1 Down peers: 0

Table         Tot Paths Act Paths Suppressed   History Damp State   Pending

inet.0              

                  995104    995104         0         0         0         0

Peer                    AS     InPkt    OutPkt   OutQ  Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...

1.1.1.2              64402      9956        37      0      4      15:57 Establ

 inet.0: 995104/995104/995104/0

labroot@h10-44> show system processes extensive | match system   

    1 root        1 19  0  22756  10068 S 00:03:48 0.0 0.0 systemd

5437 root     5437 19  0   2636   5584 S 00:00:04 0.0 0.0 systemd-udevd

6146 root     6146 19  0    532   4396 S 00:00:00 0.0 0.0 systemd-logind

17971 root    17971 19  0  33820 211592 S 00:16:54 0.3 0.0 systemd-journal

23110 labroot 23110 19  0   1280   6952 S 00:00:00 0.0 0.0 systemd

24887 root    24887 19  0   5868  10068 S 00:00:00 0.0 0.0 show_system_pro

Also, rebooting the device will work.