I’ve got the rotator talking nicely to gpredict and am moving onto the client setup. I followed the instructions and installed on my RPi2
- Configured the /etc/supervisor/conf.d/rotctld.conf (note the d in supervisor directoy is removed) with…
[program:rotctld] command=/usr/bin/rotctld -m 202 -r /dev/ttyACM0 -s 19200 -T 127.0.0.1 autostart=true autorestart=true user=pi priority=1
- Configured the
/etc/supervisor/conf.d/satnogs.conf
(same thing with the d on supervisor directory
[program:satnogs] command=/usr/local/bin/satnogs-poller directory=/home/pi/ autostart=true autorestart=true user=pi environment=SATNOGS_SQLITE_URL="sqlite:////tmp/jobs.sqlite",SATNOGS_API_URL="https://network-dev.satnogs.org/api/",SATNOGS_API_TOKEN="token removed",SATNOGS_VERIFY_SSL="TRUE",SATNOGS_STATION_ID="46",SATNOGS_STATION_LAT="54.6422",SATNOGS_STATION_LON="-3.5375",SATNOGS_STATION_ELEV="37",SATNOGS_PPM_ERROR="0"
…note PPM error is not set as I can’t get Kal to find a GSM station…
- Restarted supervisor using
sudo supervisorctl reload
and notice that there was not green light on the dev-network and get this error in thevar/log/supervisor/supervisor.log file
2016-04-20 17:34:33,729 CRIT Supervisor running as root (no user in config file) 2016-04-20 17:34:33,730 WARN Included extra file "/etc/supervisor/conf.d/satnogs.conf" during parsing 2016-04-20 17:34:33,730 WARN Included extra file "/etc/supervisor/conf.d/rotctld.conf" during parsing 2016-04-20 17:34:33,737 INFO RPC interface 'supervisor' initialized 2016-04-20 17:34:33,738 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2016-04-20 17:34:33,739 INFO supervisord started with pid 510 2016-04-20 17:34:34,745 INFO spawned: 'rotctld' with pid 7945 2016-04-20 17:34:34,753 INFO spawned: 'satnogs' with pid 7946 2016-04-20 17:34:35,504 INFO exited: satnogs (exit status 1; not expected) 2016-04-20 17:34:36,506 INFO success: rotctld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-04-20 17:34:36,511 INFO spawned: 'satnogs' with pid 7987 2016-04-20 17:34:37,311 INFO exited: satnogs (exit status 1; not expected) 2016-04-20 17:34:39,321 INFO spawned: 'satnogs' with pid 7991 2016-04-20 17:34:40,138 INFO exited: satnogs (exit status 1; not expected) 2016-04-20 17:34:43,148 INFO spawned: 'satnogs' with pid 8037 2016-04-20 17:34:43,990 INFO exited: satnogs (exit status 1; not expected) 2016-04-20 17:34:44,992 INFO gave up: satnogs entered FATAL state, too many start retries too quickly
I’m more of a mechanical chap and this looks a bit fatal for some reason. Any suggestions / comments?
73
Alex, g7kse