Troubleshooting

Device Errors

Device is not showing up in Cluster/Talaria

• Problem: Parados (the application of the device that connects to Talaria) has the incorrect url.

  • Solution: Validate Parados has the correct url.

  docker run -e URL=http://HOSTNAME:PRIMARY_PORT rdkb-simulator
  # HOSTNAME should be either a Talaria or Petasos address, with
  # the correct corresponding PRIMARY_PORT
  

• Problem: TLS is inconsistent between Talaria and Petasos.

  • Fixed Solution: Change Talaria and Petasos configurations to be consistent with http or https.

  # talaria  
  service:
    defaultScheme: http
    fixed:
      - http://TALARIA_HOSTNAME:PRIMARY_PORT
  # petasos
  service:
  defaultScheme: http
  fixed:
    - http://TALARIA_HOSTNAME:PRIMARY_PORT
  

  • Consul Solution: Change Talaria and Petasos Configuration to be consistent with http or https. https is default.

  # talaria  
  service:
    defaultScheme: http
    # ^ important
    consul:
      client:
        address: "CONSUL_ADDRESS:CONSUL_API_PORT"
        scheme: "http"
        waitTime: "30s"
      disableGenerateID: true
      vnodeCount: 211
      watches:
        -
          service: "talaria"
          tags:
            - "dev"
            - "docker"
          passingOnly: true
      registrations:
        -
          id: "HOSTNAME"
          name: "talaria"
          tags:
            - "dev"
            - "docker"
            - "stage=dev"
            - "flavor=docker"
          address: "http://HOSTNAME:PRIMARY_PORT"
          # ^ important
          scheme: "http"
          # ^ important
          port: 6210
          checks:
            -
              checkID: "talaria-1:http"
              http: "http://HOSTNAME:HEALTH_PORT/health"
              interval: "30s"
              deregisterCriticalServiceAfter: "70s"
  
  # petasos
  service:
  defaultScheme: http
  # ^ important
  consul:
    client:
      address: "consul0:8500"
      scheme: "http"
      waitTime: "30s"
    disableGenerateID: true
    watches:
      -
        service: "talaria"
        passingOnly: true
    vnodeCount: 211
  

• Problem: Talaria is not registering with Consul.

  • Detection: On a consul node, run the following command(s):

  consul catalog services
  # Talaria should show up in list, if not try the solution
  

  • Solution: Validate Consul client block in Talaria config, with TLS and address.

  consul:
    client:
      address: "CONSUL_ADDRESS:CONSUL_API_PORT"
      # ^ important
      scheme: "http"
      # ^ important
      waitTime: "30s"
  

Event Errors

• Problem: Caduceus is not receiving events.

  • Solution: Update the Talaria yaml with the correct information.

  eventMap:
      default: http://CADUCEUS_HOSTNAME:PRIMARY_PORT/api/v3/notify
        # double check http vs https and the hostname
  

General Errors

• Problem: Docker networking with localhost.
  • Solution: Use the ip address of the host machine. You can not use localhost when working with docker.

This documentation is open-source. Please help improve it by filing issues or pull requests.