• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

CentOS: "Quota not supported" Warning while updating to plesk 10.0.1

AdrianC

Basic Pleskian
On CentOS while trying to update plesk from (from 9.x I think) to 10.0.1 I got these errors in the log:

===> Installing Quotas
Trying to change quota limits... done
Run quotacheck. This may take some time.
Trying to check for quota support... Quota is not supported by your operating system.
Probably kernel has not compiled in quota support.

WARNING!
During the check for quota support found some problems(see log file: /tmp/pp10.9.0-bootstrapper.110108.06.59.log)

Continue...
ANd at the end of the install screen I got:
WARNING: Some problems occured during upgrade. You need to check log file at ...
- Update was completed but should I worry about it?
- Second question: server uses around 500 (of 2000) MB of ram right after restart, without any domain active or anything, empty server after attempting to do these updates.
 
>Update was completed but should I worry about it?
Don't worry, it just diagnostic message (not OS depended). Appears just if quota support on FS is not configured.
By the way, U get same message in log of clean panel installation (if it was saved).

>Second question:
Need to provide more information for problem localization. Which process are more greedy. Possible system maintenance scripts?
Also do not forget about mail services (such as antiviruses, spamfilters), tomcat support.
 
Thanks for the tips.
I later did a server reinstall (server was empty anyway) I got same errors but the ram usage is somehow normal, I think previous setup used too much ram because I had many recent updates that probably had things to finish.

I updated it to latest 9.x version, 10.x seems to have issues, but I liked the "server health" feature of the 10.x panel.
 
Back
Top