I have been using ispconfig 3 for years. I have upgraded to 3.2.p1. I have a number of issues: I ran it in Centos-7 for years. I have now migrated to Red Hat 8.5 1) I have deleted several websites and they no longer appear on the ispconfig websites screen. They keep popping up in the /etc/httpd/conf/sites-enabled and /etc/httpd/conf/sites-available/ directories. So to make a domain go away and not come back, what table in dbispconfig do I delete the data from: MariaDB [(none)]> use dbispconfig Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [dbispconfig]> show tables; +--------------------------+ | Tables_in_dbispconfig | +--------------------------+ | aps_instances | | aps_instances_settings | | aps_packages | | aps_settings | | attempts_login | | client | | client_circle | | client_message_template | | client_template | | client_template_assigned | | country | | cron | | directive_snippets | | dns_rr | | dns_slave | | dns_soa | | dns_ssl_ca | | dns_template | | domain | | firewall | | ftp_traffic | | ftp_user | | help_faq | | help_faq_sections | | iptables | | mail_access | | mail_backup | | mail_content_filter | | mail_domain | | mail_forwarding | | mail_get | | mail_mailinglist | | mail_relay_domain | | mail_relay_recipient | | mail_traffic | | mail_transport | | mail_user | | mail_user_filter | | monitor_data | | openvz_ip | | openvz_ostemplate | | openvz_template | | openvz_traffic | | openvz_vm | | remote_session | | remote_user | | server | | server_ip | | server_ip_map | | server_php | | shell_user | | spamfilter_policy | | spamfilter_users | | spamfilter_wblist | | support_message | | sys_config | | sys_cron | | sys_datalog | | sys_dbsync | | sys_filesync | | sys_group | | sys_ini | | sys_log | | sys_remoteaction | | sys_session | | sys_theme | | sys_user | | web_backup | | web_database | | web_database_user | | web_domain | | web_folder | | web_folder_user | | web_traffic | | webdav_user | | xmpp_domain | | xmpp_user | +--------------------------+ 77 rows in set (0.001 sec) MariaDB [dbispconfig]> select server_name,web_server from server; +----------------------------+------------+ | server_name | web_server | +----------------------------+------------+ | mercury.investmenttool.com | 1 | +----------------------------+------------+ 1 row in set (0.000 sec) MariaDB [dbispconfig]> select * from server_ip; +--------------+------------+-------------+---------------+----------------+----------------+-----------+-----------+---------+----------------+-------------+------------------+ | server_ip_id | sys_userid | sys_groupid | sys_perm_user | sys_perm_group | sys_perm_other | server_id | client_id | ip_type | ip_address | virtualhost | virtualhost_port | +--------------+------------+-------------+---------------+----------------+----------------+-----------+-----------+---------+----------------+-------------+------------------+ | 1 | 1 | 1 | riud | riud | | 1 | 0 | IPv4 | 10.240.0.7 | y | 80,443 | | 3 | 1 | 1 | riud | riud | | 1 | 2 | IPv4 | 10.240.0.6 | y | 80,443 | | 6 | 1 | 1 | riud | riud | | 1 | 0 | IPv4 | 10.240.0.8 | y | 80,443 | +--------------+------------+-------------+---------------+----------------+----------------+-----------+-----------+---------+----------------+-------------+------------------+ 3 rows in set (0.001 sec) I probably need to look at the logs and need to see what is going on there. 1 log file. I may have caused this issue because I am using galera/mariadb and I have 1 dbispconfig data base that is running all 3 nodes in my current set up. I am looking to go into load balance high availability mode. I have three IP's running right now. Lets say they are 10.240.0.6 10.240.0.7 10.240.0.8 Question: Do I need to have a dbispconfig database for all 3 nodes? I have seen some issues with the dbispconfig database due to the fact that it is rsyncing (galera) the same database to all 3 nodes. This is kind of interesting: root@mercury /var/log/ispconfig/httpd# mysqlcheck --repair --use-frm dbispconfig -h localhost -u root -pSarBit@2010 dbispconfig.aps_instances OK dbispconfig.aps_instances_settings OK dbispconfig.aps_packages OK dbispconfig.aps_settings warning : Number of rows changed from 0 to 3 status : OK dbispconfig.attempts_login warning : Number of rows changed from 0 to 25 status : OK dbispconfig.client warning : Number of rows changed from 0 to 16 status : OK dbispconfig.client_circle OK dbispconfig.client_message_template OK dbispconfig.client_template OK dbispconfig.client_template_assigned OK dbispconfig.country warning : Number of rows changed from 0 to 240 status : OK dbispconfig.cron OK dbispconfig.directive_snippets OK dbispconfig.dns_rr warning : Number of rows changed from 0 to 378 status : OK dbispconfig.dns_slave OK dbispconfig.dns_soa warning : Number of rows changed from 0 to 15 status : OK dbispconfig.dns_ssl_ca warning : Number of rows changed from 0 to 48 status : OK dbispconfig.dns_template warning : Number of rows changed from 0 to 1 status : OK dbispconfig.domain OK dbispconfig.firewall warning : Number of rows changed from 0 to 1 status : OK dbispconfig.ftp_traffic OK dbispconfig.ftp_user warning : Number of rows changed from 0 to 4 status : OK dbispconfig.help_faq OK dbispconfig.help_faq_sections OK dbispconfig.iptables OK dbispconfig.mail_access warning : Number of rows changed from 0 to 79 status : OK dbispconfig.mail_backup OK dbispconfig.mail_content_filter warning : Number of rows changed from 0 to 25 status : OK dbispconfig.mail_domain warning : Number of rows changed from 0 to 18 status : OK dbispconfig.mail_forwarding warning : Number of rows changed from 0 to 4 status : OK dbispconfig.mail_get OK dbispconfig.mail_mailinglist OK dbispconfig.mail_relay_domain note : The storage engine for the table doesn't support repair dbispconfig.mail_relay_recipient OK dbispconfig.mail_traffic warning : Number of rows changed from 0 to 360 status : OK dbispconfig.mail_transport OK dbispconfig.mail_user warning : Number of rows changed from 0 to 23 status : OK dbispconfig.mail_user_filter warning : Number of rows changed from 0 to 95 status : OK dbispconfig.monitor_data warning : Number of rows changed from 0 to 30 status : OK dbispconfig.openvz_ip OK dbispconfig.openvz_ostemplate warning : Number of rows changed from 0 to 1 status : OK dbispconfig.openvz_template warning : Number of rows changed from 0 to 1 status : OK dbispconfig.openvz_traffic OK dbispconfig.openvz_vm OK dbispconfig.remote_session OK dbispconfig.remote_user OK dbispconfig.server warning : Number of rows changed from 0 to 1 status : OK dbispconfig.server_ip warning : Number of rows changed from 0 to 3 status : OK dbispconfig.server_ip_map OK dbispconfig.server_php warning : Number of rows changed from 0 to 2 status : OK dbispconfig.shell_user warning : Number of rows changed from 0 to 1 status : OK dbispconfig.spamfilter_policy warning : Number of rows changed from 0 to 8 status : OK dbispconfig.spamfilter_users warning : Number of rows changed from 0 to 39 status : OK dbispconfig.spamfilter_wblist warning : Number of rows changed from 0 to 32 status : OK dbispconfig.support_message OK dbispconfig.sys_config warning : Number of rows changed from 0 to 3 status : OK dbispconfig.sys_cron warning : Number of rows changed from 0 to 40 status : OK dbispconfig.sys_datalog warning : Number of rows changed from 0 to 349 status : OK dbispconfig.sys_dbsync OK dbispconfig.sys_filesync OK dbispconfig.sys_group warning : Number of rows changed from 0 to 17 status : OK dbispconfig.sys_ini warning : Number of rows changed from 0 to 1 status : OK dbispconfig.sys_log warning : Number of rows changed from 0 to 1 status : OK dbispconfig.sys_remoteaction warning : Number of rows changed from 0 to 3 status : OK dbispconfig.sys_session warning : Number of rows changed from 0 to 1 status : OK dbispconfig.sys_theme warning : Number of rows changed from 0 to 2 status : OK dbispconfig.sys_user warning : Number of rows changed from 0 to 18 status : OK dbispconfig.web_backup warning : Number of rows changed from 0 to 1 status : OK dbispconfig.web_database warning : Number of rows changed from 0 to 32 status : OK dbispconfig.web_database_user warning : Number of rows changed from 0 to 31 status : OK dbispconfig.web_domain warning : Number of rows changed from 0 to 17 status : OK dbispconfig.web_folder OK dbispconfig.web_folder_user OK dbispconfig.web_traffic warning : Number of rows changed from 0 to 52442 status : OK dbispconfig.webdav_user OK dbispconfig.xmpp_domain OK dbispconfig.xmpp_user OK Last issue: I had a server running off a certbot obtained ssl cert on 10.240.0.7. I configured DNS to resolve to 10.240.0.8 and then updated the website in the ispconfig3 interface to only run on 1 IP address. I got a message when I tried to enter the site: The ssl cert is for a different server 10.240.0.7 Obviously I have not gotten the certificate correctly requested. Also the hostnames of the 3 servers show up as mercury.domain.tld but the three hostnames are: mercury.domain.tld mars.domain.tld saturn.domain.tld Named the servers after battlestars in my sci-fi story which is hosted by this configuration. I am going to try and find out where these website servers that I have decommed some years ago are in the dbispconfig database. I would like to turn on troubleshooting and watch the transaction flows. New users are not being added to the OS. Lots of problems but I think I can take care of this with some changes to how I am doing things.
If the websites don't show in the ui, they are probably not in the web_domain table; perhaps you have old sys_datalog jobs to create or update those sites, and then a later job would catch the "delete" ? You might check the sys_datalog table, or the job queue in the Monitor tab of the ui.
I have resolved all these issues. There were some issues with jobs and I cleaned that up. The old sites stopped returning when I stopped the old DNS servers for them. 1 site I blocked with an immutable file in /etc/httpd/conf/sites-available/ I have the ;ab servers running smooth;y on 3 nodes load balanced set up. I do have a serious issue but it requires a new thread.