Comment 1 for bug 1673657

Revision history for this message
MarginHu (margin2017) wrote :

I enter into the container, and found it is "sleep 1"

()[root@kode1 /]# ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
swift 1 0.0 0.0 192 4 ? Ss+ 15:07 0:00 /usr/local/bin/dumb-init /bin/bash /usr/local/
swift 7 0.0 0.0 11632 1404 ? Ss 15:07 0:00 /bin/bash /usr/local/bin/kolla_start
root 1012 0.1 0.0 15200 2016 ? S 15:24 0:00 -bash
swift 1048 0.0 0.0 4308 344 ? S 15:24 0:00 sleep 1
root 1049 0.0 0.0 50872 1828 ? R+ 15:24 0:00 ps aux
()[root@kode1 /]# ls
anaconda-post.log dev home lib64 media opt root sbin sys usr
bin etc lib lost+found mnt proc run srv tmp var
()[root@kode1 /]#

()[root@kode1 /]# cat /usr/local/bin/kolla_start
#!/usr/local/bin/dumb-init /bin/bash
set -o errexit

# Wait for the log socket
if [[ ! "${!SKIP_LOG_SETUP[@]}" && -e /var/lib/kolla/heka ]]; then
    while [[ ! -S /var/lib/kolla/heka/log ]]; do
        sleep 1
    done
fi
....

but I found other swift process works well, why? it seems that root cause is located in heka.