kubernetes: kubectl logs -f failed with 'unexpected stream type "" '
I was running a kubectl logs -f, not for long, that broke unexpectedly with
{"level":"info","msg":"Sync time: 2.276207ms","time":"2017-06-20T17:30:02Z"}
{"level":"info","msg":"Sync time: 5.663623ms","time":"2017-06-20T17:30:32Z"}
unexpected stream type ""
Doesn’t seem normal.
$ kc version
Client Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.0-alpha.0.533+1168552fade5fd", GitCommit:"1168552fade5fd138e4af664ed7b31ec40c6a20f", GitTreeState:"clean", BuildDate:"2017-06-10T16:56:39Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T18:33:17Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 6
- Comments: 19 (12 by maintainers)
Commits related to this issue
- Merge pull request #50381 from sczizzo/bugfix-issue-47800 Automatic merge from submit-queue (batch tested with PRs 50381, 51307, 49645, 50995, 51523) Bugfix: Use local JSON log buffer in parseDocker... — committed to kubernetes/kubernetes by deleted user 7 years ago
- Merge pull request #51872 from feiskyer/503812 Automatic merge from submit-queue Automated cherry pick of #50381 to release-1.6 **What this PR does / why we need it**: Use local JSON log buffer ... — committed to kubernetes/kubernetes by deleted user 7 years ago
FYI, the fix is in 1.7.6.
So I have access after all 😃 docker 11.2 is used and the log driver is json-file. Unfortunately, I have scaled the deployment down since I had the issue and now I cannot find the container log under /var/log/containers. Noted for the next time tho