How can I prevent Atlas Probe writing to Syslog?

xsys · November 28, 2022, 9:37am

I see lots of worthless messages in Syslog [http://192.168.1.1/cgi-bin/luci/admin/status/syslog] coming from the Atlas Probe. How can I stop that?


Nov 28 09:15:52 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:15:59 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:16:51 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:17:09 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:17:41 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c&SRC=timesync >> /home/atlas/data/new/main
Nov 28 09:17:55 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:17:55 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:18:51 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:18:58 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:19:08 OmniaDoma eperd[2233]: ping_cb: not busy for state 0x1dad7c0, 'appdownload.itunes.apple.com'
Nov 28 09:19:56 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:20:00 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:20:57 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:20:58 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:21:57 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:22:09 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:22:47 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:23:09 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:24:00 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main
Nov 28 09:24:00 OmniaDoma perd[2231]: USER root pid   0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 28 09:24:46 OmniaDoma perd[2231]: USER root pid   0 cmd httppost -A 9015 --set-time 2 --delete-file --maxpostsize 9000000 --post-header /home/atlas/status/p_to_c_report_header --post-dir /home/atlas/data/out --post-footer /home/atlas/status/con_session_id.txt -O /home/atlas/data/new/main_sent.vol http://127.0.0.1:8080/?PROBE_ID=1000069&SESSION_ID=d6440d629984000805ea09c4cd55123fe1e7d9b11f70d031ecc6d7ff1941ee1c >> /home/atlas/data/new/main

I tried following settings but it does not affect anything:

/etc/config/atlas

option log_stderr ‘0’
option log_stdout ‘0’

commar · November 28, 2022, 10:08am

xsys · November 28, 2022, 10:36am

Yes I saw that, but I wanted to avoid those messages be written to the log, instead of only ignoring that.
There must be a way to prevent a process writing to the Log, but I’m not finding anything relevant.

commar · November 28, 2022, 11:09am

Me neither. Me neither.

xsys · November 30, 2022, 2:42pm

Anyone, please?
Bumping up…

kixorz · November 30, 2022, 9:18pm

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.

kixorz · December 1, 2022, 12:36am

It’s way less spammy, but eooqd and httppost are still pretty loud in the log. I’ll take another look.

kixorz · December 1, 2022, 2:54am

Based on looking at https://github.com/RIPE-NCC/ripe-atlas-probe-measurements/blob/7c03fba082e93b7a1f0f14cc3769bb31e83909e3/eperd/eooqd.c eooqd and https://github.com/RIPE-NCC/ripe-atlas-probe-measurements/blob/7c03fba082e93b7a1f0f14cc3769bb31e83909e3/networking/httppost.c httpost don’t support controlling log levels directly from the command line.

xsys · December 1, 2022, 8:03am

Thanks for sharing, I’m trying now.

system · December 4, 2022, 8:04am

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.