Blog
  • Welcome to egonzalez blog
  • Software Supply Chain Security
    • Software Supply Chain Security: Why It Matters
    • Software Supply Chain Security: A Technical Deep Dive
    • SLSA and the Software Supply Chain Security: Time to Get Serious
  • Provenance
    • Understanding Provenance in Software Supply Chain Security
  • Building a secure development framework
  • Hacking
    • Index
      • Hack the box writeups
        • Dyplesher HTB writeup
        • Fatty HTB writeup
        • Oouch HTB writeup
        • Sauna HTB writeup
      • Python Vulnerabilities
        • Data Deserialization
          • Pickle
          • XML
          • YAML
      • Hacking cheatsheet
  • DevSecOps
    • Index
      • Gitlab CI minikube development environment
      • Gerrit review minikube
      • Gerrit and gitlab replication and CI job hooks on k8s
      • Vault integration with Gitlab CI
      • Gitlab CI template for DefectDojo
      • Falco real time runtime thread detection on k8s
      • Zarf - Airgap deployment in kubernetes
      • OWASP Dependency-track
      • OpenDaylight in a Docker
      • To conditional or to skip, that's the Ansible question
      • Spacewalk Red Hat Satellite v5 in a Docker container PoC
      • Ansible INI file module
  • OpenStack
    • Index
      • OpenStack tacker and service function chaining sfc with kolla
      • Deploy OpenStack designate with kolla-ansible
      • OpenStack keystone zero downtime upgrade process newton to ocata
      • Midonet integration with OpenStack Mitaka
      • OpenStack kolla deployment
      • Magnum in RDO OpenStack Liberty
      • Nova VNC flows under the hood
      • Ceph Ansible baremetal deployment
      • Rally OpenStack benchmarking with Docker
      • OpenStack affinity/anti-affinity groups
      • Migrate keystone v2.0 to keystone v3 OpenStack
      • Neutron DVR OpenStack Liberty
      • OpenStack segregation with availability zones and host aggregates
      • Nova Docker driver
      • Murano in RDO OpenStack manual installation
      • Ceph RadosGW admin Ops
      • Multiple store locations for glance images
      • List all tenants belonging an user
      • Load balancer as a service OpenStack LbaaS
      • OpenStack nova API start error
      • Delete OpenStack neutron networks
Powered by GitBook
On this page

Was this helpful?

  1. OpenStack
  2. Index

OpenStack nova API start error

Could not bind to 0.0.0.0 address all ready in use

OpenStack-nova-api doesn't start, this error is from the services boot priority in many times.

   $ service openstack-nova-api start

   2015-03-03 15:05:06.402 3313 ERROR nova.wsgi [-] Could not bind to 0.0.0.0:8775
   2015-03-03 15:05:06.402 3313 CRITICAL nova [-] error: [Errno 98] Address already in use

   $ service openstack-nova-api status

   openstack-nova-api dead but pid file exists\*

This Error happens because openstack-nova-api and openstack-nova-metadata-api use the same ports. You can start nova-api stopping metadata-api service and starting nova-api before, then start again metadata-api service.

$ service openstack-nova-metadata-api stop
$ service openstack-nova-api start
$ service openstack-nova-metadata-api

This should fix your issue. After this you can set up boot order to this processes

update-rc.d openstack-nova-api defaults [order]

Example:

If openstack-nova-metadata-api got an order boot of S90 openstack-nova-metadata-api, you should use update-rc to set nova-api start before nova-metadata-api

update-rc.d openstack-nova-api defaults 90

This will set the priority of nova-api with the priority of nova-metadata-api, wich means that nova-api will run before metadata-api.

PreviousLoad balancer as a service OpenStack LbaaSNextDelete OpenStack neutron networks

Last updated 5 years ago

Was this helpful?