RHEL 8 support in Plesk

Follow

Comments

53 comments

  • Avatar
    Rodrigo Soares
    Internal error
     Plesk Migrator error: 
    OS CentOS Linux 8.3.2011
    Product Plesk Obsidian Version 18.0.32 Update # 2

    ERROR: Plesk\Exception\Database: DB query failed: SQLSTATE[HY000]: General error: 1 Can&#039;t create/write to file &#039;/var/tmp/#sql_4e8_0.MAI&#039; (Errcode: 28 &quot;No space left on device&quot;), query was: DESCRIBE `sessions` (Mysql.php:64)<br /> <br><a href='http://kb.plesk.com/plesk-error/search?metaId=cba0466d7d87be177bf16bcb04726204&messageId=5fb0294db60d4f69b601253c7a549ad8&file=Mysql.php&line=64&type=Plesk%5CException%5CDatabase&version=18.0.32&message=DB+query+failed%3A+SQLSTATE%5BHY%5D%3A+General+error%3A++Can%22t+create%2Fwrite+to+file+%22%2Fvar%2Ftmp%2F%23sql_e_.MAI%22+%28Errcode%3A++%22No+space+left+on+device%22%29%2C+query+was%3A+DESCRIBE+%60sessions%60' target='_blank'>Search for related Knowledge Base articles</a>



    0
    Comment actions Permalink
  • Avatar
    Nico Timeo

    After a succesfull install of Plesk Obsidian 18.0.27 on a fresh and updated CentOS 8 system, I can't login to Plesk for a "Connection Refused" error.

    Command "iptables -F" resolves the problem. Why this occours? How can I solve this problem?

    Thanks in advance!

    0
    Comment actions Permalink
  • Avatar
    Nico Timeo

    After a succesfull automatic install of Plesk Obsidian 18.0.27 (via SSH) on a fresh and updated CentOS 8 system, I can't login to Plesk for a "Connection Refused" error.
    This is the output for iptables, after Plesk installation:

    # iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
    ACCEPT icmp -- anywhere anywhere
    ACCEPT all -- anywhere anywhere
    ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
    REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination
    REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination

    As you can see, there is no entry for httpd, so connections on port 80 and 443 are refused.
    I tryed also witch web installation, and same problem occuorred.

    Command "iptables -F" resolves the problem. What's wrong?
    I can add an iptables rule manually, ...and then?

    Thanks in advance!

    0
    Comment actions Permalink
  • Avatar
    Rodrigo Soares

    I just performed the following tests with:

    1 - OS: CentOS Stream 8
    Product Plesk Obsidian Version 18.0.32 Update # 2, last updated on Jan 14.

    2 - OS CentOS Linux 8.3.2011
    Product Plesk Obsidian Version 18.0.32 Update # 2, last updated on Jan 17, 2021

    ** Migration tool: Plesk Migrator Version 2.20.2-962

    **** - Server to be migrated:
    * OS CentOS 6.10 (Final)
    Product Plesk Obsidian Version 18.0.31 Update # 3, last updated 12/25/2020

    Result:

    Both CentOS 8 (Stream and Linux 8.3) worked correctly. Much faster Stream version, but ....

    * Grafanna does not respond with Stream version.
    * Plesk Migrator does not
    * PHP versions 5.6 and earlier did not respond.
    * Wersites with summer prior to PHP 7.1 do not respond with ioncube_loader.

    0
    Comment actions Permalink
  • Avatar
    Dennis Am

    Docker now works on CentOS 8 (since Docker extension version 1.4.6): https://docs.plesk.com/release-notes/obsidian/change-log/#docker-1.4.6

    0
    Comment actions Permalink
  • Avatar
    Razvan Rosca

    Any support for cGroups on CentOS 8? RHEL/C8 fully supports cGroups.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Jonathan

    This wasn't tested but should work. Use this instruction to register custom PHP version in Plesk: https://support.plesk.com/hc/en-us/articles/115000497853

    Let me note that enabled custom repositories sometimes prevent Plesk form installing updates.

    0
    Comment actions Permalink
  • Avatar
    GK (Edited )

    Hi,

    Thanks for the good work. I know the big difference between EL7 and EL8 (for example the dnf modules). We always used the official MariaDB (not the redhat ones) packages for the DB on EL7. On EL8 this doesn't work anymore:

    Problem 1: package plesk-backup-utilities-18.0-2.centos.8+p18.0.25.2+t200325.1928.x86_64 requires plesk-mysql-server >= 18.0, but none of the providers can be installed
    - package plesk-mysql-server-18.0-2.centos.8+p18.0.24.0+t200128.1353.noarch requires mariadb-server >= 5.0.60, but none of the providers can be installed
    - conflicting requests
    - package mariadb-server-3:10.3.17-1.module+el8.1.0+3974+90eded84.x86_64 is excluded

    I understand the message because we had to disable the mariadb module because we wanted to use the MariaDB packages.  Right now:

    MariaDB-common-10.3.22-1.el8.x86_64
    MariaDB-server-10.3.22-1.el8.x86_64
    MariaDB-client-10.3.22-1.el8.x86_64

    Fix:

    Adding the official MariaDB packages to the required list in the RPM is very easy (did it myselves a couple of times). Check https://rpm.org/user_doc/boolean_dependencies.html . With this trick you can have a dependency on mariadb-server AND MariaDB-server.

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Karl May (Edited )

    > Atomic did not yet release their ModSecurity rules compatible with CentOS 8/RHEL 8, since it is not available for selection at Tools & Settings > Web Application Firewall > Settings

    What exactly does that mean? atomicorp community support said:

    > The rules are supported on any platform that supports modsecurity, that includes Centos 8.

    0
    Comment actions Permalink
  • Avatar
    Lars Mautsch

    Klinging on what Steve Yates wrote above: CentOS Linux will be retired and support end of 2021. Are there any plans to support CentOS Stream instead of the "normal" releases of CentOS 8 so have a proper subsitute?

    0
    Comment actions Permalink
  • Avatar
    Mitchell van Bijleveld

    It seems like there are now Docker packages available for CentOS 8?

    https://download.docker.com/linux/centos/8/x86_64/stable/Packages/

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Hi Benjamin Hodgetts I have double-checked with CloudLinux and Centos 8 is now supported. I have updated the article.

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Nico Timeo to manage it in a nice way and store permanently please install and enable Firewall module:

    https://support.plesk.com/hc/en-us/articles/115001078014--How-to-manage-local-firewall-rules-on-a-Plesk-for-Linux-server

    0
    Comment actions Permalink
  • Avatar
    Benjamin Noack (Edited )

    Seems that Backup Task limitation dont work under CentOS 8,

    I've limited to 4 Backup Tasks at the same Time, but "top" says 12 backupmng are running. I've set it up to not compress the backups

    0
    Comment actions Permalink
  • Avatar
    Peter Olsen

    Do we know of a time frame for when Advanced ModSecurity Rules by Atomicorp, will be available for usage? A rough estimate.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Bryan Joshua Pedini

    Imunify360 supports CentOS 8 starting from version 4.9, which is currently in beta.

    As far as I know, the "Site Import" issue was investigated in a ticket.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Adrian Chan

    On servers with Plesk it's recommended to use repos provided by Os vendor only. Otherwise, this may lead to dependency issues during Plesk updates or components installation.

    0
    Comment actions Permalink
  • Avatar
    Benjamin Hodgetts

    Specifically CentOS 8 will be retired at that point, CentOS 7 will still be supported until June 30th, 2024.

    0
    Comment actions Permalink
  • Avatar
    Abdullahfahim

    Plesk's Firewall module isn't as flexible as manual nftables/iptables rules so make sure to backup any rules before you enable it.

    0
    Comment actions Permalink
  • Avatar
    Mitchell van Bijleveld

    Any ETA on Docker/Podman support on CentOS 8?

    0
    Comment actions Permalink
  • Avatar
    Francesco Zanti

    Some questions about Docker: I know that Red Hat 8 (and so CentOS 8) supports Podman, instead Docker. 

    Will be there ripercussions on Plesk after this change?

    Is there any Eta for Plesk container support (not only remote) on CentOS 8?

    Finally: could I install Podman / Docker on CentOS 8 + Plesk or there will be some bug / crash?

    Thanks in advance.

    0
    Comment actions Permalink
  • Avatar
    Mitchell van Bijleveld

    Is Docker supposed to be supported later or is this never going to work and only remotely?

    0
    Comment actions Permalink
  • Avatar
    Karl May

    Can you please split the list of limitations into what can't be fixed and things that currently don't work?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request