init-logger chewing CPU

peter

Member
Nov 25, 2008
31
0
6
On the following proxmox server:

Code:
# pveversion -v
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.18-1-pve
proxmox-ve-2.6.18: 1.5-3
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-1-pve: 2.6.18-3
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve4
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-3

I've two Centos 5 servers. On one of them init-logger is chewing 99% of the CPU

Code:
top - 08:40:42 up  1:35,  0 users,  load average: 1.13, 1.03, 0.92
Tasks:  20 total,   3 running,  17 sleeping,   0 stopped,   0 zombie
Cpu(s): 20.3%us, 79.7%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   1048576k total,    69308k used,   979268k free,        0k buffers
Swap:        0k total,        0k used,        0k free,        0k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 7405 root      25   0    92   16    4 R 99.6  0.0  95:30.80 init-logger
    1 root      15   0  2068  644  556 S  0.0  0.1   0:00.12 init



I can find very little information about what init-logger does, but I assume all it does is log any init messages.

Running strace on the process reveals:

Code:
Process 7405 attached - interrupt to quit
restart_syscall(<... resuming interrupted call ...>) = 0
setuid(0)                               = 1
restart_syscall(<... resuming interrupted call ...>) = 0
setuid(0)                               = 1
restart_syscall(<... resuming interrupted call ...>) = 0
setuid(0)                               = 1
restart_syscall(<... resuming interrupted call ...>) = 0

I'm not really sure if this is a openvz issue or a Centos issue or both.