Development Environment Tutorial not working

Boundary
1

Hi,

I followed this tutorial and it’s not working. I’m getting these errors:

.
.
.
==> Boundary server started! Log data will stream in below:

{
  "id": "Si3y4WC7AM",
  "source": "https://hashicorp.com/boundary/dev-controller/boundary-dev",
  "specversion": "1.0",
  "type": "error",
  "data": {
    "error": "db.LookupWhere: record not found, search issue: error #1100: dbw.LookupWhere: record not found",
    "error_fields": {
      "Code": 1100,
      "Msg": "",
      "Op": "db.LookupWhere",
      "Wrapped": {}
    },
    "id": "e_MJ36F5lzQy",
    "version": "v0.1",
    "op": "db.LookupWhere"
  },
  "datacontentype": "text/plain",
  "time": "2022-04-07T15:17:30.703605648+02:00"
}
{
  "id": "MAU4CKuiCm",
  "source": "https://hashicorp.com/boundary/dev-controller/boundary-dev",
  "specversion": "1.0",
  "type": "error",
  "data": {
    "error": "db.LookupWhere: record not found, search issue: error #1100: dbw.LookupWhere: record not found",
    "error_fields": {
      "Code": 1100,
      "Msg": "",
      "Op": "db.LookupWhere",
      "Wrapped": {}
    },
    "id": "e_RUs4NdNMo3",
    "version": "v0.1",
    "op": "db.LookupWhere"
  },
  "datacontentype": "text/plain",
  "time": "2022-04-07T15:17:30.959560606+02:00"
}
{
  "id": "WBoNqZ5X4b",
  "source": "https://hashicorp.com/boundary/dev-controller/boundary-dev",
  "specversion": "1.0",
  "type": "system",
  "data": {
    "version": "v0.1",
    "op": "worker.(Worker).createClientConn",
    "data": {
      "address": "127.0.0.1:9201",
      "msg": "connected to controller"
    }
  },
  "datacontentype": "text/plain",
  "time": "2022-04-07T15:17:30.992418308+02:00"
}
{
  "id": "ctGHsfqbGV",
  "source": "https://hashicorp.com/boundary/dev-controller/boundary-dev",
  "specversion": "1.0",
  "type": "system",
  "data": {
    "version": "v0.1",
    "op": "controller.(interceptingListener).Accept",
    "data": {
      "msg": "worker successfully authed",
      "name": "dev-worker"
    }
  },
  "datacontentype": "text/plain",
  "time": "2022-04-07T15:17:31.009622804+02:00"
}

$ uname -a
Linux 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ docker version
Client: Docker Engine - Community
 Version:           20.10.12
 API version:       1.40
 Go version:        go1.16.12
 Git commit:        e91ed57
 Built:             Mon Dec 13 11:45:27 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:01:06 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

I’ve also tried different versions of postgres like this:

boundary dev -container-image="postgres:XYZ"

Any ideas?

Thanks

2

Hello @polcikj

Welcome and thank you for trying Boundary! As it happens there is a pull request to fix those erroneous logs currently open, this should be resolved in the next release of Boundary later this month.

Please note that you can continue using Boundary as those lookups are retried.

Let me know if you have any issues

3

Sorry, I don’t understand what you mean by this:

Please note that you can continue using Boundary as those lookups are retried.

Could you explain this in more detail, please?

Thank you

4

The error you are getting db.LookupWhere: record not found, search issue: error #1100: dbw.LookupWhere: record not found occurs at startup when Boundary is performing a lookup, when first trying the lookup it fails because it does not exist, but it retries the lookup again and that succeeds. Even though the error is logged you can ignore it and continue using Boundary.

2 Likes
5

Oh sorry. Now I understand. Before I wrote this post I did try to run localhost:9200 despite the errors but it was not working - I don’t know why and unfortunately I will not find out it anymore.

Now it’s working dispite the errors as you wrote me, so I guess I created a useless post for this :slight_smile: At least we know that it will be fixed later this month :slight_smile: Sorry again and thanks.

6

Not useless at all – I guarantee you somebody else will see your post and the replies and that’ll answer their question quickly :slight_smile:

1 Like