Query messaging from satnogs-client.service

Can anyone please explain the following date/time messages?

$ systemctl status satnogs-client
● satnogs-client.service - SatNOGS client
Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-06-06 15:31:38 BST; 19h ago
Main PID: 436 (satnogs-client)
Tasks: 5 (limit: 3723)
CPU: 2h 23min 14.052s
CGroup: /system.slice/satnogs-client.service
└─436 /var/lib/satnogs/bin/python /var/lib/satnogs/bin/satnogs-client

Jun 07 02:43:00 snogs2122 satnogs-client[3553]: [INFO] Using format CF32.
Jun 07 02:50:50 snogs2122 satnogs-client[436]: netrigctl_close: done status=Command completed successfully
Jun 07 08:50:08 snogs2122 satnogs-client[436]: rig_init: rig does not have rx_range!!
Jun 07 08:50:08 snogs2122 satnogs-client[436]: network_open: hoststr=127.0.0.1, portstr=4532
Jun 07 08:50:10 snogs2122 satnogs-client[4520]: [INFO] Using format CF32.
Jun 07 08:57:24 snogs2122 satnogs-client[436]: netrigctl_close: done status=Command completed successfully
Jun 07 10:21:10 snogs2122 satnogs-client[436]: rig_init: rig does not have rx_range!!
Jun 07 10:21:10 snogs2122 satnogs-client[436]: network_open: hoststr=127.0.0.1, portstr=4532
Jun 07 10:21:12 snogs2122 satnogs-client[4804]: [INFO] Using format CF32.
Jun 07 10:32:40 snogs2122 satnogs-client[436

[INFO] Using format CF32. from the flowgraph, I think soapy and depending on sdr.
netrigctl_close: done status=Command completed successfully flowgraph done with doppler control.
rig_init: rig does not have rx_range!! benign warning from hamlib.

Many thanks for your response, Daniel.
However, why do I not see the same output as that shown in 'Verification of Correct Installation" within the SatNOGS Client Setup wiki? And there’s no mention of this in the Troubleshooting Guide, when I was exploring it?
I’m using an Airspy R2 and the changes required to the installation as against using a RTLSDR are still not added to the Airspy section of the Software Defined Radio wiki, which was suggested by @SM0TGU back in Nov’22.
Is it time for a re-write of the wikis - by someone with a higher pay-grade than myself?