Actually I very recently discussed this same subject on some other forums, and found the appropriate article on Juniper KB: KB94473
Quite simple: the trace process (ifstraced) that logs those (useless and massive) routing change data (since JunOS 17.4) is very easy to disable (but with a hidden command):
set system processes ifstate-tracing-process disable
Result:
> show log ifstraced | last 1 | no-more
ifstraced: [go_trace:488] Received signal SIGINT or SIGTERM, shutting down ifstraced
Job done, no more TB of useless stuff wearing out the SSD.
------------------------------
Olivier Benghozi
------------------------------
Original Message:
Sent: 06-11-2026 23:03
From: UKDSL
Subject: "ifstraced" logfile
Bumping this up as we'd also like to disable this log.
We have this writing 24MB/minute on our edge Juniper routers.
Original Message:
Sent: 10-15-2022 11:21
From: PreArt
Subject: "ifstraced" logfile
I have updated the system to 21.4R3.15
21.4R3 is marked as RESOLVED IN for PR1654737 , but /var/log/ifstraced is still being filled
Is there a way to disable this log?
Original Message:
Sent: 10-09-2022 12:00
From: STEVE PULUKA
Subject: "ifstraced" logfile
You might be hitting this issue fixed with upgrade to the listed versions.
https://prsearch.juniper.net/problemreport/PR1654737
------------------------------
Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
http://puluka.com/home
------------------------------