Client not able to connect to network.satnogs.org

kb0fx · July 15, 2020, 10:12pm

Team - I just installed the latest version of the client on a Raspberry Pi 3B. I was able to initially able to successfully schedule and retrieve some test observations. Then I installed the RPI in a weather proof box directly under my antenna. The RPI is connected via Ethernet. I am able to Traceroute from the RPI to network.satnogs.org port 443. My logs are below.

Thanks!

● satnogs-client.service - SatNOGS client
Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-07-15 18:42:36 UTC; 2h 0min ago
Main PID: 325 (satnogs-client)
Tasks: 22 (limit: 2200)
Memory: 72.8M
CGroup: /system.slice/satnogs-client.service
└─325 /var/lib/satnogs/bin/python3 /var/lib/satnogs/bin/satnogs-client

Jul 15 20:27:52 satnogs satnogs-client[325]: return request(‘get’, url, params=params, **kwargs)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/requests/api.py”, line 60, in request
Jul 15 20:27:52 satnogs satnogs-client[325]: return session.request(method=method, url=url, **kwargs)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/requests/sessions.py”, line 533, in request
Jul 15 20:27:52 satnogs satnogs-client[325]: resp = self.send(prep, **send_kwargs)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/requests/sessions.py”, line 646, in send
Jul 15 20:27:52 satnogs satnogs-client[325]: r = adapter.send(request, **kwargs)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/requests/adapters.py”, line 516, in send
Jul 15 20:27:52 satnogs satnogs-client[325]: raise ConnectionError(e, request=request)
Jul 15 20:27:52 satnogs satnogs-client[325]: requests.exceptions.ConnectionError: HTTPSConnectionPool(host=‘network.satnogs.org’, port=443):
Max retries exceeded with url: /api/jobs/?ground_station=1380&lat=38.695&lon=-90.46&alt=174 (Caused by NewConnectionError(’<urllib3.connection.VerifiedHTTPSConnection object at
0x72f3d730>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution
~

Jul 15 20:27:52 satnogs satnogs-client[325]: apscheduler.executors.default - ERROR - Job “get_jobs (trigger: interval[0:01:00], next run at: 2020-07-15 20:28:42 UTC)”
Jul 15 20:27:52 satnogs satnogs-client[325]: Traceback (most recent call last):
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 159, in _new_conn
Jul 15 20:27:52 satnogs satnogs-client[325]: (self._dns_host, self.port), self.timeout, **extra_kw)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/util/connection.py”, line 57, in create_connection
Jul 15 20:27:52 satnogs satnogs-client[325]: for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3.7/socket.py”, line 748, in getaddrinfo
Jul 15 20:27:52 satnogs satnogs-client[325]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
Jul 15 20:27:52 satnogs satnogs-client[325]: socket.gaierror: [Errno -3] Temporary failure in name resolution
Jul 15 20:27:52 satnogs satnogs-client[325]: During handling of the above exception, another exception occurred:
Jul 15 20:27:52 satnogs satnogs-client[325]: Traceback (most recent call last):
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 600, in urlopen
Jul 15 20:27:52 satnogs satnogs-client[325]: chunked=chunked)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 343, in _make_request
Jul 15 20:27:52 satnogs satnogs-client[325]: self._validate_conn(conn)
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/connectionpool.py”, line 841, in _validate_conn
Jul 15 20:27:52 satnogs satnogs-client[325]: conn.connect()
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 301, in connect
Jul 15 20:27:52 satnogs satnogs-client[325]: conn = self._new_conn()
Jul 15 20:27:52 satnogs satnogs-client[325]: File “/usr/lib/python3/dist-packages/urllib3/connection.py”, line 168, in _new_conn
Jul 15 20:27:52 satnogs satnogs-client[325]: self, “Failed to establish a new connection: %s” % e)
Jul 15 20:27:52 satnogs satnogs-client[325]: urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x72f3d730>: Failed to estab

Acinonyx · July 16, 2020, 8:27am

Your DNS is or was failing at that moment.

kb0fx · July 16, 2020, 11:44am

Vasilis - The DNS was not failing. See the traceroute I just ran from the RPI below. I have also included the Support Report output.

pi@satnogs:~ $ traceroute network.satnogs.org -p 443
traceroute to network.satnogs.org (94.130.162.100), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 4.775 ms 4.612 ms 5.692 ms
2 * * *
3 dtr01ovldmo-tge-0-3-0-23.ovld.mo.charter.com (96.34.56.113) 32.643 ms 32.7 43 ms 32.658 ms
4 crr01ovldmo-bue-100.ovld.mo.charter.com (96.34.49.220) 32.562 ms 32.273 ms 32.383 ms
5 crr02blvlil-bue-200.blvl.il.charter.com (96.34.76.131) 32.298 ms 32.210 ms 32.120 ms
6 bbr01blvlil-bue-110.blvl.il.charter.com (96.34.2.170) 32.031 ms 43.698 ms 46.851 ms
7 bbr01olvemo-bue-3.olve.mo.charter.com (96.34.0.14) 45.576 ms 27.772 ms 36 .298 ms
8 bbr02chcgil-bue-2.chcg.il.charter.com (96.34.0.12) 30.616 ms 35.873 ms 36 .130 ms
9 prr01chcgil-bue-4.chcg.il.charter.com (96.34.3.11) 30.321 ms 35.863 ms 35 .856 ms
10 4.68.127.133 (4.68.127.133) 35.760 ms 35.589 ms 19.857 ms
11 * * *
12 ae0-3356.lon10.core-backbone.com (212.113.8.42) 123.381 ms 123.286 ms 124 .332 ms
13 ae10-2021.fra20.core-backbone.com (80.255.14.6) 123.280 ms 123.054 ms 122 .961 ms
14 core-backbone.hetzner.com (80.255.15.122) 142.471 ms 133.883 ms 142.282 m s
15 core23.fsn1.hetzner.com (213.239.224.249) 142.694 ms core24.fsn1.hetzner.co m (213.239.224.253) 135.083 ms *
16 ex9k2.dc4.fsn1.hetzner.com (213.239.229.134) 138.312 ms ex9k2.dc4.fsn1.hetz ner.com (213.239.229.130) 139.684 ms ex9k2.dc4.fsn1.hetzner.com (213.239.229.13 4) 138.129 ms
17 srv01.libre.space (94.130.162.100) 138.903 ms !X 134.135 ms !X 137.545 ms !X

kb0fx · July 16, 2020, 11:49am

Vasilis - The Support Report is below.

Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.3.2”,
“satnogs-client-ansible”: “202006062329”,
“satnogs-flowgraphs”: “1.2.1-1”,
“gr-satnogs”: “2.1.2.1-1”,
“gr-soapy”: “2.1.3-1”,
“gnuradio”: “3.8.1.0~rc1-2”,
“satnogs-config”: “0.10.2”
},
“state”: {
“is-applied”: false,
“pending-tags”: null
},
“system”: {
“date”: “2020-07-16T00:02:33.547726+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: false,
“platform”: {
“system”: “Linux”,
“node”: “satnogs”,
“release”: “4.19.118-v7+”,
“version”: “#1311 SMP Mon Apr 27 14:21:24 BST 2020”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 971038720,
“available”: 790102016,
“percent”: 18.6,
“used”: 116772864,
“free”: 554491904,
“active”: 146763776,
“inactive”: 201826304,
“buffers”: 27553792,
“cached”: 272220160,
“shared”: 6467584,
“slab”: 48893952
},
“disk”: {
“total”: 31090814976,
“used”: 3879776256,
“free”: 25900580864,
“percent”: 13.0
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “8”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “174”,
“satnogs_station_id”: “1380”,
“satnogs_station_lat”: “38.695”,
“satnogs_station_lon”: “-90.460”
}
}
------------[ copy end ]-------------

Acinonyx · July 16, 2020, 9:15pm

Your support report looks good. [Errno -3] Temporary failure in name resolution indicates a DNS resolution error.

mfalkvidd · July 16, 2020, 9:31pm

Note: traceroute will use udp by default, and the -p option will work like this: For UDP tracing, specifies the destination port base traceroute will use (the destination port number will be incremented by each probe).

Not that it matters that much for the traceroute result, but your traceroute does not test the https port.

kb0fx · July 17, 2020, 9:53pm

I have resolved the DNS issue. I did not have IPV6 enabled on my router. Now I have an issue with apscheduler. See the error log below.

pi@satnogsclient:~ $ journalctl -u satnogs-client
– Logs begin at Fri 2020-07-17 20:17:01 UTC, end at Fri 2020-07-17 20:39:18 UTC. –
Jul 17 20:25:02 satnogsclient systemd[1]: Started SatNOGS client.
Jul 17 20:28:48 satnogsclient satnogs-client[333]: apscheduler.executors.default - WARNING - Run time of job “get_jobs
(trigger: interval[0:01:00], next run at: 2020-07-17 20:26:08 UTC)” was missed by 0:00:40.036647
Jul 17 20:28:48 satnogsclient satnogs-client[333]: apscheduler.executors.default - WARNING - Run time of job “post_data
(trigger: interval[0:03:00], next run at: 2020-07-17 20:31:08 UTC)” was missed by 0:00:40.039221

Acinonyx · July 18, 2020, 9:38am

Maybe your system clock is not synchronized with an NTP. Check that NTP servers are accessible.

kb0fx · July 20, 2020, 2:29am

Problem Resolved. My 5 volt power supply did not have enough current. I was using a 12 volt to 5 volt converter. I replaced that with a 5 volt wall wart an that resolved the issue.

Thank you for your help!