• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Has my installation become corrupted?

K

Kora Upt

Guest
I couldn't delete a domain. In the Web interface, there was no error message, the domain simply wasn't deleted. I tried from the command line also and got the following message:
An error occured during domain removal: Unable to remove domains: MySQL query failed: Table 'psa.BackupsScheduled' doesn't exist

I needed to delete the domain so that I could then add it as an alias for another domain. I eventually went about with a manual deletion, in which I removed all records in the psa database which made literal reference to the domain I wished to delete, and also deleted the directory in /var/www/vhosts -- after this procedure, I was able to successfully add the domain as an alias on another domain.

Anyway, presumably either whatever caused the original issue, or what I did to get around the original issue, is now carrying over to a new issue ... any subdomains I create through the Web interface appear to be created just fine ... no error message is shown, and the subdomain shows up in the list for the parent domain in the Web interface, but navigating the browser to the subdomain only produces a blank page.

Is it possible that our Plesk installation has simply become corrupted? Is there anything I can do to fix it if so?

We're using Plesk 9.5.2 on CentOS 5.7
 
Looks like that Plesk psa database is corrupted. Try to create missing table BackupsScheduled according to:

mysql> show create table BackupsScheduled\G
*************************** 1. row ***************************
Table: BackupsScheduled
Create Table: CREATE TABLE `BackupsScheduled` (
`id` int(10) unsigned NOT NULL auto_increment,
`obj_id` int(10) unsigned NOT NULL,
`obj_type` enum('server','reseller','client','domain') NOT NULL,
`repository` enum('local','ftp') NOT NULL default 'local',
`last` datetime default NULL,
`period` int(10) unsigned NOT NULL,
`active` enum('true','false') NOT NULL,
`processed` enum('true','false') NOT NULL,
`rotation` int(11) NOT NULL default '0',
`prefix` varchar(255) character set utf8 default NULL,
`email` varchar(255) character set utf8 default NULL,
`split_size` int(10) unsigned NOT NULL default '0',
`suspend` enum('true','false') NOT NULL default 'false',
`with_content` enum('true','false') NOT NULL default 'true',
`backup_day` int(10) unsigned NOT NULL default '0',
`backup_time` time NOT NULL default '00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
 
Create Table: CREATE TABLE `BackupsScheduled` (
`id` int(10) unsigned NOT NULL auto_increment,
`obj_id` int(10) unsigned NOT NULL,
`obj_type` enum('server','reseller','client','domain') NOT NULL,
`repository` enum('local','ftp') NOT NULL default 'local',
`last` datetime default NULL,
`period` int(10) unsigned NOT NULL,
`active` enum('true','false') NOT NULL,
`processed` enum('true','false') NOT NULL,
`rotation` int(11) NOT NULL default '0',
`prefix` varchar(255) character set utf8 default NULL,
`email` varchar(255) character set utf8 default NULL,
`split_size` int(10) unsigned NOT NULL default '0',
`suspend` enum('true','false') NOT NULL default 'false',
`with_content` enum('true','false') NOT NULL default 'true',
`backup_day` int(10) unsigned NOT NULL default '0',
`backup_time` time NOT NULL default '00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Thank you, that corrected the problem.
 
Back
Top