Article ID: 121515, created on May 9, 2014, last review on May 10, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7

Symptoms

Reboot process gets stuck on stopping pvaagentd service:

[root@linvz1 ~]# ps fax | tail
54576 ?        S      0:00  \_ sfcbd -d
54578 ?        S      0:00  \_ sfcbd -d
54579 ?        S      0:00  \_ sfcbd -d
54781 ?        S      0:00  \_ sfcbd -d
54786 ?        S      0:00  \_ sfcbd -d
54798 ?        S      0:00  \_ sfcbd -d
55987 ?        Ssl    0:59 automount --pid-file /var/run/autofs.pid
37801 ?        S      0:27 /sbin/plymouthd --mode=shutdown
37808 ?        Ss     0:00 /bin/bash /etc/rc.d/rc 6
37953 ?        S      0:35  \_ /bin/sh /etc/rc6.d/K17pvaagentd stop
[root@linvz1 ~]#

Cause

PVA Agent might get stuck on stopping state if there are processes in D-state. E.g.:

[root@linvz1 ~]# ps aux | grep pva | grep -v pvamn
root      6147  0.0  0.0 471152   224 ?        D    Feb21   0:00 /opt/pva/agent/bin/vzlpl /var/opt/pva/agent/tmp.TqHUZ8
root     37953  1.1  0.6 109760 101384 ?       S    14:45   0:43 /bin/sh /etc/rc6.d/K17pvaagentd stop
root     50122  0.0  0.0 139892  6252 ?        Ss   Feb26   8:50                           -f /etc/opt/pva/cc/pvacc.conf
root     51561  0.0  0.0 320812  3600 ?        D    Feb26   0:00 pvaagent [backup_reloader]    //opt/pva/agent/bin/pva.conf
root     51743  0.0  0.0 151096  3896 ?        Ss   Feb26   0:35                           -f /etc/opt/pva/pp/pvapp.conf
root     51754  0.0  0.0 224552  4616 ?        S    Feb26   0:16 pvaagent [servconn]        -f /etc/opt/pva/pp/pvapp.conf
root     51755  0.0  0.0 149468  4552 ?        S    Feb26   0:54 pvaagent [vzcpenvcache]    -f /etc/opt/pva/pp/pvapp.conf
root     51756  0.0  0.0 148724  3272 ?        S    Feb26   0:00 pvaagent [vzcproxy]        -f /etc/opt/pva/pp/pvapp.conf
root     51757  0.0  0.0 148700  3584 ?        S    Feb26   0:47 pvaagent [vzcpwatcher]     -f /etc/opt/pva/pp/pvapp.conf
[root@linvz1 ~]#

Processes 51561 and 6147 are in D state. Process in D state cannot be terminated unless it changes its state to S (sleeping) - it's not interruptible until then.

Resolution

Since there are non-interruptible processes present there will be no way to stop pvaagent gracefully. The only option is to perform hard-reset.

It's recommended to prepare the host to the reset to make sure there will be no data loss. Follow next steps to minimize the impact from the reset:

  1. Stop all containers via vzctl:

    # vzlist -Ho ctid | while read ctid; do vzctl stop $ctid;done
    
  2. After stopping the containers sync file system to make sure there are no unfinished transactions:

    # echo S > /proc/sysrq-trigger
    
  3. Once filesystem is synced - perform the reset via SysRQ (alternatively you can do it using power-cycle manually or via iLO/KVM/iDRAC):

    # echo b > /proc/sysrq-trigger
    

Search Words

system wont reboot

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF