Use of dbispconfig_serv1 instead dbispconfig (default)

Discussion in 'Installation/Configuration' started by francoisPE, Jan 14, 2021.

  1. francoisPE

    francoisPE Active Member HowtoForge Supporter

    Hello
    I run ispconfig on 2 servers with ubuntu 20.04, setup following perfect server tuto...
    In order to differentiate db on my server I use dbispconfig_serv1 on my web ispconfig server.
    Not sure it works.
    When running php -q update.sh with rewrite permission=yes, I face this message:
    "
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE(`status`, `error`) ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE(`status`) ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE(`updated`) ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE (`ssl`, `ssl_letsencrypt`, `ssl_request`, `ssl_cert`, `ssl_action`, `ssl_key`) ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE (`action_state`, `response`) ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT , DELETE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT, UPDATE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT, UPDATE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE, DELETE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, DELETE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT, DELETE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT, DELETE ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, UPDATE(`dnssec_initialized`, `dnssec_info`, `dnssec_last_signed`) ON ?? TO ?@?
    Error:
    WARNING: Unable to set rights of user in master database: dbispconfig
    Query: GRANT SELECT, INSERT, UPDATE ON ?? TO ?@?
    Error:
    "
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    So this is on a slave server?

    The permissions rewrite should only be done on the master.
     
  3. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    The database is differentiated by what server you are connected to, there is no need to name them differently (unless you're doing a master-master cluster setup, which is not what you indicated).
     
  4. francoisPE

    francoisPE Active Member HowtoForge Supporter

    It happens on master, not slave.
    I have a script for install. It was simplier to script for name 'dbispconfig_$server_name' whatever the case : slave or master...
    I understand that dbispconfig is "a must" for master (mariadb+web interface) server.
    I still use 'dbispconfig_$server_name' for others set up in case I decide to switch them to slave later on...
     

Share This Page