yahoo-eng-team team mailing list archive

[Stephen Finucane <stephen.finucane@xxxxxxxxx>]

As with neutron and keystone, nova is also using oslo.log > 1.3.0 so I
think this is no longer an issue
https://github.com/openstack/nova/blob/a35bd3/requirements.txt#L41

** Changed in: nova
       Status: Confirmed => Fix Released

** Summary changed:

- nova syslog logging to /dev/log race condition in python 2.6 and 2.7
+ nova syslog logging to /dev/log race condition

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

Title:
  nova syslog logging to /dev/log race condition

Status in Glance:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.log:
  Fix Released

Bug description:
  
  running nova-api-ec2
  running rsyslog

  service rsyslog restart ; service nova-api-ec2 restart

  nova-api-ec2 consumes up to 100% of the available CPU (or at least a
  full core) and s not responsive.  /var/log/nova/nova-api-ec2.lgo
  states the socket is already in use.

  strace the process

  sendto(3, "<142>2013-01-18 20:00:22 24882 INFO nova.service [-] Caught
  SIGTERM, exiting\0", 77, 0, NULL, 0) = -1 ENOTCONN (Transport endpoint
  is not connected)

  service nova-api-ec2 restart fails as upstart already thinks the
  process has been terminated.

  The only way to recover is to pkill -9 nova-api-ec2 and then restart
  it with 'service nova-api-ec2 restart'.

  The same behavior has been seen in all nova-api services.

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