ctd

After a redeployment

• Update ctd_config.csv
• Then power cycle the device.
• The ctd commands are sent to the device after a power cycle (if enabled in previously linked ctd_config.csv file).

Data problems...

• Is data appearing on the windows app? It means the device is working
• If the python receiver cannot be reached...
  • gconode01 might not be running?
  • is the ctd collector showing ok in supervisord?
  • there might be a problem with supervisord on gconode01?
  • there could be another problem on gconode01
  • There may be a network problem?
• If no data in the python receiver
  • is it connecting to the correct moxa switch and port (configured in the ctd_config.csv file)
  • use telnet or similar to verify connection to ctd on gconode01
• If python receiver seems ok, but no data on mqtt.marine.ie ...
  • perhaps it is not a ctd specific problem?
  • could be a problem with the kafka cluster?
  • could be a problem with mirrormaker on kafka02
  • could be a problem with the small kafka (in docker) node on gconode01?
  • could be a full disk or some other problem on gconode01
• if python receiver seems ok, but no data in erddap
  • if the data is showing in mqtt.marine.ie then it's not a problem with kafka.
  • could be a problem with cassandra
  • could be a problem in node-red