Nope - can’t get it to work, but I’m sure I don’t know how to change my cron job to include that line… here is my cron job, what do I change to implement that environment?
Dec 18 17:09:42 satnogs1 systemd[359]: satnogs-client.service: Failed to execute command: No such file or directory
Dec 18 17:09:42 satnogs1 systemd[359]: satnogs-client.service: Failed at step EXEC spawning /var/lib/satnogs/bin/satnogs-client: No such file or directory
Dec 18 17:09:42 satnogs1 systemd[1]: satnogs-client.service: Main process exited, code=exited, status=203/EXEC
Dec 18 17:09:42 satnogs1 systemd[1]: satnogs-client.service: Failed with result 'exit-code'.
Dec 18 17:09:42 satnogs1 systemd[1]: satnogs-client.service: Service RestartSec=100ms expired, scheduling restart.
Dec 18 17:09:42 satnogs1 systemd[1]: satnogs-client.service: Scheduled restart job, restart counter is at 5.
Dec 18 17:09:42 satnogs1 systemd[1]: Stopped SatNOGS client.
Dec 18 17:09:42 satnogs1 systemd[1]: satnogs-client.service: Start request repeated too quickly.
Dec 18 17:09:42 satnogs1 systemd[1]: satnogs-client.service: Failed with result 'exit-code'.
Dec 18 17:09:42 satnogs1 systemd[1]: Failed to start SatNOGS client.
By calling the interpreter in the virtualenv and providing the script as command line argument you can execute the script in the virtualenv within a non-interactive session like cron.
To update SatNOGS software, including the configuration tool itself:
SSH into the system and (re-)run sudo satnogs-setup ; this will bring up the configuration menu
Select Upgrade to upgrade all distribution packages to the latest; this may require a reboot. If this option is not available, running an Update will make it show up
Select Update to update the configuration tool
Select Apply and the Raspberry Pi will update itself; this may take some time
Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
This didn’t work at all, but if I add /home/pi before the first part, I get this:
2019-12-19 21:51:15,294 - root - INFO - Requesting information for ground station 272
2019-12-19 21:51:16,962 - root - INFO - Ground station information retrieved!
2019-12-19 21:51:16,965 - root - INFO - Updating transmitters and TLEs for station
2019-12-19 21:51:16,967 - root - INFO - Fetching transmitter information from DB.
2019-12-19 21:51:21,043 - root - INFO - Transmitters received!
2019-12-19 21:51:21,110 - root - INFO - Transmitters filtered based on ground station capability.
2019-12-19 21:51:21,112 - root - INFO - Fetching transmitter information from DB.
2019-12-19 21:51:29,119 - root - INFO - Transmitters received!
2019-12-19 21:51:29,185 - root - INFO - Transmitters filtered based on ground station capability.
2019-12-19 21:51:29,187 - root - INFO - Fetching satellite information from DB.
2019-12-19 21:51:30,337 - root - INFO - Satellites received!
2019-12-19 21:51:30,355 - root - INFO - Requesting transmitter success rates.
2019-12-19 21:52:08,321 - root - INFO - Transmitter success rates received!
2019-12-19 21:52:08,323 - root - INFO - Fetch from http://mstl.atl.calpoly.edu/~ops/keps/kepler.txt
2019-12-19 21:52:08,768 - root - INFO - Fetch from https://www.amsat.org/amsat/ftp/keps/current/nasabare.txt
Traceback (most recent call last):
File "/home/pi/autosked/gitclone/satnogs-auto-scheduler/schedule_single_station.py", line 395, in <module>
main()
File "/home/pi/autosked/gitclone/satnogs-auto-scheduler/schedule_single_station.py", line 246, in main
tles = fetch_tles(norad_cat_ids)
File "/home/pi/autosked/gitclone/satnogs-auto-scheduler/scheduler_env/lib/python3.7/site-packages/satellite_tle/fetch_tles.py", line 53, in fetch_tles
new_tles = fetch_tles_from_url(url=url, verify=verify)
File "/home/pi/autosked/gitclone/satnogs-auto-scheduler/scheduler_env/lib/python3.7/site-packages/satellite_tle/fetch_tle.py", line 88, in fetch_tles_from_url
if (lines[i + 1][0] == "1") & (lines[i + 2][0] == "2"):
IndexError: string index out of range
I tried this: pip install --upgrade satellitetle , but it didn’t seem to change the results.
I believe this has fixed my issues. I was able to manually run the command and the scheduling worked. The true test will be tonight at 00:00z, but generally I think I am back on track! Thank you everbody!
did the stub for rtlsdr also change? did two passes with a new and old long running client on pi. Since the update there is no reception anymore (did not change params).
According the logs the qrg did not lock and the campaign failed
pi@oe8rke-satnogs:~ $ journalctl -f -u satnogs-client.service
– Logs begin at Thu 2016-11-03 17:16:43 UTC. –
Dec 21 17:42:30 oe8rke-satnogs satnogs-client[374]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
Dec 21 18:23:54 oe8rke-satnogs satnogs-client[374]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: gr-osmosdr 0.1.4 (0.1.4) gnu radio 3.7.10
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: Using device #0 Realtek RTL2 838UHIDIR SN: 00000001
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: Using 32 buffers of size 163 84.
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: Found Rafael Micro R820T tun er
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: [R82XX] PLL not locked!
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: Exact sample rate is: 100000 0.026491 Hz
Dec 21 18:23:58 oe8rke-satnogs satnogs-client[374]: [R82XX] PLL not locked!
Any clue how to fix this or how to revert back? Target qrg was 437200000
