Skip to main content

Quota Errors on Attempt to Modify Account after 58 Upgrade

Comments

36 comments

  • Zurrie
    Hello, To update, the resolution associated with CPANEL-7896 is included with cPanel 58.0.19: Fixed case CPANEL-7896: Add fallback to reading /etc/fstab if /dev/root is a broken symlink. This version is currently published to the "Edge" and "Current" build tiers, and is expected to make it's way to the "Release" build tier in the next couple of days. You can review the full change log, information on updating cPanel/WHM, and information on the build/release process at:
    0
  • cPanelMichael
    the server root space seems increase, do you know why? Filesystem Size Used Avail Use% Mounted on /dev/sda 95G 72G 23G 77% / Filesystem Size Used Avail Use% Mounted on /dev/root 20G 10G 8.2G 56% /

    Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • sehh
    Hello, I have a server running 11.58.0.25 (virtuozzo VPS), which won't create any new accounts, producing a similar error to the OP's post. I tried running fixquotas, which produced the following errors:
    Installing Default Quota Databases......Done journaled quota support: not available with vzaquota (disabled) checking out /backup checking out /backup Quotas have been enabled and updated. Reading package super_client Resetting quota for superdomain to 0 M edquota: Quota write failed (id 510): Invalid argument ...
    There is no /dev/root but even if I create one, it makes no difference, I see the same errors as above when I re-run fixquotas. My fstab looks like this:
    # cat /etc/fstab none /dev/pts devpts rw 0 0
    df output:
    # df -h Filesystem Size Used Avail Use% Mounted on /dev/simfs 160G 9.7G 151G 7% / none 7.8G 4.0K 7.8G 1% /dev
    mount output:
    # mount|grep quota /dev/simfs on / type simfs (rw,relatime,usrquota,grpquota)
    I'd appreciate some help please.
    0
  • sehh
    errmm.. not sure what to say, the problem was fixed once I rebooted the VPS... weird. sorry for the false alarm.
    0
  • cPanelMichael
    not sure what to say, the problem was fixed once I rebooted the VPS... weird.

    I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.
    0
  • Hargreaves Standa
    All the above solutions didn't work for me but restarting cpanel service via shell using the script below did! /usr/local/cpanel/scripts/restartsrv_*
    0

Please sign in to leave a comment.