Hi, I've set up a CentOS 7 container and installed Plesk 12.5 after that. My versions are: - OpenVZ kernel: 2.6.32-042stab112.15 - VZQuota: vzquota-3.1-1.x86_64 While starting to set up the system (I didn't actually configure Plesk yet - only MySQL), I've noticed that VZQuota is not working. I'm getting the following: [root@server /]# systemctl status vzquota vzquota.service - LSB: Start vzquota at the end of boot Loaded: loaded (/etc/rc.d/init.d/vzquota) Active: failed (Result: exit-code) since Tue 2015-11-03 22:33:22 CET; 36min ago Process: 100 ExecStart=/etc/rc.d/init.d/vzquota start (code=exited, status=2) Nov 03 22:33:22 server systemd[1]: Starting LSB: Start vzquota at the end of boot... Nov 03 22:33:22 server vzquota[100]: quotaon: using //aquota.group on /dev/simfs [/]: Device or resource busy Nov 03 22:33:22 server vzquota[100]: quotaon: using //aquota.user on /dev/simfs [/]: Device or resource busy Nov 03 22:33:22 server systemd[1]: vzquota.service: control process exited, code=exited status=2 Nov 03 22:33:22 server systemd[1]: Failed to start LSB: Start vzquota at the end of boot. Nov 03 22:33:22 server systemd[1]: Unit vzquota.service entered failed state. Some googling showed, that the problems seem to occur because of systemd. How can I solve this problem? Thanks in advance! boindil
Maybe you can try create a systemd startup script for vzquota that starts it after that process it is having trouble accessing. Creating systemd scripts are very simple compared to init.d scripts. Try systemd-anaylyze blame to see what is happening during the startup sequence and when vzquote is trying to start. With a systemd startup script you can change the order of when vzquota starts. Try move it down to the end. Maybe after rsyslog starts. It's very easy to do that in systemd scripts.