che-machine-exec(Kubernetes infra) after few hours get connection refused

[AndrienkoAleksandr]

che-machine-exec(Kubernetes infra) after few hours get connection refused:

messages.js:46 Uncaught (in promise) Error: Get https://172.30.0.1:443/api/v1/namespaces/mini-che/pods?labelSelector=che.workspace_id%3Dworkspaceb8ox77fvleydtylm: dial tcp 172.30.0.1:443: connect: connection refused
    at Proxy.<anonymous> (proxy-factory.ts:230)
    at n.<anonymous> (remote-terminal-widget.ts:267)
    at terminal-quick-open.ts:84
    at Object.next (terminal-quick-open.ts:84)
    at terminal-quick-open.ts:84
    at new Promise (<anonymous>)
    at a (terminal-quick-open.ts:84)

[AndrienkoAleksandr]

In progress

[AndrienkoAleksandr]

Seems the reason of the fail terminal work after few hours is another one. EOF exeception... I reproduced it only on the Minishift. Minikube and local openshift (deployed by https://github.com/eclipse/che/blob/master/deploy/openshift/ocp.sh) seems works fine.

2018/10/24 08:47:12 Use kubernetes implementation
--
  | 2018/10/24 08:47:12 ⇩ Registered HTTPRoutes:
  | 2018/10/24 08:47:12 Exec-Machine WebSocket routes:
  | 2018/10/24 08:47:12 ✓ MachineExec api end point(websocket) .... GET    /connect
  | 2018/10/24 08:47:12 ✓ Attach to exec(pure websocket) .......... GET    /attach/:id
  | 2018/10/24 08:47:12
  | 2018/10/24 08:47:12 ⇩ Registered RPCRoutes:
  | 2018/10/24 08:47:12 Json-rpc MachineExec Routes:
  | 2018/10/24 08:47:12 ✓ create
  | 2018/10/24 08:47:12 ✓ check
  | 2018/10/24 08:47:12 ✓ resize
  | 2018/10/24 08:50:40 Parsed id 1
  | 2018/10/24 09:11:19 failed to read ws-conn message
  | 2018/10/24 09:11:25 Parsed id 1
  | 2018/10/24 09:11:40 Error occurs on sending ping message to ws-conn. websocket: close sent
  | 2018/10/24 09:56:29 failed to read ws-conn message
  | 2018/10/24 09:56:55 Error occurs on sending ping message to ws-conn. websocket: close sent
  | 2018/10/24 09:57:00 Parsed id 1
  | 2018/10/24 09:57:26 failed to read ws-conn message
  | 2018/10/24 09:57:30 Error occurs on sending ping message to ws-conn. websocket: close sent
  | 2018/10/24 09:57:33 Parsed id 1
  | 2018/10/24 11:54:52 failed to read ws-conn message
  | 2018/10/24 11:54:52 Couldn't write message to the tunnel. Message: *jsonrpc.Response, &{2.0 120 [123 34 105 100 34 58 49 44 34 116 101 120 116 34 58 34 69 120 101 99 32 119 105 116 104 32 105 100 32 49 32 32 119 97 115 32 115 117 99 99 101 115 115 102 117 108 108 121 32 114 101 115 105 122 101 100 34 125] <nil>}
  | 2018/10/24 11:54:52 Couldn't write message to the tunnel. Message: *jsonrpc.Response, &{2.0 121 [123 34 105 100 34 58 49 44 34 116 101 120 116 34 58 34 69 120 101 99 32 119 105 116 104 32 105 100 32 49 32 32 119 97 115 32 115 117 99 99 101 115 115 102 117 108 108 121 32 114 101 115 105 122 101 100 34 125] <nil>}
  | 2018/10/24 11:54:52 Couldn't write message to the tunnel. Message: *jsonrpc.Response, &{2.0 122 [123 34 105 100 34 58 49 44 34 116 101 120 116 34 58 34 69 120 101 99 32 119 105 116 104 32 105 100 32 49 32 32 119 97 115 32 115 117 99 99 101 115 115 102 117 108 108 121 32 114 101 115 105 122 101 100 34 125] <nil>}
  | 2018/10/24 11:54:52 Couldn't write message to the tunnel. Message: *jsonrpc.Response, &{2.0 123 [123 34 105 100 34 58 49 44 34 116 101 120 116 34 58 34 69 120 101 99 32 119 105 116 104 32 105 100 32 49 32 32 119 97 115 32 115 117 99 99 101 115 115 102 117 108 108 121 32 114 101 115 105 122 101 100 34 125] <nil>}
  | 2018/10/24 11:54:52 Couldn't write message to the tunnel. Message: *jsonrpc.Response, &{2.0 124 [123 34 105 100 34 58 49 44 34 116 101 120 116 34 58 34 69 120 101 99 32 119 105 116 104 32 105 100 32 49 32 32 119 97 115 32 115 117 99 99 101 115 115 102 117 108 108 121 32 114 101 115 105 122 101 100 34 125] <nil>}
  | 2018/10/24 11:54:52 Couldn't write message to the tunnel. Message: *jsonrpc.Response, &{2.0 125 [123 34 105 100 34 58 49 44 34 116 101 120 116 34 58 34 69 120 101 99 32 119 105 116 104 32 105 100 32 49 32 32 119 97 115 32 115 117 99 99 101 115 115 102 117 108 108 121 32 114 101 115 105 122 101 100 34 125] <nil>}
  | 2018/10/24 11:54:52 Error while closing connection, close tcp 172.17.0.10:4444->172.17.0.1:49068: use of closed network connection
  | 2018/10/24 11:54:52 Error occurs on sending ping message to ws-conn. websocket: close sent
  | 2018/10/24 11:58:00 Parsed id 1
  | 2018/10/24 13:37:01 failed to read ws-conn message
  | 2018/10/24 13:37:08 Parsed id 1
  | 2018/10/24 13:37:30 Error occurs on sending ping message to ws-conn. websocket: close sent
  | 2018/10/24 15:31:57 Parsed id 2
  | E1025 06:30:14.512620       1 v2.go:105] write tcp 172.17.0.10:48648->172.30.0.1:443: write: connection reset by peer
  | E1025 06:30:16.561519       1 v2.go:105] write tcp 172.17.0.10:34150->172.30.0.1:443: write: connection reset by peer
  | E1025 06:38:20.570967       1 v3.go:79] EOF
  | E1025 06:38:20.616313       1 v3.go:79] EOF
  | E1025 06:38:20.659396       1 v3.go:79] EOF
  | E1025 06:38:20.705581       1 v3.go:79] EOF
  | E1025 06:38:20.735290       1 v3.go:79] EOF
  | E1025 06:38:20.751263       1 v3.go:79] EOF
  | E1025 06:38:22.041758       1 v3.go:79] EOF
  | E1025 06:38:25.321216       1 v3.go:79] EOF
  | E1025 06:38:25.336138       1 v3.go:79] EOF

[AndrienkoAleksandr]

Merged https://github.com/ws-skeleton/che-machine-exec/pull/6