Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

golang rpc exception #4

Closed
TomShacham opened this issue Sep 15, 2016 · 4 comments
Closed

golang rpc exception #4

TomShacham opened this issue Sep 15, 2016 · 4 comments

Comments

@TomShacham
Copy link

tom$ cf enable-diego some-app
Setting some-app Diego support to true
2016/09/15 14:54:54 rpc: gob error encoding body: gob: type not registered for interface: []interface {}
FAILED
Error:  reading body EOF

While I can enable diego for every other app in my CF and Diego deployments, this one app gets this exception.

Thanks!

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/130448655

The labels on this github issue will be updated when the story is started.

@dkoper
Copy link
Contributor

dkoper commented Sep 16, 2016

Hi @TomShacham

Can you enable cf CLI trace and attach the output here if there is any?
Also, can you provide more details about your environment? Platform, cf CLI version, Diego-Enabler plugin version, CF release version (see output cf api), etc.

Cheers,
Dies Koper
CF CLI PM

@TomShacham
Copy link
Author

TomShacham commented Sep 21, 2016

Hi @dkoper thanks for your reply :)

Unfortunately the app was moved back to a DEA because it's quite critical. But the next time I see this bug I will re-run it with a CF_TRACE=true.

Also, can you provide more details about your environment? Platform, cf CLI version, Diego-Enabler plugin version, CF release version (see output cf api), etc.

Platform = vsphere
cf CLI version = (hard to say what it was but...) between 6.15.0 and 6.21.1 inclusive.

$ cf api
API endpoint: https://[redacted].com (API version: 2.59.0)

Diego-Enabler plugin version = 1.2.1
CF release version = 240

Thanks!

@dkoper
Copy link
Contributor

dkoper commented Sep 22, 2016

Hi @TomShacham

We fixed a potentially related issue in the cf CLI (found as part of #3), which was incorporated in cf CLI version 6.21.1. I'll close this issue. Please submit a new one with CF trace if you see it again on the latest cf CLI?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants