<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>nova-consoleauth maintains a little local persistence by default, so you probably only run one unless you've done work or configuration to localize that persistent data for all instances. nova-cert is in the same boat. <br><br>-joe</div><div><br>On May 11, 2013, at 6:46 PM, Juan José Pavlik Salles <<a href="mailto:jjpavlik@gmail.com">jjpavlik@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><p>Hi guys, on friday i was trying to reach my vms through novnc proxy and i ran into some kind of odd behaviour. One every two attempts were successfull so we started watching logs. after a couple of hours stopping and starting services we realized that this strange behaviour was due to we had two nova-consoleauth instances running, one per compute node. We stopped one of the instances a everything started to work just fine, even both novncproxies.<br>
I found this <a href="https://bugs.launchpad.net/nova/+bug/989337">https://bugs.launchpad.net/nova/+bug/989337</a> but it's suppossed to be fixed in folsom, and i'm running grizzly. </p>
<p>Should i run just one instance of nova-consoleauth?</p>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OpenStack-operators mailing list</span><br><span><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></span><br></div></blockquote></body></html>