RPI 4, Trunk-Recorder lots of screen logging

Status
Not open for further replies.

TippyTurtle

Member
Joined
Dec 10, 2019
Messages
5
I have 3 SDR's running trunk-recorder recording SmartNet on rebanded 800...all works great. Uploads to OpemMHZ great and everything. It's just that I get insane amounts of logging reading the identical thing (below). How can I reduce this useless (to me) logging?

What I am tracking:
EPSCA Simulcast Site Details (Seattle-King County Public Safety (KCERS))

I have about 70 TalkGroups I am capturing...and none of them are "TalkGroup 6400"

I have TONS of:
2020-01-11 13:08:46.064901] (info) Patching Command: 340 Freq: 0.000000 Talkgroup: 6400

[2020-01-11 13:08:46.532116] (info) Patching Command: 340 Freq: 0.000000 Talkgroup: 6400

[2020-01-11 13:08:47.088493] (info) Patching Command: 340 Freq: 0.000000 Talkgroup: 6400

[2020-01-11 13:08:47.343248] (info) Patching Command: 340 Freq: 0.000000 Talkgroup: 6400

[2020-01-11 13:08:47.484894] (info) Patching Command: 340 Freq: 0.000000 Talkgroup: 6400

[2020-01-11 13:08:47.858382] (info) Patching Command: 340 Freq: 0.000000 Talkgroup: 6400

As a side note I was able to shut down the large amounts of GnuRadio logging by editing /etc/gnuradio/conf.d/gnuradio-runtime.conf to read (among other things): log_level = error

Thanks in advance,
Todd
 
Last edited:

TippyTurtle

Member
Joined
Dec 10, 2019
Messages
5

Correct. Those the the URL's my system is publishing to....when my system doesn't get in a zombie state.

But on my local system, logging is clogged with tons of entries that are hiding real issues I want to watch for.

Does anyone know how to reduce the logging on Trunk-Recorder....or diagnosed the "info" messages to eliminate them?

Thanks again,
Todd
 

jkraemer

Member
Premium Subscriber
Joined
Jun 30, 2015
Messages
60
Location
BEE00
Running trunk recorder using the following command line will filter ALL "Command 340" listings.

taskset 0xFF ./recorder --config=./config.json 3>&1 1>&2 2>&3 | egrep -v "Patching Command: 340|^$" 3>&1 1>&2 2>&3

*Note: the taskset at the beginning instructs the command to use all processor cores.
 
Status
Not open for further replies.
Top