Article ID: 116985, created on Aug 28, 2013, last review on May 11, 2014

  • Applies to:
  • Plesk 11.5 for Linux
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

A container stays mounted after rebooting from PVA Power Panel or after using reboot from the container.

Cause

The link to "vzreboot" does not have the proper priority.

The problem is triggered by using the command chkconfig --add ... (included in the post-install script of any package with a network-related service).

As a result, the priority of "vzreboot" is changed from 00 to 50.

    ~# ll /vz/private/19150/fs/root/etc/rc.d/rc6.d/ |grep reboot
    -rwxrwxrwt 1 root root 84 Aug 20  2012 S01reboot
    lrwxrwxrwx 1 root root 18 Aug 10 12:14 S50vzreboot -> ../init.d/vzreboot

Resolution

To fix it manually, add the line # chkconfig: 6 00 to the script:

    ~# cat /vz/root/622/etc/init.d/vzreboot
    #!/bin/bash
    # chkconfig: 6 00
    ### BEGIN INIT INFO
    # Provides: vzreboot
    # Required-Start:
    # Required-Stop:
    # Default-Start:
    # Default-Stop: 6
    # Description: Creates  Parallels Virtuozzo Containers reboot mark
    ### END INIT INFO

Search Words

reboot

vzreboot

power panel

container stays mounted

container reboot

vps mounted

Virtuozzo: mounted after reboot

Container stay mounted after reboot

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF