Error messages on agent.proxycfg

[jorgemarey]

Overview of the Issue

We are seeing some error messages on consul when deploying connect services with nomad. Are these logs normal?

Consul info for both Client and Server

consul v1.7.2

Log Fragments

Mar 26 11:13:30 wrkr-b78b7e82-3b consul: {"@level":"error","@message":"watch error","@module":"agent.proxycfg","@timestamp":"2020-03-26T11:13:30.090703Z","error":"invalid type for service checks response: cache.FetchResult, want: []structs.CheckType","id":"service-http-checks:_nomad-task-2d5ea1b0-dee8-df84-6869-31494a2e9941-group-test-test-10080"}
Mar 26 11:23:36 wrkr-b78b7e82-3b consul: {"@level":"error","@message":"watch error","@module":"agent.proxycfg","@timestamp":"2020-03-26T11:23:36.243619Z","error":"invalid type for service checks response: cache.FetchResult, want: []structs.CheckType","id":"service-http-checks:_nomad-task-c3f41e0f-a5d1-2fb9-3883-82be8f092377-group-test-test-10080"}
Mar 26 11:25:05 wrkr-b78b7e82-3b consul: {"@level":"error","@message":"watch error","@module":"agent.proxycfg","@timestamp":"2020-03-26T11:25:05.531741Z","error":"invalid type for service checks response: cache.FetchResult, want: []structs.CheckType","id":"service-http-checks:_nomad-task-708d62cf-e14c-1011-125b-65c04d48ce58-group-test-test-10080"}
Mar 26 11:53:11 wrkr-b78b7e82-3b consul: {"@level":"error","@message":"watch error","@module":"agent.proxycfg","@timestamp":"2020-03-26T11:53:11.846211Z","error":"invalid type for service checks response: cache.FetchResult, want: []structs.CheckType","id":"service-http-checks:_nomad-task-8c5caf4b-0a5a-d144-195d-04a7c029ea77-group-test-test-10080"}
Mar 26 12:24:37 wrkr-b78b7e82-3b consul: {"@level":"error","@message":"watch error","@module":"agent.proxycfg","@timestamp":"2020-03-26T12:24:37.160438Z","error":"invalid type for service checks response: cache.FetchResult, want: []structs.CheckType","id":"service-http-checks:_nomad-task-8d93ccd3-d883-e849-9d8e-64d9a8e1ad23-group-test-test-10080"}
Mar 26 12:34:46 wrkr-b78b7e82-3b consul: {"@level":"error","@message":"watch error","@module":"agent.proxycfg","@timestamp":"2020-03-26T12:34:46.001895Z","error":"invalid type for service checks response: cache.FetchResult, want: []structs.CheckType","id":"service-http-checks:_nomad-task-8a1a7924-672a-b994-ef02-9ebffaf2398e-group-test-test-10080"}

[jsosulska]

Hi @jorgemarey !

Thank you for opening an issue with us! I am putting the theme/consul-nomad label so that both teams can potentially take a look at this. We will update this thread with more information when we have it.

In the meantime, I have a few additional questions.

• Is this happening for all services, or a specific service?
• Can you please provide an example service config, with sensitive information removed?
• Can you specify what version of Nomad you are using?

Thank you for your time! Best, Jono

[dnephin]

This was fixed in cb050b280ceb4186de765118611a7a92d8158c3f. The cache-type was was ignoring an error, and the error returns were using a FetchResult as the result value instead of nil. This change has not yet been backported into 1.8.x, so I will do that now.