Hello to all,
I hope you are all well
At times I have input/output errors and this has generated ERROR - No waterfall data file found. And all observations failed.
I definitely want to fix it. If anyone has the same problem, it will be helpful to share how to fix it.
Worse, I can’t reboot my computer remotely.
Cheers,
cceres_team.
Could you copy paste the errors you see? Are you on the latest version?
Hi Fredy,
I lost my journalctl message. It not set to storage.
Alternatively want I run sudo journalctl -p err I have this an output.
août 02 09:23:22 cceres_team kernel: ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
août 02 09:23:22 cceres_team kernel: ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
août 02 09:23:22 cceres_team kernel: ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
août 02 09:23:22 cceres_team kernel: ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
août 02 09:23:28 cceres_team avahi-daemon[665]: chroot.c: open() failed: No such file or directory
août 02 09:23:40 cceres_team minissdpd[997]: ioctl(s, SIOCGIFADDR, …): Cannot assign requested address
août 02 09:38:41 cceres_team kernel: i2c i2c-5: sendbytes: NAK bailout.
août 02 10:42:53 cceres_team cinnamon-screensaver-pam-helper[10966]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 10:42:53 cceres_team cinnamon-screensaver-pam-helper[10966]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 10:49:25 cceres_team cinnamon-screensaver-pam-helper[11547]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 10:49:25cceres_team cinnamon-screensaver-pam-helper[11547]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 10:49:58 cceres_team cinnamon-screensaver-pam-helper[11597]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 10:49:58 cceres_team cinnamon-screensaver-pam-helper[11597]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 10:53:49 cceres_team cinnamon-screensaver-pam-helper[11906]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 10:53:49cceres_team cinnamon-screensaver-pam-helper[11906]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 13:40:36 cceres_team cinnamon-screensaver-pam-helper[25521]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 13:40:36 cceres_team cinnamon-screensaver-pam-helper[25521]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 14:12:34 cceres_team cinnamon-screensaver-pam-helper[28093]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 14:12:34 cceres_team cinnamon-screensaver-pam-helper[28093]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 14:13:47 cceres_team cinnamon-screensaver-pam-helper[28218]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 14:13:47 cceres_team cinnamon-screensaver-pam-helper[28218]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 14:14:51 cceres_team cinnamon-screensaver-pam-helper[28301]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 14:14:51 cceres_team cinnamon-screensaver-pam-helper[28301]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 14:17:39 cceres_team cinnamon-screensaver-pam-helper[28547]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 14:17:39 cceres_team cinnamon-screensaver-pam-helper[28547]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 14:47:57 cceres_team cinnamon-screensaver-pam-helper[31049]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 14:47:57 cceres_team cinnamon-screensaver-pam-helper[31049]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 14:52:48 cceres_team cinnamon-screensaver-pam-helper[31437]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 14:52:48 cceres_team cinnamon-screensaver-pam-helper[31437]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:14:12 cceres_team cinnamon-screensaver-pam-helper[787]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:14:12 cceres_team cinnamon-screensaver-pam-helper[787]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:27:02 cceres_team cinnamon-screensaver-pam-helper[2184]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:27:02 cceres_team cinnamon-screensaver-pam-helper[2184]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:29:40 cceres_team cinnamon-screensaver-pam-helper[2410]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:29:40 cceres_team cinnamon-screensaver-pam-helper[2410]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:32:02 cceres_team cinnamon-screensaver-pam-helper[2604]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:32:02 cceres_team cinnamon-screensaver-pam-helper[2604]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:48:51 cceres_team cinnamon-screensaver-pam-helper[3987]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:48:51 cceres_team cinnamon-screensaver-pam-helper[3987]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:56:30 cceres_team cinnamon-screensaver-pam-helper[4599]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:56:30 cceres_team cinnamon-screensaver-pam-helper[4599]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
août 02 15:57:31 cceres_team cinnamon-screensaver-pam-helper[4701]: pam_unix(cinnamon-screensaver:auth): conversation failed
août 02 15:57:31 cceres_team cinnamon-screensaver-pam-helper[4701]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [user]
I am wondering about this also!
cheers,
cceres_team
Hi ccreres_team,
Those errors seem to indicate your BIOS and/or kernel may need an update to properly identify the (video?) card. If your system isn’t crashing , you can probably just ignore those messages.
You could also narrow down the journalctl query by using
journalctl -f -u satnogs-client.service
What OS distro and version are you running???
Please pass along the output of satnogs-setup ->advanced ->support as well.
Here is my :
versions": {
“satnogs-client”: “1.5.1”,
“satnogs-client-ansible”: “202105301943”,
“satnogs-flowgraphs”: “1.3.1-1”,
“gr-satnogs”: “2.2.1.0-1”,
“gr-soapy”: “2.1.3.1-1”,
“gnuradio”: “3.8.2.0-14satnogs2”,
“satnogs-config”: “0.12”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2021-08-03T12:25:31.009597+00:00”,
“distribution”: {
“DESCRIPTION”: “Debian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Debian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “cceres_team”,
“release”: “4.19.0-17-amd64”,
“version”: “#1 SMP Debian 4.19.194-3 (2021-07-18)”,
“machine”: “x86_64”,
“processor”: “”
},
“memory”: {
“total”: 16498630656,
“available”: 12748361728,
“percent”: 22.7,
“used”: 3089199104,
“free”: 11634016256,
“active”: 3692126208,
“inactive”: 833572864,
“buffers”: 158924800,
“cached”: 1616490496,
“shared”: 349310976,
“slab”: 205832192
},
“disk”: {
“total”: 231216836608,
“used”: 24934731776,
“free”: 194465546240,
“percent”: 11.4
}
},
“configuration”: {
“gpsd_enabled”: true,
“hamlib_utils_rot_enabled”: true,
“hamlib_utils_rot_opts”: “-m 603 -r /dev/ttyS1 -s 9600 -T localhost -t 4533 -vvvvv”,
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_artifacts_api_token”: “******************************************************”,
“satnogs_gain_mode”: “Settings Field”,
“satnogs_log_level”: “INFO”,
“satnogs_other_settings”: “LNA=12,MIX=8,VGA=11”,
“satnogs_rot_baud”: “9600”,
“satnogs_rot_model”: “ROT_MODEL_NETROTCTL”,
“satnogs_rot_port”: “localhost:4533”,
“satnogs_rx_bandwidth”: “9.0e6”,
“satnogs_rx_samp_rate”: “2.5e6”,
“satnogs_soapy_rx_device”: “driver=airspy”,
“satnogs_station_elev”: “120”,
“satnogs_station_id”: “1062”,
“satnogs_station_lat”: “48.807”,
“satnogs_station_lon”: “2.229”,
“sentry_enabled”: true,
“udp_dump_host”: “localhost”
}
}
journalctl -f -u satnogs-client.service: give me currently journal or I need journal since 2021/08/01.
What do you mean by If your system isn’t crashing?
I’m using a lest kernel version…
cheers,
cceres_team.
“satnogs_log_level”: “INFO”,
Change the satnogs_log_level to DEBUG and then Apply. Then post the DEBUG log for the time that an observation fails with the sections just before and after the
ERROR-No waterfall data file found
message. It’s probably a radio setting that’s causing the the observation/waterfall error. I’m not familiar with airspy SDRs to offer particulars but if I were to guess, I’d start with eliminating this setting for now to see if that clears up the error:
“satnogs_gain_mode”: “Settings Field”,
This does not look right “Settings Field” , at least this variable isn’t defined in my setup (using a RTL-SDR v3 blog)
“satnogs_other_settings”: “LNA=12,MIX=8,VGA=11”,
“satnogs_rx_bandwidth”: “9.0e6”,
Might want to unset these as well for now, then try an observation or two.
re: latest kernel
Since you have the latest kernel, you can probably just ignore those error messages if you have the latest kernel and your system doesn’t crash/hang. Maybe you have a late model GFX board that Debian buster hasn’t incorporated into their kernel source yet or your motherboard BIOS needs updating (or both) … don’t know.
Hi,
Thanks for these advice.
I thanks I make some test about satnogs_gain_mode (Overall or Settings Field) and Any trouble.
But I re-do this.
And the Satnogs_rx_bandwidth is the typical bandwidth of airspy r2. Do you thanks that this parameters was automatically set by stanogs-client and the gr-satnogs?
Must be - I have no experience with airspy hardware . I’ve run into the ‘waterfall data not found’ during multiple tests over the last year and it was always related to a bad setting (or typo), usually regarding the radio side of things. One time it was a custom path I had define besides the default /tmp/.satnogs/
The DEBUG logs have always been the source of identifying the issue.
Ok.
I got some fail observation but I thinks but I don’t have any error unless
the typicall error that I got for every observation
cceres_team modesmixer2[694]: 2021-08-04 09:57:24.214 INFO inConnectId(127.0.0.1:30005:ADSB) connecting 127.0.0.1:30005 août 04 09:57:24
cceres_team modesmixer2[694]: 2021-08-04 09:57:24.214 ERROR inConnectId(127.0.0.1:30005:ADSB) connect host 127.0.0.1:30005 e
août 04 09:57:24 cceres_team modesmixer2[694]: 2021-08-04 09:57:24.214 INFO inConnectId(127.0.0.1:30005:ADSB) reconnect in 590 seconds
lines 1823-1855/1855 (END)
But after making change like you advice, I didn’t get observation that have data and all observation have Waterfall EMPTY.
Cheers,
cceres_team.
Hi,
I also have the same problem. My station regularly crashes with my SDRPlay.
I noticed that when I don’t have a waterfall, when I run the instruction “SoapySDRUtil --probe = sdrplay” I get an error message.
So I think it’s a driver crash. For the moment, the only solution I have found is to restart the raspberry every day.
Sorry for my English “Google”
Manu F4HSE