Website diskquota pulling data from wrong server

Discussion in 'General' started by inviso, Sep 18, 2023.

  1. inviso

    inviso New Member

    We've inherited a couple of ISPConfig 3 servers when we acquired a company.
    We've realized that the website diskquota is pulling the data from the wrong server.
    We have 3 servers setup. www1, www2 and www3.
    www1 is the primary server, it's running the ISPConfig control panel, websites, e-mail and DNS.
    www2 is only used for DNS
    www3 is a secondary web/mailserver that does not run DNS.

    When looking at either the website quota on the "home"-page or through "Sites -> Website harddisk quota" the quota reported does not correspond with the actual quota set on the account in a lot of cases. This seem to be the case for all websites that are using www1 for web. If they are using www3 for webb, the quota is correct, same goes if they are recently added, it pulls the data from www1.
    In the rest of the cases, the quota is pulled from the www2 machine that is only used for DNS. I've managed to confirm this by logging onto the www2-server by SSH and update the quota on an account manually through Linux.

    The data that's being stored in the dbispconfig database in the table monitor_data and the tuples with the type "harddisk_quota" and if I'd remove the data from the tuple corresponding to the www2-server, all data in the control panel is correct, but ISPConfig automatically refills the tuple again and the graphical data on the frontend is incorrect once again.

    Hopefully someone here are able to help us figure this out, how to solve or workaround this issue.

    Best Regards
    Robert Larsson
    Inviso Webbhotell
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Hard to say what caused this, must be that something has be set up incorrectly. If you are unfamiliar with ISPConfig, it might be best to hire someone to support you.
  3. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Since you inherited them, they might be just old, or badly setup / maintained like @Th0m said, so first, before anything else, try to make a full working backup.

    Then update them all accordingly, first ISPConfig from slave to master, then the OS, then use the relevant ISPConfig Perfect Tutorials to guide you with checking and installing necessary packages, and finally run ISPConfig update again (use force) to reconfigure services.

    Alternatively, consider doing migration and using ISPConfig migration tools.

    Also consider hiring helps as suggested by @Th0m as another alternative.
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I would do that, to get a correctly set up ISPConfig system that then can be maintained with the usual methods. If the previous maintainer has not left notes and documentation on what has been done to the current system it is going to be full of suprises.
    But like already suggested, make a backup first so you can go back to a "working" system if something breaks.
    ahrasis likes this.
  5. inviso

    inviso New Member

    We took over the systems about 2 years ago and been working with it since. I'd say while not experts, we sure are fairly familiar with the system.
    The servers are setup using the "Perfect server guide" here on the howtoforge website.

    The system is not a faulty setup, and I would appreciate if you would try to help us figure out this very specific bug in the system instead of telling us to reinstall. The demeaning manner of all these answers is very unfortunate.

    All the systems are running the latest versions of ISPConfig, and this has been an issue for a long time, just hasn't been dug into before, considering it's just a graphical issue.
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Which ISPConfig version do you use? Are the servers www2 and www3 set to be a mirror of www1? Has the issue started just recently, or has it persisted since you set this up?

    Or you might want to contact business support and have them take a look at your system directly:
  7. inviso

    inviso New Member

    We're running ISPConfig Version: 3.2.9p1 at the moment. The issue has persisted since at least version 3.2.3, but considering the nature of the issue just being graphical, probably longer than that.

    The www2-server is a mirror of www1. www3 is not.
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Please post the result of this commands from www2 server:

    ls /usr/local/ispconfig/server/mods-enabled/
    ls /usr/local/ispconfig/server/plugins-enabled/

    and does the command:

    repquota -avu | grep web

    when run on www2 returns quotas for web* users.
  9. inviso

    inviso New Member

    www2~# ls /usr/local/ispconfig/server/mods-enabled/

    www2~# ls /usr/local/ispconfig/server/plugins-enabled/ empty.dir

    When running the repquota command we do get data of webquotas for users.
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    The problem with your setup is that you try to do a partial service mirroring, which ISPConfig does not support. When you enable mirroring for a server, all services get mirrored, not just DNS as you try to do it. That's why you can see in ISPConfig multiserver install guides that every time mirroring is used, the mirror runs the same services. so if you have a ns1 /ns2 mirror pair, then ns1 runs just DNS and ns2 runs also just dns.

    As your system is set up this way now, you can try to fix it by disabling harddisk quota on the www2 system, so repquota does not return any quotas anymore.
    ahrasis likes this.
  11. inviso

    inviso New Member

    Seem to have worked to disable the quota on the www2 system. The data is still reported and the tuple in the database is updated, but it contains no data for the website and thus use the data from the www1 system.
  12. remkoh

    remkoh Active Member

    Since www2 is just dns, why not disable mirroring www1 and create a slave zone on www2 in ispconfig?

    I never understood why people would mirror a dns in ispconfig.
    Just create a master and proper slave zone, like dns is supposed to function.
    ahrasis likes this.
  13. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Secondary zone support was not in ISPConfig originally, it appeared about the time when DNSSEC became popular. So old ISPConfig setups mirrored DNS servers.
    remkoh likes this.
  14. nhybgtvfr

    nhybgtvfr Well-Known Member HowtoForge Supporter

    also, if the servers are running exactly the same services and dnssec is not needed, mirroring is just simply a damn sight easier.

Share This Page