Hi!
First of all if you use jtdx, wsjtx or any other program that uses your rig cat control you can not get Cqrlog work properly when checking "run rigctld when program starts" at same time those other programs are running.

Using linux it is possible to connect to same serial port with several programs. It may chaos if all programs are writing to serial port. Listeners are ok.
With Windoze it will say "com port is already in use", or something like that.

Recommended reading:
https://github.com/OH1KH/CqrlogAlpha/blob/main/compiled/setting_rigctld_...

That will explain how to do settings.

I have two rigs. I use a script to start rigctld for both ones together *before* I start any other program.
Both rigctlds start as daemons and keep running there until I stop them or close PC.

In Cqrlog settings I use:

rig1: Model Hamlib Net rigctld , Host: localhost, Port:4532, Poll rate: 1000, "run rigctld when program starts": unchecked (other settings are not needed)

rig2: Model Hamlib Net rigctld , Host: localhost, Port:14532, Poll rate: 1000, "run rigctld when program starts": unchecked (other settings are not needed)

The only difference is Port number.

Then within my script where rigctlds for both rigs are started, parameter "-t" sets equal port numbers 4532 and 14532. That way two rigctlds can run at same time, separated.

For other programs wsjtx. jtdx, qsstv, fldigi, gpredict I always use rig model "Hamlib Net rigctld" and corresponding port number what rig I want to use.
If I ever change rigs only script must be modified. All programs will keep their rig settings as was.

That is just what the PDF link above explains.

Script is named "srig" ("start rig") and without extension ".sh". It is placed in ~/.local/bin where user binaries exist.
srig (restarts rigs, or start them if not stated yet)
srig restart (restarts rigs, or start them if not stated yet)
srig stop (stops rigs)
srig v (starts rig 1, IC7300 without --vfo parameter)

NOTE: with old Cqrlog, as yours seem's to be, you can not use rigctld start parameter "--vfo" as then the command syntax changes and Cqrlog can not command rigctld properly.

Script writes start log to /tmp/srig.log
With rigctld parameters "-vvvvv -Z >" it writes rigctld debug to file.

My debug files for rigs are /tmp/rig7300log%Y%m%d%H%M.txt and /tmp/rig706log%Y%m%d%H%M.txt they are set at start of script.
I.E. rig name and day+time when rigctld started.
(that is what you were missing in your message to see rigctld errors)

You have also checked "show communication with TRX in console" and if you want communication into file too you need to start Cqrlog from command console:
cqrlog > /tmp/cqrlog.log

using only:
cqrlog
You see rig communication in console, but it scrolls and is hard to study afterwards.