Troubleshooting Legacy - Revision history

Acinonyx: Undo revision 3949 by Fredy (talk)

2025-03-21T08:38:03Z

Undo revision 3949 by Fredy (talk)

Acinonyx: Acinonyx moved page Troubleshooting to Troubleshooting Legacy without leaving a redirect

2025-03-21T08:32:46Z

Acinonyx moved page Troubleshooting to Troubleshooting Legacy without leaving a redirect

Fredy: /* Client troubleshooting */

2025-02-20T04:05:35Z

‎Client troubleshooting

Kerel+satnogs: Add "Observer job lock acquiring timed out" section

2024-03-04T09:51:43Z

Add "Observer job lock acquiring timed out" section

Fredy: /* Invalid Signature for download.opensuse.org */ Fix formatting

2024-02-26T11:29:21Z

‎Invalid Signature for download.opensuse.org: Fix formatting

Gpoverby: Update instructions to fix the Invalid Signature error

2024-02-23T23:52:33Z

Update instructions to fix the Invalid Signature error

Fredy at 08:58, 25 June 2022

2022-06-25T08:58:10Z

Danwhite: /* Client troubleshooting */ add note about including the support report menu output when getting help.

2022-05-23T13:29:13Z

‎Client troubleshooting: add note about including the support report menu output when getting help.

Fredy: /* Raise or Set the debug level */

2021-06-14T13:07:47Z

‎Raise or Set the debug level

Jacquin01: /* apt-get update: connection failed */

2021-04-12T18:53:40Z

‎apt-get update: connection failed

@@ Line 2: / Line 2: @@
 ==Client troubleshooting==
-{{Message| Before starting check the logs for an error (there are two different commands depending on the installation way):
+{{Message| Before starting check the logs for an error:
-* Check the whole error log with either <code>journalctl -u satnogs-client.service</code> (old version) or <code>sudo docker logs satnogs_satnogs-client</code> (new version)
-* Check live the error log with either <code>journalctl -f -u satnogs-client.service</code> (old version) or <code>sudo docker logs -f satnogs_satnogs-client</code> (new version)}}
+* Check the whole error log with <code>journalctl -u satnogs-client.service</code>
 {{Message|If the hints for common issues below don't help solve your issue, you are welcome to post in the forum.  When doing so, please include any error from the logs and the output of the support report generated by the menu item <code>Advanced -> Support</code> from <code>sudo satnogs-setup</code>. This helps give context to the logging messages.}}

@@ Line 2: / Line 2: @@
 ==Client troubleshooting==
-{{Message| Before starting check the logs for an error:
+{{Message| Before starting check the logs for an error (there are two different commands depending on the installation way):
+* Check the whole error log with either <code>journalctl -u satnogs-client.service</code> (old version) or <code>sudo docker logs satnogs_satnogs-client</code> (new version)
-* Check the whole error log with <code>journalctl -u satnogs-client.service</code>
+* Check live the error log with either <code>journalctl -f -u satnogs-client.service</code> (old version) or <code>sudo docker logs -f satnogs_satnogs-client</code> (new version)}}
 {{Message|If the hints for common issues below don't help solve your issue, you are welcome to post in the forum.  When doing so, please include any error from the logs and the output of the support report generated by the menu item <code>Advanced -> Support</code> from <code>sudo satnogs-setup</code>. This helps give context to the logging messages.}}

← Older revision		Revision as of 09:51, 4 March 2024
Line 101:		Line 101:

	This rule must be modified to allow the raspberry to access the repository		This rule must be modified to allow the raspberry to access the repository
		+
		+	=== ERROR - Observer job lock acquiring timed out. ===
		+
		+	<pre>
		+	Mar 03 20:05:53 satnogs satnogs-client[257]: satnogsclient.scheduler.tasks - ERROR - Observer job lock acquiring timed out.
		+	</pre>
		+
		+	This message is shown when a previous Observation failed (due to a hardware issue or some bug) and didn't properly terminate. To fix this issue, first check the logs for the observation that failed to understand the root cause. Then, restart satnogs-client.

	==Signal troubleshooting==		==Signal troubleshooting==

@@ Line 70: / Line 70: @@
 ===Invalid Signature for download.opensuse.org===
 Example error during satnogs-setup update or apt-get update:
-   <code>The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:[[Mailto:librespace@build.opensuse.org|librespace@build.opensuse.org]]></code>
 Fix:
-<code>
- wget -qO - <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki> > k
+<pre>
- gpg --no-default-keyring --keyring ./temp-keyring.gpg --import k
+wget -qO - http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key > k
- gpg --no-default-keyring --keyring ./temp-keyring.gpg --export --output k.gpg
+gpg --no-default-keyring --keyring ./temp-keyring.gpg --import k
- mkdir /etc/apt/keyrings
+gpg --no-default-keyring --keyring ./temp-keyring.gpg --export --output k.gpg
- mv k.gpg /etc/apt/keyrings/satnogs2.gpg
+mkdir /etc/apt/keyrings
- vi /etc/apt/sources.list.d/satnogs.list
+mv k.gpg /etc/apt/keyrings/satnogs2.gpg
- insert a signed-by statement, as:
+vi /etc/apt/sources.list.d/satnogs.list
- deb [signed-by=/etc/apt/keyrings/satnogs2.gpg] /repositories/home:/librespace:/satnogs/Raspbian_11 - openSUSE Download ./</code>
+</pre>
 More info available at https://community.libre.space/t/sudo-apt-update-signature-invalid/7643/7 and https://community.libre.space/t/update-to-the-invalid-signature-problem-in-the-troubleshooting-document/11386

@@ Line 72: / Line 72: @@
     <code>The following signatures were invalid: EXPKEYSIG 8BD3901736A40B6C home:librespace OBS Project <home:[[Mailto:librespace@build.opensuse.org|librespace@build.opensuse.org]]></code>
 Fix:
-<code>wget -qO - <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki> | sudo apt-key --keyring /etc/apt/trusted.gpg add -</code>
+More info available at https://community.libre.space/t/sudo-apt-update-signature-invalid/7643/7 and https://community.libre.space/t/update-to-the-invalid-signature-problem-in-the-troubleshooting-document/11386
 ===apt-get update: connection failed===

← Older revision	Revision as of 08:32, 21 March 2025
(No difference)

@@ Line 1: / Line 1: @@
 ==Client troubleshooting==
-{{Message|If the hints for common issues below don't help solve your issue, you are welcome to post in the forum.  When doing so, please include the output of the support report generated by the menu item <code>Advanced -> Support</code> from <code>sudo satnogs-setup</code>.  This helps give context to the logging messages.}}
 ===Raise or Set the debug level===
@@ Line 37: / Line 45: @@
 *Check your SATNOGS_NETWORK_API_URL.  It should point to https://network.satnogs.org/api/ (prod) or https://network-dev.satnogs.org/api/ (dev).
 *Check your network connectivity.  Can you ping network.satnogs.org or network-dev.satnogs.org?  Try running <code>curl https://network.satnogs.org</code> or <code>curl https://network-dev.satnogs.org</code>.
 ===RuntimeError: RTL-SDR device not found.===

@@ Line 4: / Line 4: @@
 ===Raise or Set the debug level===
-*Run <code>sudo satnogs-setup</code>;
+*Run <code>sudo satnogs-setup</code>
-*Go to '''Advanced Configuration''' and  set the '''Debug level''' (see below)
+*Go to '''Advanced Configuration''' and  set the '''Debug level''' to one of the Values below
 *'''Apply''' the change
 {| class="wikitable"
 !'''Setting'''
-!Value
+!Values
 |-
 |'''DEBUG'''
@@ Line 16: / Line 16: @@
 {| class="wikitable"
 |<code>CRITICAL</code>
 |-
 |<code>ERROR</code>
 |-
 |<code>WARNING</code>
 |-
 |<code>INFO</code>
 |-
 |<code>DEBUG</code>
 |-
 |<code>NOTSET</code>
 |}
 |}

@@ Line 76: / Line 76: @@
 More info available at https://community.libre.space/t/sudo-apt-update-signature-invalid/7643/7
-=== apt-get update: connection failed ===
+===apt-get update: connection failed===
 When using the sudo apt-get update command, we get the following connection error:
 [[File:UpdateFailed.png]]
 However, a ping to the Ip address works.