controller node hangs with zombie process

Bug #1425228 reported by Leontii Istomin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
High
Pavel Boldin

Bug Description

[root@fuel ~]# fuel --fuel-version
api: '1.0'
astute_sha: f7cda2171b0b677dfaeb59693d980a2d3ee4c3e0
auth_required: true
build_id: 2015-02-07_20-50-01
build_number: '76'
feature_groups:
- mirantis
fuellib_sha: 64f3ebe9fcbd18bf6c80a948e06061783a090347
fuelmain_sha: c799e3a6d88289e58db764a6be7910aab7da3149
nailgun_sha: 2ef819732a3ee7acf7b610e7d1c1a6da0434c1a0
ostf_sha: 3b57985d4d2155510894a1f6d03b478b201f7780
production: docker
release: 6.0.1
release_versions:
  2014.2-6.0.1:
    VERSION:
      api: '1.0'
      astute_sha: f7cda2171b0b677dfaeb59693d980a2d3ee4c3e0
      build_id: 2015-02-07_20-50-01
      build_number: '76'
      feature_groups:
      - mirantis
      fuellib_sha: 64f3ebe9fcbd18bf6c80a948e06061783a090347
      fuelmain_sha: c799e3a6d88289e58db764a6be7910aab7da3149
      nailgun_sha: 2ef819732a3ee7acf7b610e7d1c1a6da0434c1a0
      ostf_sha: 3b57985d4d2155510894a1f6d03b478b201f7780
      production: docker
      release: 6.0.1

Baremetal,Ubuntu, HA, Neutron-gre,Ceilometer,Sahara,Ceph-all, Debug, nova-quotas,6.0.1_76
Controllers:3 Computes:96

deployment was successfull, but during rally tests controller node was hunged.
I couldn't perform any bash command:
ls -la
-bash: fork: Cannot allocate memory
I couldn't open nw ssh connection. I couldn't reach bash of the node even ipmi.
Beheviour very similar with https://bugs.launchpad.net/fuel/+bug/1422186, but disks are ok.

from atop dump I can see that at 2015/02/21 10:44:01 we had zombie process, but I can't detect the process.
Also tslpi grows from Feb 21 10:43
Keystone and most of logs stopped at 10:43.

atop is here https://drive.google.com/a/mirantis.com/file/d/0Bx4ptZV1Jt7hNnNaVDg0ZkgwYkk/view?usp=sharing
I'll upload DG asap

Tags: scale
no longer affects: fuel
Changed in mos:
assignee: nobody → Pavel Boldin (pboldin)
Revision history for this message
Leontii Istomin (listomin) wrote :
Revision history for this message
Michael Semenov (msemenov) wrote :
Changed in mos:
importance: Undecided → High
status: New → Won't Fix
milestone: none → 6.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.