• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Problems with starting my plesk Container / vzquota

Mrilabs

New Pleskian
---------------------------------------------------------------
Plesk / Virtuozzo, 10.4.4, Ubuntu 10.4 LTS, x86_64 GNU/Linux

Hey Guys, I have since today problems to start my plesk Container. My Virtuozzo shows me following Error:

Operation start with the Env(s) "SERVER" is finished with errors: Error invoking external utility: vzctl start 36574 failed: Validate Container: Starting Container ... Running command: /usr/sbin/vzquota show 36574 -p /vz/private/36574/fs Running command: /usr/sbin/vzquota on 36574 -s 1 -u 500 -R -p /vz/private/36574/fs -b 26214500 -B 27263076 -i 4721410 -I 4999140 -e 259000 -n 259000 Mounting root: /vz/template:/vz/private/36574/fs /vz/root/36574 Container is mounted running: /usr/sbin/vzpkg info -q ubuntu-10.04-x86_64 osrelease Setup slm memory limit Setup slm subgroup (default) init 00000018 -1 9 httpd 0000001c -1 2 httpsd 0000001c -1 2 lighthttpd 0000001c -1 2 mysqld 0000001c -1 3 syslogd 00000018 0 8 sshd 00000018 0 8 inetd 00000018 0 8 xinetd 00000018 0 8 cron 00000018 0 8 crond 00000018 0 8 00000004 9 0 ....

Complete Boot-Message: https://gist.github.com/f7c5b37ed8b0a96f19da

Task i've done bevore: A Plesk minor-update on Sunday, a user reported today that he's got a 'Disk quota exceeded' on his account. I've changed his webspace limits from 2 to 4 gb. This change has had no effects, so i've tried to reboot the server with the effect that he's not booting again. There is 60% Disk space free(!!), so there's no problem with a full disc. I could access the Server with a repair system. I have no own or special Scripts on this Server.

So has anyone of you some suggestions how I could fix this problem? *hrm*
 
Maybe there is lack of free inodes but not free disk space? Did you check it?
 
Back
Top