• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue re installing plesk error

Amin

New Pleskian
hi guys,

i stuck and can't figure it out how to fix this issue
i tried to repair with 'sudo plesk repair all -y -v' it didnt help
so i tried the plesk-remover file to remove and re install the plesk
but now when i try 'sudo ./plesk-installer' i get thiss bunch of error below

i appreciate if you can help
thanks



***** installing problem report *****
ERROR while trying to establish test connection
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log), fix and try again
establish test connection
dpkg: error processing package psa-firewall (--remove):
subprocess installed pre-removal script returned error exit status 1
Errors were encountered while processing:
psa-fileserver
plesk-config-troubleshooter
psa-firewall
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish
 
update:

it suggested to use apt-get f install

but it didnt help either i get his

root@co:/# sudo apt -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
plesk-config-troubleshooter psa-fileserver psa-firewall
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 4579 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 101821 files and directories currently installed.)
Removing psa-fileserver (17.8.11-ubuntu16.04.build1708180301.19) ...
Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
dpkg action:
Trying to start service mysql... /usr/sbin/mysqld is stopped
Jul 10 03:20:14 co systemd[1]: Failed to start MySQL Community Server.
Jul 10 03:20:14 co systemd[1]: mysql.service: Unit entered failed state.
Jul 10 03:20:14 co systemd[1]: mysql.service: Failed with result 'exit-code'.

WARNING!
Some problems are found during start service mysql(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log)

Continue...
 
Your database service does not start. Please check the /var/log/messages file when you try to
# service mysql start
or
# service mysqld start
or
# service mariadb start
and also check the output of "systemctl status mysql.service" and "journalctl -xe" for details. They will both list the error that is preventing MySQL from starting. Fix that error first, then start the database service, then continue with your installation.
 
This error usually means that MySQL is down or it is not working properly. Such behavior can occur after a system update, sudden OS shutdown or after incorrect actions with packages. The following steps should be done in order to troubleshoot the issue and find the cause of it:

  1. Log in to the server console or run Terminal and make sure that the server has enough free disk space and inodes:

    # df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/ploop21792p1 40G 4.9G 33G 13% /
    none 1.5G 4.0K 1.5G 1% /dev
    none 1.5G 0 1.5G 0% /dev/shm

    # df -i
    Filesystem Inodes IUsed IFree IUse% Mounted on
    /dev/ploop21792p1 2621440 180351 2441089 7% /
    none 393216 152 393064 1% /dev
    none 393216 1 393215 1% /dev/shm

    Note: All the listed partitions should have free disk space.
  2. Try to start MySQL service:
    # service mysqld start

    Note: On different OS versions the service may be mysql, mariadb
  3. If the service failed to start, try to find the error in service status:
    # service mysqld status

    or check service log located at /var/log/mysqld.log
    Note: The location of log may be also /var/log/mysql/error.log
 
Back
Top