ArgumentError raised when starting Bors

rokthewok · December 23, 2019, 6:19pm

I'm attempting to spin up a docker container running bors-ng. I supply the required environment variables, as outlined in the docs and in the guide, Setting up bors with docker-compose. However, after the log line "running migrations for bors", I encounter the following error, and the service crashes.

The stack trace is as follows:

web_1  | Running migrations for bors
web_1  | 23:50:22.825 [error] GenServer BorsNG.GitHub terminating
web_1  | ** (ArgumentError) argument error: [[], {:jose_jws, {:jose_jws_alg_rsa_pkcs1_v1_5, :RS256}, :undefined, %{"typ" => "JWT"}}, %{"aud" => "Joken", "exp" => <redacted>, "iat" => <redacted>, "iss" => <redacted>, "jti" => "<redacted>", "nbf" => <redacted>}]
web_1  |     (jose) src/jose_jwt.erl:184: :jose_jwt.sign/3
web_1  |     (joken) lib/joken/signer.ex:119: Joken.Signer.sign/2
web_1  |     (joken) lib/joken.ex:365: Joken.encode_and_sign/3
web_1  |     (joken) lib/joken.ex:211: Joken.generate_and_sign/4
web_1  |     (joken) lib/joken.ex:225: Joken.generate_and_sign!/4
web_1  |     (bors) lib/github/github/server.ex:62: BorsNG.GitHub.Server.handle_call/3
web_1  |     (stdlib) gen_server.erl:661: :gen_server.try_handle_call/4
web_1  |     (stdlib) gen_server.erl:690: :gen_server.handle_msg/6
web_1  | Last message (from BorsNG.Supervisor): :get_app
web_1  | 23:50:22.830 [info] Application bors exited: BorsNG.Application.start(:normal, []) returned an error: shutdown: failed to start child: BorsNG.Attrs
web_1  |     ** (EXIT) exited in: GenServer.call(BorsNG.GitHub, :get_app, 10000)

Has anyone else encountered this before? Unfortunately I'm not familiar with Elixir/Phoenix/Erlang, so debugging has proven difficult.

rokthewok · December 31, 2019, 5:50pm

I still haven't been able to resolve this issue. I did find this github issue, in which the user did not have their pem input correctly formatted within an Elixir string. I'm not sure how I can see if this is the issue; I base64-encode my pem with

openssl base64 -A -e < secret.pem

And decoding it gives me the correct result.

notriddle · January 1, 2020, 8:02pm

Okay, can you ask GitHub to regenerate your PEM key, then post an exact copy of your docker-compose.yml file?

rokthewok · January 1, 2020, 9:25pm

Certainly, thanks for the reply. Here's the docker-compose.yml file (PEM and client secret have been since regenerated and my public ec2 DNS fudged):

version: "2"
services:
  web:
    image: borsng/bors-ng
    restart: always
    ports:
      - 80:8000
    environment:
      PORT: 4000
      PUBLIC_HOST: "ec2-3-15-96-420.us-east-1.compute.amazonaws.com"
      DATABASE_URL: "postgres://postgres:testing1@postgres:5432/bors_ng"
      GITHUB_CLIENT_ID: "Iv1.896d6f4781cfdfa7"
      GITHUB_CLIENT_SECRET: "5fb8a1969375132a30be4fed1a5d243d0a7a5031"
      GITHUB_INTEGRATION_ID: 49067
      GITHUB_INTEGRATION_PEM: "LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLSBNSUlFcEFJQkFBS0NBUUVBMEVaeFZQRjRMcVRsVDZGT1d1c2hlSERZTmNUNGh0c1BvSUZ1Rm00SnBsclNrdmVuIDdxZGo1SHFWTWNxQkNXbHAvZEhQL1JvTXp4aTFlNUZ5UmpXUzU5Vlp5UXlxeWZ3amc0R2M0ZVhWVk5rZDNUMFIgTE1BZWVFaGFJUzJQMVVrazhwZXZ4Y2xVIGRiRWtDL0JvQ1F6enVrUzlvWGJoVWl4VWZvK1A2NU1JVm8wNlJkZFggNnNVWXdtVGNkQnl6MVVYMXJlcWR2R01EdFNhcS9tWllWbmlKSEc0eUQrbUhsWnZxM0xRbWVHRkpxcmFCRGt0SCBWZjlDTUtoZGtpd0x0SmUvSHRKQmVOeHB0V1AvMmc0U2cxOTh3RDJ3STRIYUFseThSS1ppS3h4RC9Hdmk2ODU3IC9meVdnVlRCak5Kelc2TGVWSWpSUVRKMmo4bnFIWEFNOVR4d3IgUUlEQVFBQkFvSUJBUUNRU0l5UWxPdDJITVBEIEEzTTlwdkE3K0tpL3J5R2dncmR6c05acjhYVDc2cVZBTFJNSVVLdnlCejIrRFpTUXlaY2t3Q24vSkFIRm9rOXYgT0JaYkx4Z0RSUmo3SDZ4ZFd5L2JGWHB5UC84bTFYWkw0dGM0RWl2SmxnM2lPQ2NSVWFlbjY0OVlUSjRYSGsxaiBlL3NHY2hPU2NiYVEyY05FWXZOeDdkQjlHUkhJcXJNWUtqL1pObU1KaEEyLzg5K0hrayBRb2g1dU5lR1UvUDhBQyBQWmtNbjFpQ0xLbVJGY1hLNHBiYmJjUnNBaWdRWkRpL1dqZEJRUlBDVEZNVHo3aGd3NTJjSlFLUTFkZFgvL2swIDJHOG5VZG1FWC9oanBQUVkvbHZWQUFWQng2c2hGdlFnU1FJL1ptUzRaVVpRbU1mQnFmMTZhVWhSOTlrdHBtZGogUXFJQjB5NWRBb0dCQVBhczc3WkdmdHdPWFNLNWYyNHFIUUU4ZUhzOXM5eU1OU3VKU2g4MThnRDZpYWk2UXFjWiB3bmY3YUZVQ3ZoVzYxaW9Ub3ppWTFXL3NNa0kzOHMzY2lqdnI5MmRDeVBGUWtSc3AwaXNVYnV4Zk1FUGpSRlIxICsxbTlSRTM3MkI2MTMxMWZhT0pEekdhM2c1NDQrTGFSbFVBUjdZd3ZvY3V4c0Q0MDlZeE1hbmpYQW9HQkFOZ2wgNkl6cFZGbG5qQkFjNk1iSG02cytVbE9pbTdmWmVPdHhjb1ZjT2FqUG43dzJwaERNTDhjZkRBdkdqMThSeld2YyBoaFpEakJqZ3hudkxoYUNRQk9manBUZ2hHL3BkamNZUGNjcmtWaEpkanpLUjNuZUdmYmhVZlZRMmFTaDlzRkNHIDVJNmlQNkxJdE1iNmhGbDVMZmpRZy8xR3FGbFRDV3UxVzhVOVc1NGJBb0dBRE1aVCs3cVc0MHFUSkRNN0dEZHkgSFJoR25RdEsvMGI3a2UrZ09SR1FJT0RZdERaQk1Xb3lHZ2laRkozNXZpSlk2UUR2V1FVQk9MU2d2YkVzRCtFMSAvM2h1N1pnVjAvbDZLay8ySkdrQWZabElaSnVtZEVGUDdRdlNONyt0SjVuL29WUkptRDR1bmJzdlE4aHJpUGp0IEk4NUo0Ukt1YkdBZFludFhwQlpwQlMwQ2dZRUF5MjQ2UmMwZzd4aE9zYWVUeWVwNTc1eXpQVFh3MndNYUZIWHMgcytsTjl6eVorVGx4NktOVVlGTXZNaklLSkE4TVNIVC8yaHB1MDhkUjU1ZHdSK0xrU3g5dEU3dk5xa0M4dTJreiB6eUpDZy94OFZyc0ZKM2QwQWJXN1V6UDJtdjVZb0NHbElUMUJLVU0vS1hzRWIzVm11Q1AvNWJQSHBISkxqb3pkIE4zRDlObnNDZ1lCSzZVNWJLNm1MZUxXRVM5VDJsZ25tYnM3dVJkd0t3eXpZM0FhdjFCSHlPUUZxZGJpcE1QcWkgaCtDanFuQnovL1lwSUVJbmdLY2ZuK3pGckc5V3JsQml6ZVUvbm1Bd2xMdWhIVWJqVzBOb1hHdDZGcVo2UXZXVSBFa1A3YTZOWlphSFdteHM0Uk0zVm1qamFpZ21RSlFnME1RYm9ybWxINGg1YUVXaVRPVDNLK1E9PSAtLS0tLUVORCBSU0EgUFJJVkFURSBLRVktLS0tLQo="
      GITHUB_WEBHOOK_SECRET: "YzUzYzY1YTY2MmFiMTdjNzliNTFlZDBh"
      DATABASE_USE_SSL: "false"
      DATABASE_AUTO_MIGRATE: "true"
      ALLOW_PRIVATE_REPOS: "true"
      SECRET_KEY_BASE: 46290
  postgres:
    image: postgres:11.6
    restart: always
    volumes:
      - datadb:/var/lib/postgresql/data
    environment:
      POSTGRES_PASSWORD: testing1
volumes:
  datadb:
networks:
  default:
    driver: bridge

notriddle · January 2, 2020, 6:13pm

Found the problem. All of the line breaks in your pemfile have been replaced with spaces. That is, it looks like this when I base64 decode it:

When it ought to look more like this:

The lines breaks here are part of the format.

rokthewok · January 2, 2020, 7:02pm

That indeed was the issue! Thanks so much for the help. I was unaware that private keys required those newlines.