Re: [Openstack] Quantum CLI errors on Grizzly
Hi Jay, The log file ( /var/log/quantum/server.log) that you requested is empty :( What else can I do to trouble shoot ? On Mon, Apr 29, 2013 at 8:38 PM, Jay S Bryant jsbry...@us.ibm.com wrote: Ashutosh, Have you verified that the necessary Quantum processes are running? If not, ensure that quantum-dhcp-agent, quantum-l3-agent, quantum-openvswitch-agent and most importantly quantum are running. If those processes are running can you share the output from /var/log/quantum/server.log . It should contain a hint as to why the server is not ready for connections. Also, please be aware, the first time you start quantum it can take quite some time to be ready for CLI connections depending on the speed of the database you are using. * Jay S. Bryant** Linux Developer - OpenStack Enterprise Edition* [image: OpenStack Community Logo] Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From:Ashutosh Narayan aashutoshnara...@gmail.com To:OpenStack openstack@lists.launchpad.net, Date:04/29/2013 05:08 AM Subject:[Openstack] Quantum CLI errors on Grizzly Sent by:Openstack openstack-bounces+jsbryant= us.ibm@lists.launchpad.net -- Hi folks, I have installed Grizzly on CentOS 6.3 and was setting up Quantum by following the instructions given in the below link : *https://fedoraproject.org/wiki/Packstack_to_Quantum*https://fedoraproject.org/wiki/Packstack_to_Quantum In step 13 when I start using Quantum CLI to create a private network using the command - *quantum net-create private* I get [ Error 111 ] Connection refused as an error. I have installed OpenvSwitch from the source Even in the dashboard it's not allowing me to create Routers. Same Error 111 is seen there too. Any suggestions ? Thank you, -- Ashutosh Narayan * **http://ashutoshn.wordpress.com/* http://ashutoshn.wordpress.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Ashutosh Narayan http://ashutoshn.wordpress.com/ image/jpeg___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum CLI errors on Grizzly
Hi, If you want to see other logs in /var/log/quantum - Here are they : *dhcp-agent.log* 2013-05-08 18:02:30ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:02:40ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:03:40ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:03:50ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:04:50ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:05:00ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:06:00ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds *l3-agent.log:* 2013-05-08 18:03:15ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:04:15ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:04:25ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:05:26ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:05:36ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:06:36ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds 2013-05-08 18:06:46ERROR [quantum.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: [Errno -2] Name or service not known. Sleeping 60 seconds *openvswitch-agent.log:* Stderr: 'sudo: no tty present and no askpass program specified\n' 2013-05-08 18:07:31ERROR [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Failed reporting state! Traceback (most recent call last): File /usr/lib/python2.6/site-packages/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py, line 201, in _report_state self.agent_state) File /usr/lib/python2.6/site-packages/quantum/agent/rpc.py, line 66, in report_state topic=self.topic) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/proxy.py, line 80, in call return rpc.call(context, self._get_topic(topic), msg, timeout) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/__init__.py, line 140, in call return _get_impl().call(CONF, context, topic, msg, timeout) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/impl_qpid.py, line 610, in call rpc_amqp.get_connection_pool(conf, Connection)) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/amqp.py, line 613, in call rv = list(rv) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/amqp.py, line 555, in __iter__ self.done() File /usr/lib64/python2.6/contextlib.py, line 23, in __exit__ self.gen.next() File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/amqp.py, line 552, in __iter__ self._iterator.next() File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/impl_qpid.py, line 435, in iterconsume yield self.ensure(_error_callback, _consume) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/impl_qpid.py, line 379, in ensure error_callback(e) File /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/impl_qpid.py, line 420, in _error_callback raise rpc_common.Timeout() Timeout: Timeout while waiting on RPC response. 2013-05-08 18:07:31 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 56.20085 sec 2013-05-08 18:07:31ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-vsctl', '--timeout=2', 'list-ports', 'br-int']. Exception: Command: ['sudo', 'ovs-vsctl', '--timeout=2', 'list-ports', 'br-int'] Timeout: Timeout while waiting on RPC response. 2013-05-08 18:07:31 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 56.20085 sec 2013-05-08 18:07:31ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-vsctl', '--timeout=2', 'list-ports', 'br-int']. Exception: Command: ['sudo', 'ovs-vsctl', '--timeout=2', 'list-ports', 'br-int'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty
Re: [Openstack] Quantum CLI errors on Grizzly
Ashutosh, [ Error 111 ] Connection refused as an error. for the above error you might wanna check your keystone authentication part. create the service endpoints properly Ashok On Wed, May 8, 2013 at 5:52 PM, Ashutosh Narayan aashutoshnara...@gmail.com wrote: Hi Jay, The log file ( /var/log/quantum/server.log) that you requested is empty :( What else can I do to trouble shoot ? On Mon, Apr 29, 2013 at 8:38 PM, Jay S Bryant jsbry...@us.ibm.com wrote: Ashutosh, Have you verified that the necessary Quantum processes are running? If not, ensure that quantum-dhcp-agent, quantum-l3-agent, quantum-openvswitch-agent and most importantly quantum are running. If those processes are running can you share the output from /var/log/quantum/server.log . It should contain a hint as to why the server is not ready for connections. Also, please be aware, the first time you start quantum it can take quite some time to be ready for CLI connections depending on the speed of the database you are using. * Jay S. Bryant** Linux Developer - OpenStack Enterprise Edition* [image: OpenStack Community Logo] Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From:Ashutosh Narayan aashutoshnara...@gmail.com To:OpenStack openstack@lists.launchpad.net, Date:04/29/2013 05:08 AM Subject:[Openstack] Quantum CLI errors on Grizzly Sent by:Openstack openstack-bounces+jsbryant= us.ibm@lists.launchpad.net -- Hi folks, I have installed Grizzly on CentOS 6.3 and was setting up Quantum by following the instructions given in the below link : *https://fedoraproject.org/wiki/Packstack_to_Quantum*https://fedoraproject.org/wiki/Packstack_to_Quantum In step 13 when I start using Quantum CLI to create a private network using the command - *quantum net-create private* I get [ Error 111 ] Connection refused as an error. I have installed OpenvSwitch from the source Even in the dashboard it's not allowing me to create Routers. Same Error 111 is seen there too. Any suggestions ? Thank you, -- Ashutosh Narayan * **http://ashutoshn.wordpress.com/* http://ashutoshn.wordpress.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Ashutosh Narayan http://ashutoshn.wordpress.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regds, Ashok , Delivery Consultant, HP. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum CLI errors on Grizzly
Ashutosh, Have you verified that the necessary Quantum processes are running? If not, ensure that quantum-dhcp-agent, quantum-l3-agent, quantum-openvswitch-agent and most importantly quantum are running. If those processes are running can you share the output from /var/log/quantum/server.log . It should contain a hint as to why the server is not ready for connections. Also, please be aware, the first time you start quantum it can take quite some time to be ready for CLI connections depending on the speed of the database you are using. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Ashutosh Narayan aashutoshnara...@gmail.com To: OpenStack openstack@lists.launchpad.net, Date: 04/29/2013 05:08 AM Subject:[Openstack] Quantum CLI errors on Grizzly Sent by:Openstack openstack-bounces+jsbryant=us.ibm@lists.launchpad.net Hi folks, I have installed Grizzly on CentOS 6.3 and was setting up Quantum by following the instructions given in the below link : https://fedoraproject.org/wiki/Packstack_to_Quantum In step 13 when I start using Quantum CLI to create a private network using the command - quantum net-create private I get [ Error 111 ] Connection refused as an error. I have installed OpenvSwitch from the source Even in the dashboard it's not allowing me to create Routers. Same Error 111 is seen there too. Any suggestions ? Thank you, -- Ashutosh Narayan http://ashutoshn.wordpress.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp image/jpeg___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
