Problem to control Big-Ras controller from Ubuntu 20 client

SatNOGS
1

Hello Satnogs community,

I finished my tracking Yagi antenna and did all s/w installation, but there is one issue left over. I do not know where to look for the bug anymore. Your help would be highly appreciated.

Here is what I did:
1- I installed the Ubuntu 20 client:
https://wiki.satnogs.org/Ubuntu_-_Client_Installation
without much trouble. All services(rigctl, rotctl, satnogsclient) are running. The journal files look good.

2-The satnogs-monitor works fine. It syncs with the webinterface, that is, if I schedule a pass on the satnogs webinterface, the monitor correctly shows the next pass

3-I can control azimuth and elevation my controller using rotctl -m 901 -r /dev/ttyUSB0 -s 115200 . (/etc/default/hamlib-util has the rotator options)

But when I schedule a pass on the satnogs web interface, the rotator won’t rotate. Somehow, the connection between the satnogs service and the rotctl service fails.

If you had a hunch where I could look for trouble - that would be great.

Cheers. Jan

2

Good afternoon, I use -s 9600

Julio // LW2DYB

3

Hi Jan,
Do you use rotctl or rotctld ? What is the relevant configuration in -client ?
You can increase the log level to INFO and you will see a bunch more chatter that might reveal what is going on.
I am using a Spid-Ras with MD-03.

4

thank you. I am reasonable confident to use the right options for rotctl because when I use it manually (not the system service), it works.
Cheers. Jan

5

Hello and thank you.

I am afraid, I do not know how to increase the log level in the Ubuntu 20 client. Would you mind to tell how to do this?

For the configuration: please see below the content of the systemd config files:

------------------ CONTENT OF SYSTEM SERVICES CONFIG FILES

sudo nano /etc/default/satnogs-client

PYTHONPATH=/usr/local/lib/python3/dist-packages
SATNOGS_API_TOKEN=“cd74e3xxxxxx0c2367”
SATNOGS_STATION_ID=“3533”
SATNOGS_STATION_LAT=“49.626”
SATNOGS_STATION_LON=“6.159”
SATNOGS_STATION_ELEV=“350”
SATNOGS_SOAPY_RX_DEVICE=“driver=hackrf”
SATNOGS_RF_GAIN=“64”
SATNOGS_RX_SAMP_RATE=“8e6”
SATNOGS_ANTENNA=“TX/RX”
UDP_DUMP_HOST=“127.0.0.1”

sudo nano /etc/systemd/system/rotctld.service

[Unit]
Description=rotctld server

[Service]
EnvironmentFile=-/etc/default/hamlib-utils
ExecStart=/usr/bin/rotctld $ROT_OPTS
Restart=on-failure
User=satnogs
Group=satnogs

[Install]
WantedBy=multi-user.target

sudo nano /etc/systemd/system/rigctld.service

[Unit]
Description=rigctld server

[Service]
EnvironmentFile=-/etc/default/hamlib-utils
ExecStart=/usr/bin/rigctld $RIG_OPTS
Restart=on-failure
User=satnogs
Group=satnogs

[Install]
WantedBy=multi-user.target

sudo nano /etc/default/hamlib-utils

ROT_OPTS=“-m 901 -r /dev/ttyUSB0 -s 115200”
RIG_OPTS=“-T 127.0.0.1 -m 1”
------------------END CONTENT OF SYSTEM SERVICES CONFIG FILES

I thought I also post the systemd service status, which is not suspicious:

------------------STATUS SYSTEM SERVICES

remoteuser@ubadmin-PowerEdge-R210:/tmp$ sudo systemctl status rigctld.service
● rigctld.service - rigctld server
Loaded: loaded (/etc/systemd/system/rigctld.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-04-15 14:53:05 UTC; 1 day 5h ago
Main PID: 504 (rigctld)
Tasks: 1 (limit: 9410)
Memory: 6.0M
CGroup: /system.slice/rigctld.service
└─504 /usr/bin/rigctld -T 127.0.0.1 -m 1

Apr 15 14:53:05 ubadmin-PowerEdge-R210 systemd[1]: Started rigctld server.

remoteuser@ubadmin-PowerEdge-R210:/tmp$ sudo systemctl status rotctld.service
● rotctld.service - rotctld server
Loaded: loaded (/etc/systemd/system/rotctld.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-04-16 12:25:47 UTC; 8h ago
Main PID: 7357 (rotctld)
Tasks: 1 (limit: 9410)
Memory: 1.5M
CGroup: /system.slice/rotctld.service
└─7357 /usr/bin/rotctld -m 901 -r /dev/ttyUSB0 -s 115200

Apr 16 12:25:47 ubadmin-PowerEdge-R210 systemd[1]: Started rotctld server.

remoteuser@ubadmin-PowerEdge-R210:/tmp$ sudo systemctl status satnogs-client.service
● satnogs-client.service - SatNOGS client
Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-04-15 14:58:57 UTC; 1 day 5h ago
Main PID: 2137 (satnogs-client)
Tasks: 5 (limit: 9410)
Memory: 656.1M
CGroup: /system.slice/satnogs-client.service
└─2137 /var/lib/satnogs/bin/python /var/lib/satnogs/bin/satnogs-client

Apr 15 20:09:55 ubadmin-PowerEdge-R210 satnogs-client[3577]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 15 20:29:18 ubadmin-PowerEdge-R210 satnogs-client[3648]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 11:19:54 ubadmin-PowerEdge-R210 satnogs-client[5250]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 11:28:08 ubadmin-PowerEdge-R210 satnogs-client[5306]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 11:36:19 ubadmin-PowerEdge-R210 satnogs-client[5372]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 11:55:16 ubadmin-PowerEdge-R210 satnogs-client[6417]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 12:08:16 ubadmin-PowerEdge-R210 satnogs-client[7000]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 12:21:16 ubadmin-PowerEdge-R210 satnogs-client[7273]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 12:34:16 ubadmin-PowerEdge-R210 satnogs-client[7642]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 16 12:47:16 ubadmin-PowerEdge-R210 satnogs-client[7716]: [INFO] Opening HackRF One #0 f77c60dc255784c3…

------------------END STATUS SYSTEM SERVICES

I would appreciate any hunch on where I still could look for a bug.

Good night, 73, LX9SNT
Jan

6

I use docker for my stations, so no satnogs-setup, I just set SATNOGS_LOG_LEVEL=INFO in the env.

By the looks of it, you should set the SATNOGS_ROT_* variables as well.
https://docs.satnogs.org/projects/satnogs-client/en/stable/userguide.html#satnogs-rot-model
for example:

SATNOGS_ROT_MODEL=ROT_MODEL_NETROTCTL
SATNOGS_ROT_PORT=localhost:4533

With that setup, is rotctld available over tcp ? I use this to test connectivity: echo "+p" | nc -w 1 localhost 4533 it should return something like

get_pos:
Azimuth: 47.00
Elevation: 6.00
RPRT 0

Another issue I’ve seen is the default available range is not suitable for satnogs (that is shown in the logs).
This is was I have been using in ROT_OPTS: --set-conf=min_az=0,max_az=360,min_el=0,max_el=180

7

Hello SA2KNG,

thanks a lot.

I did not know where to put the SATNOGS_ROT_MODEL/ SATNOGS_ROT_PORT variable. So I tried the echo "+p" | nc -w 1 localhost 4533 without them. It works. I can control the rotator.

The --set-conf=min_az=0,max_az=360,min_el=0,max_el=180 did unfortunately not change anything.

However, I am very sorry, I was sloppy, in contrast to what I said above, there is an error message in a satnogs-service journal file:
" Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))" (complete journal content below).
So, some TCP problem is present.

The satnogs webinterface can see my groundstation 3533 and the satnogs-monitor is synced to the webinterface too.
I am able to ping network.satnogs.org and a
“nc -zv network.satnogs.org 443”
gives
“Connection to network.satnogs.org 443 port [tcp/https] succeeded!”

Do you have any hunch where I could look further?

Any idea is extremely welcome.

Jan

---------------------------------- BEGIN ---------------------------------------
– Reboot –
Apr 17 10:45:14 ubadmin-PowerEdge-R210 systemd[1]: Started SatNOGS client.
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: satnogsclient.scheduler.tasks - ERROR - An error occurred trying to GET observation jobs from network
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: Traceback (most recent call last):
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 159, in _new_conn
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: conn = connection.create_connection(
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/util/connection.py”, line 61, in create_connection
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3.8/socket.py”, line 918, in getaddrinfo
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: socket.gaierror: [Errno -3] Temporary failure in name resolution
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: During handling of the above exception, another exception occurred:
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: Traceback (most recent call last):
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 666, in urlopen
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: httplib_response = self._make_request(
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 377, in _make_request
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: self._validate_conn(conn)
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 1001, in _validate_conn
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: conn.connect()
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 314, in connect
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: conn = self._new_conn()
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 171, in _new_conn
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: raise NewConnectionError(
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7f6fe2274b50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: During handling of the above exception, another exception occurred:
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: Traceback (most recent call last):
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/adapters.py”, line 489, in send
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: resp = conn.urlopen(
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 720, in urlopen
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: retries = retries.increment(
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/usr/lib/python3/dist-packages/urllib3/util/retry.py”, line 436, in increment
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: raise MaxRetryError(_pool, url, error or ResponseError(cause))
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=3533&lat=49.626&lon=6.159&alt=350 (Caused by NewConnectionError(‘<urllib3.connection.VerifiedHTTPSConnection object at 0x7f6fe2274b50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: During handling of the above exception, another exception occurred:
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: Traceback (most recent call last):
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/satnogsclient/scheduler/tasks.py”, line 191, in get_jobs
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: response = requests.get(url,
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/api.py”, line 73, in get
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: return request(“get”, url, params=params, **kwargs)
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/api.py”, line 59, in request
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: return session.request(method=method, url=url, **kwargs)
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/sessions.py”, line 587, in request
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: resp = self.send(prep, **send_kwargs)
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/sessions.py”, line 701, in send
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: r = adapter.send(request, **kwargs)
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/adapters.py”, line 565, in send
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: raise ConnectionError(e, request=request)
Apr 17 10:45:37 ubadmin-PowerEdge-R210 satnogs-client[518]: requests.exceptions.ConnectionError: HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=3533&lat=49.626&lon=6.159&alt=350 (Caused by NewConnectionError(‘<urllib3.connection.VerifiedHTTPSConnection object at 0x7f6fe2274b50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: rot_init called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: dummy: _init called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: rot_register (1)
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: rot_register (2)
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: dummy_rot_init called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: rot_open called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: dummy_rot_open called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: rot_get_position called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: dummy_rot_get_position called
Apr 17 10:55:11 ubadmin-PowerEdge-R210 satnogs-client[518]: rot_set_position called
Apr 17 10:55:16 ubadmin-PowerEdge-R210 satnogs-client[1651]: [INFO] Opening HackRF One #0 f77c60dc255784c3…
Apr 17 11:07:04 ubadmin-PowerEdge-R210 satnogs-client[1733]: [INFO] Opening HackRF One #0 f77c60dc255784c3…

----------------------------------- END --------------------------------------

8

This indicates that the -client does not have rotator enabled.
The SATNOGS_ROT_MODEL and SATNOGS_ROT_PORT goes into /etc/default/satnogs-client if you’re not using satnogs-setup (with -setup it’s generated and overwritten).

If there’s connectivity issues like requests.exceptions.ConnectionError it can be either the satnogs servers or on your side, do note that sporadic timeouts from satnogs is expected.
Temporary failure in name resolution does not look too good and points to dns issue on that host.

9

Thanks a lot!

I inserted:

SATNOGS_ROT_MODEL=ROT_MODEL_SPID_ROT2PROG
SATNOGS_ROT_PORT=localhost:4533

and the dummy_rot_init message disappeared. Nice.
But the “localhost:4533” options is not accepted. I also tried /dev/ttyUSB0 and " /dev/ttyUSB0" which resulted in error messages.

I will try a bit more tomorrow and post the error messages.

Thanks so far!

Jan

10

You either let -client speak directly to the hardware (via it’s own rotctl) or you have a service (rotctld) running that connects to the hardware and the client connects to that instance via tcp.

This one connects to a rotctld running on localhost (or on the network) as a service or similar:

SATNOGS_ROT_MODEL=ROT_MODEL_NETROTCTL
SATNOGS_ROT_PORT=localhost:4533

While this one connects to the hardware directly (and only one can use it):

SATNOGS_ROT_MODEL=ROT_MODEL_SPID_ROT2PROG
SATNOGS_ROT_PORT=/dev/ttyUSB0

NETROTCTL is the tcp network protocol that allows rotctl connect to a rotctld (notice the d) and it takes host:port as destination, the others take a device as argument and also needs baud etc to work.

I advice running a rotctld as a service, that makes it easy to monitor and test it at the same time -client is using it. In this case you need to specify what rotator, device and baud etc to that service. And the client and others use the NETROTCTL model to talk to it.

11

Hello SA2KNG,
thank you for these explanations. They make a lot sense.

So, I put:

SATNOGS_ROT_MODEL=ROT_MODEL_NETROTCTL
SATNOGS_ROT_PORT=localhost:4533

into:
‘/etc/default/satnogs-client’ .
If I do ‘echo “+P 0 90” | nc -w 1 localhost 4533’ , my rotator rotates perfectly.

But the satnogs client journal file still contains the network connectivity error messages(see very end of message), which is, most likely, the reason my rotator does not rotate when the satnogsclient wants it to. The satnogs-monitor continues to be sync’ed with the satnogs webinterface: it shows my pass planning. So, somehow my PC connects to satnogs.

Thanks for bearing with me for this tricky problem. If you have a further suggestion, I would appreciate it.

Cheers. Jan

– Reboot –
Apr 18 12:55:57 ubadmin-PowerEdge-R210 systemd[1]: Started SatNOGS client.
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: satnogsclient.scheduler.tasks - ERROR - An error occurred trying to GET observation jobs from network
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: Traceback (most recent call last):
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 159, in _new_conn
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: conn = connection.create_connection(
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/util/connection.py”, line 61, in create_connection
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3.8/socket.py”, line 918, in getaddrinfo
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: socket.gaierror: [Errno -3] Temporary failure in name resolution
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: During handling of the above exception, another exception occurred:
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: Traceback (most recent call last):
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 666, in urlopen
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: httplib_response = self._make_request(
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 377, in _make_request
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: self._validate_conn(conn)
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 1001, in _validate_conn
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: conn.connect()
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 314, in connect
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: conn = self._new_conn()
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 171, in _new_conn
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: raise NewConnectionError(
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7fc17280f250>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: During handling of the above exception, another exception occurred:
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: Traceback (most recent call last):
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/adapters.py”, line 489, in send
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: resp = conn.urlopen(
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 720, in urlopen
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: retries = retries.increment(
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/usr/lib/python3/dist-packages/urllib3/util/retry.py”, line 436, in increment
Apr 18 12:56:19 ubadmin-PowerEdge-R210 satnogs-client[507]: raise MaxRetryError(_pool, url, error or ResponseError(cause))
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=3533&lat=49.626&lon=6.159&alt=350 (Caused by NewConnectionError(‘<urllib3.connection.VerifiedHTTPSConnection object at 0x7fc17280f250>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: During handling of the above exception, another exception occurred:
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: Traceback (most recent call last):
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/satnogsclient/scheduler/tasks.py”, line 191, in get_jobs
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: response = requests.get(url,
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/api.py”, line 73, in get
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: return request(“get”, url, params=params, **kwargs)
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/api.py”, line 59, in request
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: return session.request(method=method, url=url, **kwargs)
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/sessions.py”, line 587, in request
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: resp = self.send(prep, **send_kwargs)
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/sessions.py”, line 701, in send
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: r = adapter.send(request, **kwargs)
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: File “/var/lib/satnogs/lib/python3.8/site-packages/requests/adapters.py”, line 565, in send
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: raise ConnectionError(e, request=request)
Apr 18 12:56:20 ubadmin-PowerEdge-R210 satnogs-client[507]: requests.exceptions.ConnectionError: HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=3533&lat=49.626&lon=6.159&alt=350 (Caused by NewConnectionError(‘<urllib3.connection.VerifiedHTTPSConnection object at 0x7fc17280f250>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))

12

The network issue is probably blocking the client from finding out what to do. Or did?
https://network.satnogs.org/api/jobs/?ground_station=3533&lat=49.626&lon=6.159&alt=350
This url, as indicated in the log, works and looks good.
Looking at recent observations it certainly looks like the observations is running.
https://network.satnogs.org/observations/9385332/
It has the characteristic EMI patterns of a station with a rotator that isn’t grounded/filtered properly.
At the same time, not properly tracking SO-50, as it is diminished in the beginning/end:
https://network.satnogs.org/observations/9385323/
Similar this obs that was done with the rotator statically pointed straight up:
https://network.satnogs.org/observations/9053246/
Please fill in any details that can help here.

13

Hello SAKNG,

you are absolutely right. We are rotating. This is awesome. Sorry that I concluded yesterday it is still faulty.
I will look into grounding and also the correct elevation/azimuth calibration.

Thanks a lot for your help. You are great!

Jan

1 Like