OK, I'm almost back to where I was when I had things working.
I was using an older version and starting with "oc cluster up", I am now using
the latest builds and starting with "openshift start".
But if I go to any pod's Logs tab in the UI console, I see this:
"Logs are not available. The lo
Can you open the network tab in the dev tools of your browser and look for
the websocket connections. I recommend using Chrome since it does a better
job of displaying websocket information.
Any time both logs and terminal are not working, its usually a symptom of
websockets failing to open.
On
Good call:
(unknown) WebSocket connection to
'wss://192.168.1.15:8443/api/v1/namespaces/openshift-infra/pods/heapster-dln…xterm+%2Fbin%2Fsh&access_token=CpQs_rRQetCoiXwAamUgface2Op20B7bEO7p4mov_rw'
failed: Error during WebSocket handshake: Unexpected response code: 500
- Original Message --
Same thing for both Logs and Terminal - getting a error code of 500 when the
websocket tries to connect.
I have no idea why - this used to always work - until I started using the
latest code.
- Original Message -
> Good call:
>
> (unknown) WebSocket connection to
> 'wss://192.168.1.15:
With a 500 I would expect to see something in the logs for the master.
Anything there?
On Wed, Feb 22, 2017 at 2:02 PM, John Mazzitelli wrote:
> Same thing for both Logs and Terminal - getting a error code of 500 when
> the websocket tries to connect.
>
> I have no idea why - this used to always
The only thing that seems related (when I click on a Logs or Terminal tab in
the UI -this is the only error that is logged):
E0222 14:15:38.835307 31426 errors.go:63] apiserver received an error that is
not an unversioned.Status: Get
https://localhost.localdomain:10250/containerLogs/default/h
127.0.0.1:10250 is the OpenShift node's port. Is your OpenShift process
listening on that port on the loopback interface?
On Wed, Feb 22, 2017 at 2:17 PM, John Mazzitelli wrote:
> The only thing that seems related (when I click on a Logs or Terminal tab
> in the UI -this is the only error that i
Well, that's a good question. When I start OpenShift using the openshift
executable, I pass in --listen so I ensure it listens to my LAN IP - so I do
this:
openshift start --listen=https://192.168.1.15:8443
Is that bad? :)
If you pass in a --listen option, is there something else I have to spe
- Original Message -
> I normally do this:
>
> $ openshift start --write-config openshift.local.config
>
> $ sudo openshift start --master-config
> openshift.local.config/master/master-config.yaml --node-config
> openshift.local.config//node-config.yaml.
>
> You can edit the config files
I normally do this:
$ openshift start --write-config openshift.local.config
$ sudo openshift start --master-config
openshift.local.config/master/master-config.yaml --node-config
openshift.local.config//node-config.yaml.
You can edit the config files as needed (although I rarely do). If you are
j
Ok, so the issue you're hitting is that the node portion of OpenShift is
calling itself localhost.localdomain, so when the master/api part of
OpenShift tries to talk to the node part, it uses the node's identifier,
which ends up being localhost. Try setting --hostname to 192.168.1.5 and
see if that
BINGO!
Thank you Andy and Jessica!
I specified --hostname and now I see Logs and can use the Terminal.
- Original Message -
> Ok, so the issue you're hitting is that the node portion of OpenShift is
> calling itself localhost.localdomain, so when the master/api part of
> OpenShift tries
12 matches
Mail list logo
