settingsLogin | Registersettings

[Openstack-operators] Newton consoleauth HA tokens

0 votes

All,

I attempted to deploy the nova service in HA, but when users attempt to
connect via the console, it doesn't work about 30% of the time and they
get the 1006 error. The nova-consoleauth service is reporting their
token as invalid. I am running memcached, and have tried referencing it
using both the legacy memcached_servers directive and in the new [cache]
configuration section. No dice. If I disable the nova-consoleauth
service on one of the nodes, everything works fine. I see lots of bug
reports floating around about this, but I can't quite get the solutions
I have found reliably working. I'm on Ubuntu 16.04 LTS+Newton from UCA.

Ideas?

--
v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
asked Jan 25, 2017 in openstack-operators by Chris_Apsey (400 points)   1 2

5 Responses

0 votes

Hello,
You should also define memcached servers in the default Nova section I
believe.
Try that.

Best regards
George

On Tue, 24 Jan 2017, 07:48 Chris Apsey, bitskrieg@bitskrieg.net wrote:

All,

I attempted to deploy the nova service in HA, but when users attempt to
connect via the console, it doesn't work about 30% of the time and they
get the 1006 error. The nova-consoleauth service is reporting their
token as invalid. I am running memcached, and have tried referencing it
using both the legacy memcached_servers directive and in the new [cache]
configuration section. No dice. If I disable the nova-consoleauth
service on one of the nodes, everything works fine. I see lots of bug
reports floating around about this, but I can't quite get the solutions
I have found reliably working. I'm on Ubuntu 16.04 LTS+Newton from UCA.

Ideas?

--
v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jan 24, 2017 by George_Paraskevas (380 points)  
0 votes

Did you try to restart memcached after chaning the configuration to HA ?

there are two sections where you can configure, memcachedservers
[DEFAULT]
[keystone
authtoken]

how your config looks like ?

Saverio

2017-01-24 6:48 GMT+01:00 Chris Apsey bitskrieg@bitskrieg.net:

All,

I attempted to deploy the nova service in HA, but when users attempt to
connect via the console, it doesn't work about 30% of the time and they get
the 1006 error. The nova-consoleauth service is reporting their token as
invalid. I am running memcached, and have tried referencing it using both
the legacy memcached_servers directive and in the new [cache] configuration
section. No dice. If I disable the nova-consoleauth service on one of the
nodes, everything works fine. I see lots of bug reports floating around
about this, but I can't quite get the solutions I have found reliably
working. I'm on Ubuntu 16.04 LTS+Newton from UCA.

Ideas?

--
v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jan 24, 2017 by Saverio_Proto (5,480 points)   1 3 5
0 votes

George,

No dice; I set the config directives in [default] or [cache]
individually as well as simultaneously, same behavior. I also restart
mmemcached between every change just-in-case. No changes.

Thank you for the suggestion, though.

Chris


v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net

On 2017-01-24 03:27, George Paraskevas wrote:
Hello,
You should also define memcached servers in the default Nova section I
believe.
Try that.

Best regards
George

On Tue, 24 Jan 2017, 07:48 Chris Apsey, bitskrieg@bitskrieg.net
wrote:

All,

I attempted to deploy the nova service in HA, but when users attempt
to
connect via the console, it doesn't work about 30% of the time and
they
get the 1006 error. The nova-consoleauth service is reporting their
token as invalid. I am running memcached, and have tried
referencing it
using both the legacy memcached_servers directive and in the new
[cache]
configuration section. No dice. If I disable the nova-consoleauth
service on one of the nodes, everything works fine. I see lots of
bug
reports floating around about this, but I can't quite get the
solutions
I have found reliably working. I'm on Ubuntu 16.04 LTS+Newton from
UCA.

Ideas?

--
v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jan 25, 2017 by Chris_Apsey (400 points)   1 2
0 votes

Saverio,

Here is my pertinent config data:

[default]
memcached_servers = 10.10.6.240:11211

[cache]
enablde = True <<<============================ I just noticed this
as I copied into the email.
memcacheservers = 10.10.6.240:11211
backend = oslo
cache.memcache_pool

[keystoneauthtoken]
memcached
servers = 10.10.6.240:11211

See above - I just noticed my config typo as I was getting ready to send
this. Changing it to 'enabled' seems to have solved the issue.
Spelling counts. This is a working config for anyone else who runs into
the same problems. Be sure to specify the backend under [cache], as the
default is null.

Thanks for the assist!

Chris


v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net

On 2017-01-24 11:36, Saverio Proto wrote:
Did you try to restart memcached after chaning the configuration to HA
?

there are two sections where you can configure, memcachedservers
[DEFAULT]
[keystone
authtoken]

how your config looks like ?

Saverio

2017-01-24 6:48 GMT+01:00 Chris Apsey bitskrieg@bitskrieg.net:

All,

I attempted to deploy the nova service in HA, but when users attempt
to
connect via the console, it doesn't work about 30% of the time and
they get
the 1006 error. The nova-consoleauth service is reporting their token
as
invalid. I am running memcached, and have tried referencing it using
both
the legacy memcached_servers directive and in the new [cache]
configuration
section. No dice. If I disable the nova-consoleauth service on one
of the
nodes, everything works fine. I see lots of bug reports floating
around
about this, but I can't quite get the solutions I have found reliably
working. I'm on Ubuntu 16.04 LTS+Newton from UCA.

Ideas?

--
v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jan 25, 2017 by Chris_Apsey (400 points)   1 2
0 votes

Chris,

Good to see that you finally got the issue resolved! One more thing, the
[default] should be [DEFAULT] I believe.

Best regards
George Paraskevas

On 25 January 2017 at 03:21, Chris Apsey bitskrieg@bitskrieg.net wrote:

Saverio,

Here is my pertinent config data:

[default]
memcached_servers = 10.10.6.240:11211

[cache]
enablde = True <<<============================ I just noticed this
as I copied into the email.
memcacheservers = 10.10.6.240:11211
backend = oslo
cache.memcache_pool

[keystoneauthtoken]
memcached
servers = 10.10.6.240:11211

See above - I just noticed my config typo as I was getting ready to send
this. Changing it to 'enabled' seems to have solved the issue. Spelling
counts. This is a working config for anyone else who runs into the same
problems. Be sure to specify the backend under [cache], as the default is
null.

Thanks for the assist!

Chris


v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net

On 2017-01-24 11:36, Saverio Proto wrote:

Did you try to restart memcached after chaning the configuration to HA ?

there are two sections where you can configure, memcachedservers
[DEFAULT]
[keystone
authtoken]

how your config looks like ?

Saverio

2017-01-24 6:48 GMT+01:00 Chris Apsey bitskrieg@bitskrieg.net:

All,

I attempted to deploy the nova service in HA, but when users attempt to
connect via the console, it doesn't work about 30% of the time and they
get
the 1006 error. The nova-consoleauth service is reporting their token as
invalid. I am running memcached, and have tried referencing it using
both
the legacy memcached_servers directive and in the new [cache]
configuration
section. No dice. If I disable the nova-consoleauth service on one of
the
nodes, everything works fine. I see lots of bug reports floating around
about this, but I can't quite get the solutions I have found reliably
working. I'm on Ubuntu 16.04 LTS+Newton from UCA.

Ideas?

--
v/r

Chris Apsey
bitskrieg@bitskrieg.net
https://www.bitskrieg.net


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jan 25, 2017 by George_Paraskevas (380 points)  
...