Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why is nova-api not listeing on 8774,even though the process is running

Hi I have deployed the overcloud using tripleo , so far the stack has been created but while validating the installation , i found out that nova-api is not listening in 8774 in the controller,

the nova-api process is running fine and is listening on 8775 Here are the details

systemctl restart openstack-nova-api

    [root@overcloud-controller-0 heat-admin]# netstat -tulpn |grep 8774
    tcp        0      0 172.17.0.12:8774        0.0.0.0:*               LISTEN      31163/haproxy
    tcp        0      0 10.0.0.10:8774          0.0.0.0:*               LISTEN      31163/haproxy

The log after the restart

 cat /var/log/nova/nova-api.log
2017-01-16 15:12:57.105 737100 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.106 737042 INFO oslo_service.service [-] Caught SIGTERM, stopping children
2017-01-16 15:12:57.106 737100 INFO nova.metadata.wsgi.server [req-abbafe00-31a0-40fc-8e08-70b2e39d0c8d - - - - -] (737100) wsgi exited, is_accepting=True
2017-01-16 15:12:57.107 737042 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.107 737042 INFO oslo_service.service [-] Waiting on 4 children to exit
2017-01-16 15:12:57.108 737101 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.109 737101 INFO nova.metadata.wsgi.server [req-c1af612f-05c5-4eaf-a63c-cc0f716763cb - - - - -] (737101) wsgi exited, is_accepting=True
2017-01-16 15:12:57.110 737101 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.113 737102 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.114 737102 INFO nova.metadata.wsgi.server [req-1c6d395b-e75b-47cd-9424-effbc54a3a31 - - - - -] (737102) wsgi exited, is_accepting=True
2017-01-16 15:12:57.114 737042 INFO oslo_service.service [-] Child 737100 killed by signal 15
2017-01-16 15:12:57.115 737102 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.115 737103 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.115 737103 INFO nova.metadata.wsgi.server [req-2c077d0d-de7c-440d-a050-7070ca5eb552 - - - - -] (737103) wsgi exited, is_accepting=True
2017-01-16 15:12:57.116 737103 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.122 737042 INFO oslo_service.service [-] Child 737101 exited with status 0
2017-01-16 15:12:57.129 737042 INFO oslo_service.service [-] Child 737102 exited with status 0
2017-01-16 15:12:57.134 737042 INFO oslo_service.service [-] Child 737103 exited with status 0
2017-01-16 15:13:02.454 740449 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
2017-01-16 15:13:02.456 740449 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'
2017-01-16 15:13:02.850 740449 INFO nova.wsgi [-] metadata listening on 172.17.0.10:8775
2017-01-16 15:13:02.851 740449 INFO oslo_service.service [-] Starting 4 workers
2017-01-16 15:13:02.926 740449 WARNING oslo_config.cfg [-] Option "rabbit_hosts" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:02.927 740449 WARNING oslo_config.cfg [-] Option "rabbit_password" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:02.928 740449 WARNING oslo_config.cfg [-] Option "rabbit_userid" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:03.244 740525 INFO nova.metadata.wsgi.server [req-91e0d138-5875-477b-aa1b-643a7c969f5b - - - - -] (740525) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.325 740526 INFO nova.metadata.wsgi.server [req-f3b5059e-2c57-4af3-8ab5-3676dd77661b - - - - -] (740526) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.341 740527 INFO nova.metadata.wsgi.server [req-90024b19-1477-4795-a2ac-419fd6e06a03 - - - - -] (740527) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.420 740528 INFO nova.metadata.wsgi.server [req-b902c893-ea37-4b86-b420-0efb5dd7ad87 - - - - -] (740528) wsgi starting up on http://172.17.0.10:8775

at 8774 there should have been python application listeing that would have been proxied via haproxy.

netstat -tulpn |grep 8774
tcp        0      0 172.17.0.12:8774        0.0.0.0:*               LISTEN      31163/haproxy
tcp        0      0 10.0.0.10:8774          0.0.0.0:*               LISTEN      31163/haproxy

excerpt of nova-api

 [DEFAULT]
use_neutron=True
log_dir=/var/log/nova
notify_api_faults=False
#osapi_compute_listen=overcloud-controller-0.internalapi.localdomain
osapi_compute_listen=172.17.0.10
instance_name_template=instance-%08x
state_path=/var/lib/nova
report_interval=10
enabled_apis=metadata
osapi_compute_listen_port=8774
image_service=nova.image.glance.GlanceImageService
notify_on_state_change=vm_and_task_state
firewall_driver=nova.virt.firewall.NoopFirewallDriver
ram_allocation_ratio=1.0

But the metata url for nova perfectly works fine as shown in the restart log and also via examine the listening port netstat -tulpn |grep 8775 tcp 0 0 172.17.0.10:8775 0.0.0.0:* LISTEN 740449/python2 tcp 0 0 172.17.0.12:8775 0.0.0.0:* LISTEN 31163/haproxy

Why is nova-api not listeing on 8774,even though the process is running

Hi I have deployed the overcloud using tripleo , so far the stack has been created but while validating the installation , i found out that nova-api is not listening in 8774 in the controller,controller, is there any logs or details to dig into to find out what is happening ?

the nova-api process is running fine and is listening on 8775 Here are the details

systemctl restart openstack-nova-api

    [root@overcloud-controller-0 heat-admin]# netstat -tulpn |grep 8774
    tcp        0      0 172.17.0.12:8774        0.0.0.0:*               LISTEN      31163/haproxy
    tcp        0      0 10.0.0.10:8774          0.0.0.0:*               LISTEN      31163/haproxy

The log after the restart

 cat /var/log/nova/nova-api.log
2017-01-16 15:12:57.105 737100 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.106 737042 INFO oslo_service.service [-] Caught SIGTERM, stopping children
2017-01-16 15:12:57.106 737100 INFO nova.metadata.wsgi.server [req-abbafe00-31a0-40fc-8e08-70b2e39d0c8d - - - - -] (737100) wsgi exited, is_accepting=True
2017-01-16 15:12:57.107 737042 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.107 737042 INFO oslo_service.service [-] Waiting on 4 children to exit
2017-01-16 15:12:57.108 737101 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.109 737101 INFO nova.metadata.wsgi.server [req-c1af612f-05c5-4eaf-a63c-cc0f716763cb - - - - -] (737101) wsgi exited, is_accepting=True
2017-01-16 15:12:57.110 737101 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.113 737102 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.114 737102 INFO nova.metadata.wsgi.server [req-1c6d395b-e75b-47cd-9424-effbc54a3a31 - - - - -] (737102) wsgi exited, is_accepting=True
2017-01-16 15:12:57.114 737042 INFO oslo_service.service [-] Child 737100 killed by signal 15
2017-01-16 15:12:57.115 737102 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.115 737103 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.115 737103 INFO nova.metadata.wsgi.server [req-2c077d0d-de7c-440d-a050-7070ca5eb552 - - - - -] (737103) wsgi exited, is_accepting=True
2017-01-16 15:12:57.116 737103 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.122 737042 INFO oslo_service.service [-] Child 737101 exited with status 0
2017-01-16 15:12:57.129 737042 INFO oslo_service.service [-] Child 737102 exited with status 0
2017-01-16 15:12:57.134 737042 INFO oslo_service.service [-] Child 737103 exited with status 0
2017-01-16 15:13:02.454 740449 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
2017-01-16 15:13:02.456 740449 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'
2017-01-16 15:13:02.850 740449 INFO nova.wsgi [-] metadata listening on 172.17.0.10:8775
2017-01-16 15:13:02.851 740449 INFO oslo_service.service [-] Starting 4 workers
2017-01-16 15:13:02.926 740449 WARNING oslo_config.cfg [-] Option "rabbit_hosts" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:02.927 740449 WARNING oslo_config.cfg [-] Option "rabbit_password" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:02.928 740449 WARNING oslo_config.cfg [-] Option "rabbit_userid" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:03.244 740525 INFO nova.metadata.wsgi.server [req-91e0d138-5875-477b-aa1b-643a7c969f5b - - - - -] (740525) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.325 740526 INFO nova.metadata.wsgi.server [req-f3b5059e-2c57-4af3-8ab5-3676dd77661b - - - - -] (740526) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.341 740527 INFO nova.metadata.wsgi.server [req-90024b19-1477-4795-a2ac-419fd6e06a03 - - - - -] (740527) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.420 740528 INFO nova.metadata.wsgi.server [req-b902c893-ea37-4b86-b420-0efb5dd7ad87 - - - - -] (740528) wsgi starting up on http://172.17.0.10:8775

at 8774 there should have been python application listeing that would have been proxied via haproxy.

netstat -tulpn |grep 8774
tcp        0      0 172.17.0.12:8774        0.0.0.0:*               LISTEN      31163/haproxy
tcp        0      0 10.0.0.10:8774          0.0.0.0:*               LISTEN      31163/haproxy

excerpt of nova-api

 [DEFAULT]
use_neutron=True
log_dir=/var/log/nova
notify_api_faults=False
#osapi_compute_listen=overcloud-controller-0.internalapi.localdomain
osapi_compute_listen=172.17.0.10
instance_name_template=instance-%08x
state_path=/var/lib/nova
report_interval=10
enabled_apis=metadata
osapi_compute_listen_port=8774
image_service=nova.image.glance.GlanceImageService
notify_on_state_change=vm_and_task_state
firewall_driver=nova.virt.firewall.NoopFirewallDriver
ram_allocation_ratio=1.0

But the metata url for nova perfectly works fine as shown in the restart log and also via examine the listening port netstat -tulpn |grep 8775 tcp 0 0 172.17.0.10:8775 0.0.0.0:* LISTEN 740449/python2 tcp 0 0 172.17.0.12:8775 0.0.0.0:* LISTEN 31163/haproxy

Why is nova-api not listeing on 8774,even though the process is running

Hi I have deployed the overcloud using tripleo , so far the stack has been created but while validating the installation , i found out that nova-api is not listening in 8774 in the controller, is there any logs or details to dig into to find out what is happening ?

the nova-api process is running fine and meta data part is listening on 8775 Here are the details

systemctl restart openstack-nova-api

    [root@overcloud-controller-0 heat-admin]# netstat -tulpn |grep 8774
    tcp        0      0 172.17.0.12:8774        0.0.0.0:*               LISTEN      31163/haproxy
    tcp        0      0 10.0.0.10:8774          0.0.0.0:*               LISTEN      31163/haproxy

The log after the restart

 cat /var/log/nova/nova-api.log
2017-01-16 15:12:57.105 737100 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.106 737042 INFO oslo_service.service [-] Caught SIGTERM, stopping children
2017-01-16 15:12:57.106 737100 INFO nova.metadata.wsgi.server [req-abbafe00-31a0-40fc-8e08-70b2e39d0c8d - - - - -] (737100) wsgi exited, is_accepting=True
2017-01-16 15:12:57.107 737042 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.107 737042 INFO oslo_service.service [-] Waiting on 4 children to exit
2017-01-16 15:12:57.108 737101 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.109 737101 INFO nova.metadata.wsgi.server [req-c1af612f-05c5-4eaf-a63c-cc0f716763cb - - - - -] (737101) wsgi exited, is_accepting=True
2017-01-16 15:12:57.110 737101 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.113 737102 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.114 737102 INFO nova.metadata.wsgi.server [req-1c6d395b-e75b-47cd-9424-effbc54a3a31 - - - - -] (737102) wsgi exited, is_accepting=True
2017-01-16 15:12:57.114 737042 INFO oslo_service.service [-] Child 737100 killed by signal 15
2017-01-16 15:12:57.115 737102 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.115 737103 INFO nova.wsgi [-] Stopping WSGI server.
2017-01-16 15:12:57.115 737103 INFO nova.metadata.wsgi.server [req-2c077d0d-de7c-440d-a050-7070ca5eb552 - - - - -] (737103) wsgi exited, is_accepting=True
2017-01-16 15:12:57.116 737103 INFO nova.wsgi [-] WSGI server has stopped.
2017-01-16 15:12:57.122 737042 INFO oslo_service.service [-] Child 737101 exited with status 0
2017-01-16 15:12:57.129 737042 INFO oslo_service.service [-] Child 737102 exited with status 0
2017-01-16 15:12:57.134 737042 INFO oslo_service.service [-] Child 737103 exited with status 0
2017-01-16 15:13:02.454 740449 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
2017-01-16 15:13:02.456 740449 INFO nova.network.driver [-] Loading network driver 'nova.network.linux_net'
2017-01-16 15:13:02.850 740449 INFO nova.wsgi [-] metadata listening on 172.17.0.10:8775
2017-01-16 15:13:02.851 740449 INFO oslo_service.service [-] Starting 4 workers
2017-01-16 15:13:02.926 740449 WARNING oslo_config.cfg [-] Option "rabbit_hosts" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:02.927 740449 WARNING oslo_config.cfg [-] Option "rabbit_password" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:02.928 740449 WARNING oslo_config.cfg [-] Option "rabbit_userid" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2017-01-16 15:13:03.244 740525 INFO nova.metadata.wsgi.server [req-91e0d138-5875-477b-aa1b-643a7c969f5b - - - - -] (740525) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.325 740526 INFO nova.metadata.wsgi.server [req-f3b5059e-2c57-4af3-8ab5-3676dd77661b - - - - -] (740526) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.341 740527 INFO nova.metadata.wsgi.server [req-90024b19-1477-4795-a2ac-419fd6e06a03 - - - - -] (740527) wsgi starting up on http://172.17.0.10:8775
2017-01-16 15:13:03.420 740528 INFO nova.metadata.wsgi.server [req-b902c893-ea37-4b86-b420-0efb5dd7ad87 - - - - -] (740528) wsgi starting up on http://172.17.0.10:8775

at 8774 there should have been python application listeing that would have been proxied via haproxy.

netstat -tulpn |grep 8774
tcp        0      0 172.17.0.12:8774        0.0.0.0:*               LISTEN      31163/haproxy
tcp        0      0 10.0.0.10:8774          0.0.0.0:*               LISTEN      31163/haproxy

netstat -tulpn |grep 8775
tcp        0      0 172.17.0.12:8775        0.0.0.0:*               LISTEN      301753/haproxy
tcp        0      0 172.17.0.10:8775        0.0.0.0:*               LISTEN      300881/python2

excerpt of nova-api

 [DEFAULT]
use_neutron=True
log_dir=/var/log/nova
notify_api_faults=False
#osapi_compute_listen=overcloud-controller-0.internalapi.localdomain
osapi_compute_listen=172.17.0.10
instance_name_template=instance-%08x
state_path=/var/lib/nova
report_interval=10
enabled_apis=metadata
osapi_compute_listen_port=8774
image_service=nova.image.glance.GlanceImageService
notify_on_state_change=vm_and_task_state
firewall_driver=nova.virt.firewall.NoopFirewallDriver
ram_allocation_ratio=1.0

But the metata url for nova perfectly works fine as shown in the restart log and also via examine the listening port netstat -tulpn |grep 8775 tcp 0 0 172.17.0.10:8775 0.0.0.0:* LISTEN 740449/python2 tcp 0 0 172.17.0.12:8775 0.0.0.0:* LISTEN 31163/haproxy