Andes Pre-mission Checklist for Administrators
Mission name: ______________________
Mission number: ______________________
Season: ______________________
| Step description | Verified? (Initials) |
|---|---|
| Sync up regional catch list with CARL. | |
| Application is deployed on a dedicated branch and make sure deployment script points to that branch. | |
| Run the deployment script. | |
Set the server environmental variable DEBUG to False. The debug setting is set via the project’s .env file, located in the andes root directory (e.g. /opt/andes_root/andes/.env) |
|
| All test data has been removed (i.e., mission has been deployed) - Settings > Danger Zone > Deploy a Mission | |
Are the fake nmea and fake scanmar shell scripts stopped? sudo systemctl \| grep fake |
|
Are the listener services running? sudo systemctl \| grep listener |
|
| Make sure NAV inputs are working on site - GPS button > Start Recording Navigational Data | |
| Receives lat/long | |
| Receives depth | |
| Receives meteorological data | |
| Make sure Scanmar / Net telemetry is working on site: GPS button > Start Recording Scanmar | |
| Make sure all sensor roles are properly configured: Settings > Managing Sensor Type Lookups; Delete any unused lookups | |
Make sure the date/time of server is correct (see Date/Time Console under Admin menu) |
|
| Make label printers are working on site (and bonus points for adding printers to CUPS manually!!) (extra bonus points if printers are on static IP) | |
With the NAS unmounted, make sure there are no stray files from previous missions in the Andes working directory:sudo umount /opt/andes_root/andes/_working/backupsudo rm -r /opt/andes_root/andes/_working/backup/* |
|
Make sure the NAS is mounted: sudo mount -a |
|
Is the andes working directory cleaned out from older missions? sudo rm -r /opt/andes_root/andes/_working/log/* /opt/andes_root/andes/_working/tmp/* |
|
Is the andes media directory cleaned out from previous missions? sudo rm -r /opt/andes_root/andes/media/* |
|
Deal with working-backup-database folder from previous mission. For example, sudo mv /opt/andes_root/andes/_working/backup/database /opt/andes_root/andes/_working/backup/old/..../database |
|
Deal with working-backup-images folder from previous mission. For example, sudo mv /opt/andes_root/andes/_working/backup/image /opt/andes_root/andes/_working/backup/old/..../image |
|
Make sure the backup works? Create a backup SQL file and then log onto the NAS to check if file is there: ssh admin_andes@192.168.0.101ll -h /volume1/andes_backup/database |
|
In the mission settings, ensure the location of the map server is correct: Cruise > Configuration > Time, Dates and Location. The address is usually http://192.168.0.101/maptile_collection. Need to be on the ship’s LAN to verify but you can curl in ssh: curl http://192.168.0.101/maptile_collection/400201/9/159/185.png |
|
| Check everything again after a reboot of the server: Settings > Run Shell Scripts > Reboot Andes Server | |
| Make sure you can run shell scripts from the front end (optional, but if you did the above from GUI, you are good!) | |
| Navigation system (e.g., Alderbarren / OpenCPN) setup (i.e., stations are “loaded up”) | |
| Reset the Specimen table autoincrement: Settings > Run Shell Scripts > MySQL specimen autoincrement reset | |
| If using webcams, test to see that they are working | |
| If applicable, start a fishing set and test out the fishing console | |
| The following steps relate to the use of a CradlePoint mobile router (see Cradlepoint notes) |
n/a |
| Firewall: WAN to LAN policy does not permit access from non-whitelisted IPs, e.g. a “Andes Remote Access” policy | |
| Appropriate restrictions are placed on WAN to LAN access, e.g. a “WAN access on vessel” policy exists | |
| DHCP reservations for server, nas, printers, moxas | |
| DNS entry for Andes server, nas, … |