EventStore not working in minikube?

I’m not sure if doofed this up or what but…

I’m trying to set up a dev environment using Minikube in Hyper-V. I got everything else up and running fine without much effort, but EventStore is having issues. It seems to start up fine but when I try to browse to the ES dashboard, it won’t load.

This was returned in the browser window:

o������������������Invalid TCP frame received. Error: Package size is out of bounds: 542393671 (max: 67108864)..

I checked logs in kubernetes and saw this:

[00001,19,22:08:33.968] Lost connection from 172.17.0.1:64267
[00001,20,22:08:38.989] External TCP connection accepted: [Normal, 172.17.
cc-9a31-8e676298082e}].
[00001,20,22:08:38.989] FRAMING ERROR! Data:
[00001,20,22:08:38.989] 000000: 47 45 54 20 2F 20 48 54 54 50 2F 31 2E 31
000016: 48 6F 73 74 3A 20 31 30 2E 31 30 2E 31 2E 36 36  | Host: 10.10.1.6
000032: 3A 33 31 39 37 30 0D 0A 43 6F 6E 6E 65 63 74 69  | :31970..Connect
000048: 6F 6E 3A 20 6B 65 65 70 2D 61 6C 69 76 65 0D 0A  | on: keep-alive.
000064: 43 61 63 68 65 2D 43 6F 6E 74 72 6F 6C 3A 20 6D  | Cache-Control:
000080: 61 78 2D 61 67 65 3D 30 0D 0A 55 70 67 72 61 64  | ax-age=0..Upgra
000096: 65 2D 49 6E 73 65 63 75 72 65 2D 52 65 71 75 65  | e-Insecure-Requ
000112: 73 74 73 3A 20 31 0D 0A 55 73 65 72 2D 41 67 65  | sts: 1..User-Ag
000128: 6E 74 3A 20 4D 6F 7A 69 6C 6C 61 2F 35 2E 30 20  | nt: Mozilla/5.0
000144: 28 57 69 6E 64 6F 77 73 20 4E 54 20 31 30 2E 30  | (Windows NT 10.
000160: 3B 20 57 69 6E 36 34 3B 20 78 36 34 29 20 41 70  | ; Win64; x64) A
000176: 70 6C 65 57 65 62 4B 69 74 2F 35 33 37 2E 33 36  | pleWebKit/537.3
000192: 20 28 4B 48 54 4D 4C 2C 20 6C 69 6B 65 20 47 65  |  (KHTML, like G
000208: 63 6B 6F 29 20 43 68 72 6F 6D 65 2F 36 32 2E 30  | cko) Chrome/62.
000224: 2E 33 32 30 32 2E 39 34 20 53 61 66 61 72 69 2F  | .3202.94 Safari
000240: 35 33 37 2E 33 36 0D 0A 41 63 63 65 70 74 3A 20  | 537.36..Accept:
000256: 74 65 78 74 2F 68 74 6D 6C 2C 61 70 70 6C 69 63  | text/html,appli
000272: 61 74 69 6F 6E 2F 78 68 74 6D 6C 2B 78 6D 6C 2C  | ation/xhtml+xml
000288: 61 70 70 6C 69 63 61 74 69 6F 6E 2F 78 6D 6C 3B  | application/xml
000304: 71 3D 30 2E 39 2C 69 6D 61 67 65 2F 77 65 62 70  | q=0.9,image/web
000320: 2C 69 6D 61 67 65 2F 61 70 6E 67 2C 2A 2F 2A 3B  | ,image/apng,*/*
000336: 71 3D 30 2E 38 0D 0A 41 63 63 65 70 74 2D 45 6E  | q=0.8..Accept-E
000352: 63 6F 64 69 6E 67 3A 20 67 7A 69 70 2C 20 64 65  | coding: gzip, d
000368: 66 6C 61 74 65 0D 0A 41 63 63 65 70 74 2D 4C 61  | flate..Accept-L
000384: 6E 67 75 61 67 65 3A 20 65 6E 2D 55 53 2C 65 6E  | nguage: en-US,e
000400: 3B 71 3D 30 2E 39 0D 0A 0D 0A                    | ;q=0.9....

``

Does anyone have any ideas? A friend suggested it might have something to do with how EventStore deals with the TCP stack and might be having issues in the Kubernetes environment

Deployment config:

{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "eventstore",
    "namespace": "default",
    "selfLink": "/apis/extensions/v1beta1/namespaces/default/deployments/eventstore",
    "uid": "ffe6f460-db99-11e7-a9c2-00155dffba06",
    "resourceVersion": "277",
    "generation": 1,
    "creationTimestamp": "2017-12-07T22:00:12Z",
    "labels": {
      "app": "eventstore"
    },
    "annotations": {
      "deployment.kubernetes.io/revision": "1"
    }
  },
  "spec": {
    "replicas": 1,
    "selector": {
      "matchLabels": {
        "app": "eventstore"
      }
    },
    "template": {
      "metadata": {
        "name": "eventstore",
        "creationTimestamp": null,
        "labels": {
          "app": "eventstore"
        }
      },
      "spec": {
        "containers": [
          {
            "name": "eventstore",
            "image": "eventstore/eventstore",
            "resources": {},
            "terminationMessagePath": "/dev/termination-log",
            "terminationMessagePolicy": "File",
            "imagePullPolicy": "Always",
            "securityContext": {
              "privileged": false
            }
          }
        ],
        "restartPolicy": "Always",
        "terminationGracePeriodSeconds": 30,
        "dnsPolicy": "ClusterFirst",
        "securityContext": {},
        "schedulerName": "default-scheduler"
      }
    },
    "strategy": {
      "type": "RollingUpdate",
      "rollingUpdate": {
        "maxUnavailable": "25%",
        "maxSurge": "25%"
      }
    },
    "revisionHistoryLimit": 10,
    "progressDeadlineSeconds": 600
  },
  "status": {
    "observedGeneration": 1,
    "replicas": 1,
    "updatedReplicas": 1,
    "readyReplicas": 1,
    "availableReplicas": 1,
    "conditions": [
      {
        "type": "Available",
        "status": "True",
        "lastUpdateTime": "2017-12-07T22:00:22Z",
        "lastTransitionTime": "2017-12-07T22:00:22Z",
        "reason": "MinimumReplicasAvailable",
        "message": "Deployment has minimum availability."
      },
      {
        "type": "Progressing",
        "status": "True",
        "lastUpdateTime": "2017-12-07T22:00:22Z",
        "lastTransitionTime": "2017-12-07T22:00:12Z",
        "reason": "NewReplicaSetAvailable",
        "message": "ReplicaSet \"eventstore-7b85cc597b\" has successfully progressed."
      }
    ]
  }
}

``

It sounds like you are browsing to the tcp port not the http port :wink:

I agree that it looks that way, but It’s forwarding to 2113, I can see the redirect happen in the browser. The service config has ports 1113:1113 and 2113:2113. :confused:

No big deal at the moment. I’m not going to go down this path anymore. Just gonna use swarm which doesn’t seem to be having the issue.

I can assure you it is that way as the error message you are getting there is the tcp server not understanding the http request it is receiving.
t

Ok I believe you. We checked the config several times and had the same problem. We didn’t have time to continue messing with it so we just dropped it and used a real kube install. There was a release note saying that the windows version was still in beta, so maybe there was some internal nonsense there we’ll revisit some other time. Thanks

I am not sure why kube would have a problem with ports. This is most certainly a problem with port setups. Literally the data received back is http data not tcp data and is dumped as such.