• 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

Resolved PHP Fatal error: Class Smb_BackupController contains 1 abstract method

Dave_Pilbeam

New Pleskian
Virgin installation, switched on today, just the one domain created, click on any link involving Backup Manager and get:

[18-Apr-2016 10:49:30 America/Chicago]
PHP Fatal error: Class Smb_BackupController contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Smb_BackupController::_getFtpSettingsForm) in /usr/local/psa/admin/application/smb/controllers/BackupController.php on line 76

or

[18-Apr-2016 10:52:20 America/Chicago]
PHP Fatal error: Class Admin_BackupController contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Admin_BackupController::_getFtpSettingsForm) in /usr/local/psa/admin/application/admin/controllers/BackupController.php on line 77

Running
OS: CentOS 6.7 (Final)
Plesk version: 12.0.18 Update #81 , last updated at April 18, 2016 06:13 AM

Why's BackupController.php causing a problem?

Dave P
 
Try to fix it with

# /usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair
 
Problem still occurs..

/var/log/plesk/install/plesk_12.0.18_repair_problems.log
=
No output

/var/log/plesk/install/plesk_12.0.18_repair.log
=
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mysqld... mysqld (pid 794) is running...
done
Trying to establish test connection... connected
done
Trying to start service mysqld... mysqld (pid 794) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012000018
Version is OK, no need to create psa database.
Trying to backup MySQL database... Warning: Not dumping MySQL database 'horde' as it doesn't exist
Warning: Not dumping MySQL database 'atmail' as it doesn't exist
done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.12.0.18-12.0.18.20160420-034659.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.0.18-12.0.18.20160420-034701.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Could not open input file: /usr/local/psa/admin/plib/scripts/check_apsc_connection.php
Trying to reset database user password for 'apsc@'... done
APSC database has been registered successfully
Could not open input file: /usr/local/psa/admin/plib/scripts/check_apsc_connection.php

WARNING!
Some problems are found during fix credentials for APS controller database(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log)

Continue...

===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_12.0.18_repair.log' and '/var/log/plesk/install/plesk_12.0.18_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.

**** Product repair completed successfully.

STOP Bootstrapper 12.0.18 repair AT Wed Apr 20 03:47:17 CDT 2016
"/var/log/plesk/install/plesk_12.0.18_repair.log" 70L, 3544C
 
For future reference, updating all Plesk components in Upgrade Panel fixed this problem; (but couldn't upgrade to 12.5 because of restrictive Virtuozzo resource limits at 1&1 hosting)..
 
Back
Top