Databases side tab missing after 3.2 upgrade

Discussion in 'Installation/Configuration' started by georgemastro, Oct 19, 2020.

  1. georgemastro

    georgemastro New Member

    Hey all!

    Just updated to ISPConfig 3.2 and the side tab databases is missing under "Sites"!
    Image 2020-10-19 at 12.00.45.png
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Weird, I can see it on all of my systems. Do you have databases enabled for one of your servers? And does your logged in account have rights to create a database?
     
  3. georgemastro

    georgemastro New Member

    Yes, this server is running with 20 or more websites for over 3 years. The logged in account is the admin. I also did a complete server reboot, but nothing changed.
     
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Did you check that DB is enabled?

    Can you share the content of /usr/local/ispconfig/interface/web/sites/lib/module.conf.php?

    Try updating again:
    Code:
    cd /tmp
    wget https://www.ispconfig.org/downloads/ISPConfig-3.2.tar.gz
    tar xvfz ISPConfig-3.2.tar.gz
    cd ispconfig3_install/install
    php -q update.php
     
  5. georgemastro

    georgemastro New Member

    Sure! Attached.

    Also, when updating with the way you mentioned, I get this:
    PHP Warning: Packets out of order. Expected 1 received 0. Packet size=30 in /tmp/ispconfig3_install/install/lib/mysql.lib.php on line 207
     

    Attached Files:

  6. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Is the ISPConfig database on the same server as the panel?

    The file seems fine... you could try going to System -> Server Services -> server1.example.com and disable DB-Server there, save, then re-enable it again.
     
  7. georgemastro

    georgemastro New Member

    The above fixed the problem. Everything is back to normal after disabling/enabling this.

    Thanks!
     
  8. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Perfect, I think that was not stored correctly in the database then :)

    No problem.
     

Share This Page