openBalena Internal Server Error on device registration with Python SDK

ca1ebd · November 10, 2020, 8:38pm

Hello!

I am hoping to use the Balena Python SDK to pre-register my devices so that I can set critical environment variables at the same time the SD card is flashed.

However, when my python script executes balena.models.device.register(<my_application_name>, <32_character_UUID>)

I receive an internal server error.

Here is my balena.cfg file (I am running openBalena 2, not 3 yet):

[Settings]
pine_endpoint = https://api.<my_domain>/v5/
api_endpoint = https://api.<my_domain>/
builder_url = https://builder.balena-cloud.com/
api_version = v5
device_actions_endpoint_version = v1
data_directory = C:\Users\Caleb\.balena
image_cache_time = 604800000
token_refresh_interval = 3600000
timeout = 30000
cache_directory = C:\Users\Caleb\.balena\cache
token = <my_token>

Any ideas?

codewithcheese · November 11, 2020, 6:06am

Hi Caleb, check out the logs for the API service and see if you can find the exception. That can help us diagnose.

ca1ebd · November 11, 2020, 6:02pm

The Python API? How?

thgreasi · November 11, 2020, 6:35pm

Hi Caleb,

We actually meant the logs printed by the open-balena-api container that’s running on your server.
Let me point you to the template part of the respective docker-compose service:

github.com

balena-io/open-balena/blob/3b9433e9ccb3fd829c74dd1a2f3de49cb61c35d4/compose/services.yml#L12



volumes:
  certs: {}
  cert-provider: {}
  db: {}
  redis: {}
  registry: {}
  s3: {}

services:
  api:
    extends:
      file: ./common.yml
      service: component
    image: balena/open-balena-api:${OPENBALENA_API_VERSION_TAG}
    depends_on:
      - db
      - s3
      - redis
    environment:
      API_VPN_SERVICE_API_KEY: ${OPENBALENA_API_VPN_SERVICE_API_KEY}

Once you get a terminal session to the open-balena server, you should be able to do a docker ps to grab the API container name and just use journalctl -f -n 100 -u <CONTAINER_NAME> to start seeing the emitted logs.

Kind regards,
Thodoris

ca1ebd · November 13, 2020, 10:22pm

I have attached my logs from the docker ps (docker-ps.log) and journalctl -f -n 100 -u openbalena_api_1 (journalctl-api.log). Since the journalctl didn’t show any logs, I also tried without the -u flag and have attached that output (journalctl.log)

Any ideas as to why the journalctl command you gave didn’t show anything? Do I need to log in as a particular user? I did make sure to test out the code which produces the error while the journalctl was running.

docker-ps.log (2.1 KB) journalctl-api.log (49 Bytes) journalctl.log (11.2 KB)

rahul-thakoor · November 16, 2020, 6:50am

Hey there it seems there were no logs from that service?

can you try to get the logs directly while trying to run the test code again using docker logs --follow <container ID>?

in your case that would docker logs --follow 291fa7767aac

Thanks