Ask Your Question

Ram.Meena's profile - activity

2017-10-02 18:12:05 -0500 received badge  Good Answer (source)
2017-04-03 09:09:38 -0500 received badge  Famous Question (source)
2017-04-03 09:09:38 -0500 received badge  Notable Question (source)
2017-01-26 08:42:51 -0500 received badge  Popular Question (source)
2017-01-16 07:25:16 -0500 asked a question Newton RabbitMQ transport_url high availability

Hi,

In newton release rabbitmq is configured with transport_url. so how to specify multiple rabbitmq hosts in this parameter or is there any other way to achieve ha for rabbitmq.

2016-05-15 23:06:51 -0500 received badge  Nice Answer (source)
2015-08-28 08:13:53 -0500 received badge  Famous Question (source)
2015-07-23 07:11:52 -0500 answered a question Setup CEPH as a backend for Glance

Hi,

As written by Benny, you need to write below settings in glance api configuration file:

[glance_store]
default_store = rbd
stores = glance.store.rbd.Store
rbd_store_pool = images
rbd_store_user = glance
rbd_store_ceph_conf = /etc/ceph/ceph.conf
rbd_store_chunk_size = 8

You should make sure to setup appropriate authentication with ceph cluster.

2015-07-23 06:13:26 -0500 edited answer br-int internal vlan tag

The vm interfaces are attached to the qbr<xxx> Linux Bridge of the VM created. The qbr interface is a linux bridge attached with qvb<xxx> of the veth pair. The other side of the pair being a qvo<xxx> interface of br-int vlan port. So from vm side: vm(eth)->qbr(LinuxBridge)->qvb(veth)->qvo(veth)->vlan port(br-int).

Regards, Soumiyajit.

2015-07-23 06:02:18 -0500 received badge  Critic (source)
2015-07-23 05:33:55 -0500 answered a question Rescheduling instance fails if the first host that's chosen is in a failed state

Hi,

Can you write below settings in nova.conf and restart necessary services.

vif_plugging_is_fatal: false
vif_plugging_timeout: 0
2015-07-15 06:14:32 -0500 received badge  Notable Question (source)
2015-07-15 04:16:29 -0500 commented question Keystone port 5000 used by Python

Could you please try rebooting the server once..:)

2015-07-15 02:53:28 -0500 answered a question Error: unable to connect to node rabbit@controller: nodedown

Please verify below things:

  1. hostname of your controller node is same in '/etc/hostname' and '/etc/hosts'.
  2. Make sure you have only single entry of your hostname in '/etc/hosts' like below:

root@controller:~# cat /etc/hosts 192.168.10.10 controller

  1. if currently settings are not as above then you may need to uninstall/purge rabbitmq once and reinstall it.

Give it a try..:)

2015-07-14 06:31:13 -0500 received badge  Popular Question (source)
2015-07-14 05:22:07 -0500 commented answer Glance docker images not created, always in SAVING state

Still same error 'write /dev/stdout: broken pipe' and image is in 'SAVING' state.

2015-07-14 05:22:07 -0500 received badge  Commentator
2015-07-14 05:04:08 -0500 commented answer Glance docker images not created, always in SAVING state

I am pulling it now...:)

2015-07-14 04:56:03 -0500 commented answer Glance docker images not created, always in SAVING state

I have already pulled the images..you can check below output:

ubuntu@controller:~$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
cirros              latest              d8de71c04044        11 weeks ago        7.698 MB
2015-07-14 03:52:06 -0500 asked a question Glance docker images not created, always in SAVING state

Hi,

I have installed Openstack Kilo on Ubuntu 14.04 and integrated glance with docker. but when I run glance image-create command, images are always in saving state.

root@controller:~# docker save cirros | glance image-create --visibility public --container-format=docker --disk-format=raw --name cirros --progress
+------------------+--------------------------------------+
| Property         | Value                                |
+------------------+--------------------------------------+
| checksum         | None                                 |
| container_format | docker                               |
| created_at       | 2015-07-14T08:36:52Z                 |
| disk_format      | raw                                  |
| id               | 3edeb153-252f-4065-af61-f9628c3c5873 |
| min_disk         | 0                                    |
| min_ram          | 0                                    |
| name             | cirros                               |
| owner            | b48769b527734606a42bf9e69e8e9b14     |
| protected        | False                                |
| size             | None                                 |
| status           | queued                               |
| tags             | []                                   |
| updated_at       | 2015-07-14T08:36:52Z                 |
| virtual_size     | None                                 |
| visibility       | public                               |
+------------------+--------------------------------------+
write /dev/stdout: broken pipe

root@controller:~# nova image-list
+--------------------------------------+---------------------+--------+--------+
| ID                                   | Name                | Status | Server |
+--------------------------------------+---------------------+--------+--------+
| 24a1275d-ffa1-487a-aef0-0b79a6808e58 | Ubuntu-Trusty       | ACTIVE |        |
| ed5a37a3-717d-41e6-a073-88b6037f10dd | cirros              | SAVING |        |
| fa543735-28a8-4445-899c-e00747e88478 | cirros              | SAVING |        |
| 14954dd5-bc42-4f70-be59-c8c839ed72dc | cirros-0.3.4-x86_64 | ACTIVE |        |
+--------------------------------------+---------------------+--------+--------+

There is no error in logs of glance api and registry.

I have below configure in glance-api.conf:

[image_format]
container_formats = ami,ari,aki,bare,ovf,docker

[glance_store]
default_store = file
filesystem_store_datadir = /var/lib/glance/images/

If I create normal images it works fine but when I create images with docker save, it gives error 'write /dev/stdout: broken pipe' and images are always in saving state.

Please suggest.

2015-07-10 02:14:30 -0500 received badge  Supporter (source)
2014-11-27 11:08:09 -0500 edited answer AMQP server on 10.0.0.11:5672 is unreachable

@Ram.Meena,

Below is the status which you requested to check.

"[root@controller ~]# systemctl status rabbitmq-server.service -l

rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled)
   Active: active (running) since Wed 2014-11-26 19:15:17 IST; 27min ago
  Process: 47237 ExecStopPost=/usr/bin/rm /var/run/rabbitmq/pid (code=exited, status=0/SUCCESS)
  Process: 47210 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
  Process: 47268 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmqctl wait /var/run/rabbitmq/pid (code=exited, status=0/SUCCESS)
  Process: 47239 ExecStartPre=/bin/sh -c /usr/lib/rabbitmq/bin/rabbitmqctl status > /dev/null 2>&1 (code=exited, status=2)
 Main PID: 47267 (beam)
   CGroup: /system.slice/rabbitmq-server.service
           ââ47267 /usr/lib64/erlang/erts-5.10.4/bin/beam -W w -K true -A30 -P 1048576 -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.1.5/sbin/../ebin -noshell -noinput -s rabbit boot -sname rabbit@controller -boot start_sasl -kernel inet_default_connect_options [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false -rabbit error_logger {file,"/var/log/rabbitmq/rabbit@controller.log"} -rabbit sasl_error_logger {file,"/var/log/rabbitmq/rabbit@controller-sasl.log"} -rabbit enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir "/usr/lib/rabbitmq/lib/rabbitmq_server-3.1.5/sbin/../plugins" -rabbit plugins_expand_dir "/var/lib/rabbitmq/mnesia/rabbit@controller-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit@controller"
           ââ47368 inet_gethost 4
           ââ47369 inet_gethost 4
Nov 26 19:15:15 controller rabbitmqctl[47268]: pid is 47267 ...
Nov 26 19:15:15 controller rabbitmq-server[47267]: RabbitMQ 3.1.5. Copyright (C) 2007-2013 GoPivotal, Inc.
Nov 26 19:15:15 controller rabbitmq-server[47267]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Nov 26 19:15:15 controller rabbitmq-server[47267]: ##  ##
Nov 26 19:15:15 controller rabbitmq-server[47267]: ##########  Logs: /var/log/rabbitmq/rabbit@controller.log
Nov 26 19:15:15 controller rabbitmq-server[47267]: ######  ##        /var/log/rabbitmq/rabbit@controller-sasl.log
Nov 26 19:15:15 controller rabbitmq-server[47267]: ##########
Nov 26 19:15:16 controller rabbitmq-server[47267]: Starting broker... completed with 0 plugins.
Nov 26 19:15:17 controller rabbitmqctl[47268]: ...done.
Nov 26 19:15:17 controller systemd[1]: Started RabbitMQ broker."


"[root@controller ~]# rabbitmqctl status

Status of node rabbit@controller ...
[{pid,47267},
 {running_applications,[{rabbit,"RabbitMQ","3.1.5"},
                        {os_mon,"CPO  CXC 138 46","2.2.14"},
                        {xmerl,"XML parser","1.3.6"},
                        {mnesia,"MNESIA  CXC 138 12","4.11"},
                        {sasl,"SASL  CXC 138 11","2.3.4"},
                        {stdlib,"ERTS  CXC 138 10","1.19.4"},
                        {kernel,"ERTS  CXC 138 10","2.16.4"}]},
 {os,{unix,linux}},
 {erlang_version,"Erlang R16B03-1 (erts-5.10.4) [source] [64-bit] [async-threads:30] [hipe] [kernel-poll:true]\n"},
 {memory,[{total,35439832},
          {connection_procs,36904},
          {queue_procs,5440},
          {plugins,0},
          {other_proc,13412016},
          {mnesia,57232},
          {mgmt_db,0},
          {msg_index,33936},
          {other_ets,727128},
          {binary,670208},
          {code,16441148},
          {atom,594537},
          {other_system,3461283}]},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,414043340},
 {disk_free_limit,1000000000},
 {disk_free,7424532480},
 {file_descriptors,[{total_limit,924},
                    {total_used,4},
                    {sockets_limit,829},
                    {sockets_used,2}]},
 {processes,[{limit,1048576},{used,127}]},
 {run_queue,0},
 {uptime,1657}]
...done."

"[root@controller ...
(more)
2014-11-27 08:36:51 -0500 commented answer AMQP server on 10.0.0.11:5672 is unreachable

Did you check if firewall is blocking the connection on '5672' port between controller and compute node?. You should check by disabling the firewall and disabling selinux for diagnosis purposes.

2014-11-27 08:33:54 -0500 commented answer AMQP server on 10.0.0.11:5672 is unreachable

RabbitMQ server seems to be running fine. However, there is no connection established with compute node so it seems that firewall is blocking the access. You should disable the firewall for diagnosis and check it. Also make sure that there is no lag between controller and compute nodes.

2014-11-27 08:27:45 -0500 answered a question All neutron commands returns http 404

Hi,

You should verify if the neutron endpoint is created correctly. I would suggest you to delete the existing neutron user, service, endpoint and recreate them carefully following the Openstack Installation docs.

2014-11-27 08:21:11 -0500 answered a question Failed to allocate the network(s), not rescheduling

Hi,

Please change the debug mode 'true' in nova configuration file as below:

debug=True

Restart the nova compute service and check the logs again for more detailed error messages. You may also provide the logs at http://paste.openstack.org/ .

You will need to set the 'virt_type = qemu' if you are using vmware. Make sure that your installation is able to allocate appropriate resources to newly launched instances, you may try to launch the instances using 'cirros' image which needs very less amount of resources.

2014-11-27 07:46:14 -0500 edited answer juno vm stuck at spawning state

Hi,

Please change the debug mode 'true' in nova configuration file as below:

debug=True

Restart the nova compute service and check the logs again for more detailed error messages. You may also provide the logs at http://paste.openstack.org/ .

You will need to set the 'virt_type = qemu' if you are using vmware. Make sure that your installation is able to allocate IP address to newly launched instances i.e. nova network should be setup correctly following the OpenStack installation docs.

2014-11-27 07:44:04 -0500 answered a question instance stuck in build/scheduling

Hi,

Please change the debug mode 'true' in nova configuration file(nova.conf) as below:

debug=True
vebose=True

Restart the nova compute service and check the logs again for more detailed error messages.

Also make sure that nova-network is setup correctly and assigning IPs to newly created instances.

Please provide the detailed logs of nova-api and nova-compute for further tracing of the issue. You may provide the logs using http://paste.openstack.org/ .

2014-11-27 05:52:34 -0500 commented answer AMQP server on 10.0.0.11:5672 is unreachable

If your RabbitMQ server is running on controller node then you need to run these commands on controller node not on compute node. These commands are for RabbitMQ service diagnosis.

2014-11-27 05:50:33 -0500 edited answer nova service-list problem : libxenlight state driver is not active

Hi,

At the very first, it seems that compute node not able to connect successfully with AMQP server. I would suggest you to verify the 'RabbitMQ status' and make sure that all OpenStack nodes are able to ping/connect with RabbitMQ server.

To verify if RabbitMQ service is running on your rabbit server, run below command: -

#systemctl status rabbitmq-server.service -l

To verify the RabbitMQ server status run the below command: -

#rabbitmqctl status

This command should print a detailed output of various information related to AMQP server. If the status is good then you need to make sure that rabbitmq port is allowed to make connection between your openstack nodes through firewall.

On RabbitMQ server you may run the below command to check if your compute node is able to establish connection with rabbit server:-

   # lsof -i :5672|grep 'compute_node_ip'

Make sure that there is no time lag between your openstack node, all the nodes should be synced with a central server time using NTP.

After verifying with above steps, I would also suggest you to change the debug mode 'true' in nova configuration file as below:

debug=True

Restart the nova compute service and try again with your operation and check the logs again for more detailed messages.

2014-11-27 05:46:19 -0500 edited answer Juno - error while launching instance

Hi,

The issue seems to be related with AMQP server. I have also configured the openstack with Juno release and my rabbitmq settings are as below:-

rpc_backend=rabbit
rabbit_host=controller
rabbit_user=guest
rabbit_password=Password

Where password is specific to your installation and you may try changing the rpc_backend to 'rabbit'. You need to make the similar settings in all your openstack nodes configuration files.

I would suggest you to verify the 'RabbitMQ status' and make sure that all OpenStack nodes are able to ping/connect with RabbitMQ server.

To verify if RabbitMQ service is running on your rabbit server, run below command: -

#systemctl status rabbitmq-server.service -l

To verify the RabbitMQ server status run the below command: -

#rabbitmqctl status

This command should print a detailed output of various information related to AMQP server. If the status is good then you need to make sure that rabbitmq port is allowed to make connection between your openstack nodes through firewall.

On RabbitMQ server you may run the below command to check if your compute node is able to establish connection with rabbit server:-

   # lsof -i :5672|grep 'compute_node_ip'

Make sure that there is no time lag between your openstack node, all the nodes should be synced with a central server time using NTP.

I would also suggest you to change the debug mode 'true' in nova configuration file as below:

debug=True

Restart the nova compute service and check the logs again for more detailed messages.

2014-11-27 05:43:17 -0500 commented answer juno nova instance stuck in BUILD scheduling

I would also suggest you to change the debug mode 'True' in nova configuration file as below:

debug=True

Also set 'verbose = True'

Restart the nova compute service and try again with your operation and check the logs again for more detailed error messages.

2014-11-27 04:15:13 -0500 answered a question 'neutron agent-list' show nothing

Hi,

The same problem has been reported here already, would be great if you can refer to the below post:-

No module named rabbit

2014-11-27 04:04:26 -0500 answered a question systemctl status neutron-server.service is not started

First I would suggest you to verify the 'RabbitMQ status' and make sure that all OpenStack nodes are able to ping/connect with RabbitMQ server.

To verify if RabbitMQ service is running on your rabbit server, run below command : -

#systemctl status rabbitmq-server.service -l

or

#service rabbitmq-server status

To verify the RabbitMQ server status run the below command: -

#rabbitmqctl status

This command should print a detailed output of various information related to AMQP server. If the status is good then you need to make sure that rabbitmq port is allowed to make connection between your openstack nodes through firewall.

On RabbitMQ server you may run the below command to check if your compute node is able to establish connection with rabbit server:-

   # lsof -i :5672|grep 'compute_node_ip'

Make sure that there is no time lag between your openstack node, all the nodes should be synced with a central server time using NTP.

2014-11-27 03:48:34 -0500 answered a question AMQP server on 10.0.0.11:5672 is unreachable

First I would suggest you to verify the 'RabbitMQ status' and make sure that all OpenStack nodes are able to ping/connect with RabbitMQ server.

To verify if RabbitMQ service is running on your rabbit server, run below command: -

#systemctl status rabbitmq-server.service -l

To verify the RabbitMQ server status run the below command: -

#rabbitmqctl status

This command should print a detailed output of various information related to AMQP server. If the status is good then you need to make sure that rabbitmq port is allowed to make connection between your openstack nodes through firewall.

On RabbitMQ server you may run the below command to check if your compute node is able to establish connection with rabbit server:-

   # lsof -i :5672|grep 'compute_node_ip'

Make sure that there is no time lag between your openstack node, all the nodes should be synced with a central server time using NTP.

2014-11-25 23:08:29 -0500 answered a question error in creating instances "no valid host was found"

Hi,

Since there is a possibility that hypervisor on underlying vmware VM is not working appropriately so I would suggest you to check if you can create VMs using 'virt-install' command and check if your hypervisor (KVM/QEMU) is working or not. 'virt-install' is a command line tool for provisioning new virtual machines using the "libvirt" hypervisor management library. You may also use the 'virt-manager' if you need GUI to create VM. 'virt-manager' can be used to manage the created virtual machines via GUI and to access the consoles.

2014-11-25 04:14:48 -0500 commented answer Nova-compute failure due to libvirt

You can install 'virt-manager' command to manage the created virtual machines and to access the consoles.

2014-11-25 04:09:19 -0500 answered a question juno keystone driver persistence

According to the official documentation Configuring Keystone in section 'Token Persistence Driver' below information has been published:-

Keystone supports customizable token persistence drivers. These can be specified in the [token] section of the configuration file. Keystone provides three non-test persistence backends. These can be set with the [token]\driver configuration option.

The drivers Keystone provides are:

keystone.token.persistence.backends.memcache_pool.Token - The pooled memcached token persistence engine. This backend supports the concept of pooled memcache client object (allowing for the re-use of the client objects). This backend has a number of extra tunable options in the [memcache] section of the config.

keystone.token.persistence.backends.sql.Token - The SQL-based (default) token persistence engine.

keystone.token.persistence.backends.memcache.Token - The memcached based token persistence backend. This backend relies on dogpile.cache and stores the token data in a set of memcached servers. The servers URLs are specified in the [memcache]\servers configuration option in the Keystone config.

However recently I have installed the Juno on RHEL 7 system and value of 'driver' parameter in my keystone.conf is below:

driver=keystone.token.backends.sql.Token

You may also try if it works. Meanwhile I am also going to check it on ubuntu based system and will update here with my findings.

2014-11-24 00:45:50 -0500 answered a question juno glance Invalid OpenStack Identity credentials

Hi,

Could you please verify the '[keystone_authtoken]' section in glance-api and glance-registry file. Make sure that you have added 'auth_protocol=http' in this section along with other parameters like the following:-

[keystone_authtoken]
auth_host=controller
auth_protocol=http
auth_uri=http://controller:5000/
admin_tenant_name=services
admin_user=glance
admin_password=f175010940df4b64

You will need to replace the password and other credentials according to your environment. It should resolve the issue you are facing.

2014-11-24 00:14:33 -0500 answered a question packstack failing with error on Redahat 7

Hi,

Make sure that your server is able to resolve public DNS domains. You should verify if appropriate nameservers have been setup in '/etc/resolv.conf' file. You may use the google open dns ip addresses in this file.

Also run the 'yum repolist' command to make sure that all the needed repos are working on your server. All the needed repositories should be installed and enabled on your server, like:

  1. Extra Packages for Enterprise Linux (EPEL)

  2. OpenStack Juno Repository

Then run 'yum clean all' and then run the packstack installation command again or run the packstack installation with its answer file.

2014-11-23 01:12:32 -0500 received badge  Nice Answer (source)