← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1484836] Re: apache failed to restart with keystone wsgi app

 

Stop Keystone service and start apache2 so make sure keystone works on
top of apache.

no two services can work with same port , as keystone is already running
on 35357 and 5000 ports, apache2 cannot run on the same ports.

All the commands will work.

** Changed in: keystone
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1484836

Title:
  apache failed to restart with keystone wsgi app

Status in Keystone:
  Invalid

Bug description:
  From time to time apache failed to restart with init script when
  keystone wsgi application is running.

  There is steps how to reproduce it:

  launch apache start/stop in cycle
  while :; do service apache2 stop; service apache2 start; done

  after sime time apache failed to start, because it can't bind to opened socket:
   * Starting web server apache2
   *
   * Stopping web server apache2
   *
   * Starting web server apache2
   *
   * Stopping web server apache2
   *
   * Starting web server apache2
  (98)Address already in use: AH00072: make_sock: could not bind to address [::]:35357
  (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:35357
  no listening sockets available, shutting down
  AH00015: Unable to open logs
  Action 'start' failed.
  The Apache error log may have more information.
   *
   * The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
   * Stopping web server apache2
   *
   * Starting web server apache2
   *
   * Stopping web server apache2

  Without keystone wsgi application, I can't reproduce error in 12
  hours. horizon and radosgw wsgi were enabled.

  It look like root cause is in keystone wsgi application itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1484836/+subscriptions


References