Since I know my probe was also this spammy, I’ve decided to take a look at this issue.
The source for the package comes from here: packages/net/atlas-probe at openwrt-21.02 · openwrt/packages · GitHub
From looking at GitHub - RIPE-NCC/ripe-atlas-probe-measurements: RIPE Atlas probe measurement source code it seems like there is a known logging verbosity problem.
Closer look at https://github.com/RIPE-NCC/ripe-atlas-probe-measurements/blob/7c03fba082e93b7a1f0f14cc3769bb31e83909e3/eperd/eperd.c reveals that there’s a -l <loglevel> option.
From looking at my setup with grep "eperd" /usr/local/atlas/bin/ATLAS:
eperd -I br-lan -c $BASE_DIR/crons/7 -A 9807 -P $RUN_DIR/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7
eperd -c $BASE_DIR/crons/7 -A 9807 -P $RUN_DIR/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7
it seems like that can be set in the /usr/local/atlas/bin/ATLAS script. I changed both perd and eperd lines in this file to look like this:
perd -l 10 -c $BASE_DIR/crons/main -A 9801 -P $RUN_DIR/perd-main.pid.vol
perd -l 10 -c $BASE_DIR/crons/2 -A 9802 -P $RUN_DIR/perd-2.pid.vol
eperd -l 10 -I br-lan -c $BASE_DIR/crons/7 -A 9807 -P $RUN_DIR/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7
eperd -l 10 -c $BASE_DIR/crons/7 -A 9807 -P $RUN_DIR/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7
Seems like the log is now quiet, but I’ll keep an eye on it.