• 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

Search results

  1. Matt N

    Resolved 18.0.40 upgrade killed postfix, now no mail

    I can't explain why the upgrade from 18.0.39 > 18.0.40 really messed with Postfix, or the components within Plesk, such as the "Service Management" or the ability to manage the email accounts etc. The initial upgrade log that alerted me to the upgrade failure, didn't mention PostFix being a...
  2. Matt N

    Resolved 18.0.40 upgrade killed postfix, now no mail

    so after many hours of waiting, and curse words, and panic etc. I run the plesk installer again (ensuring it was pointed at the Plesk Official update servers), and attempted to add PostFix and remove QMail. and low and behold, it chugged along nicely, rather than very quickly giving me the YUM...
  3. Matt N

    Resolved 18.0.40 - killed DB as well... all sites now down

    found this article while waiting for something to happen. Gave it a go. and at least MySQL/MariaDB is now up and running again and services that were relying on it (websites) are now working again...
  4. Matt N

    Resolved 18.0.40 upgrade killed postfix, now no mail

    running greg exclude *.repo inside the /etc/yum.repos.d directory returns no results. my /etc/yum.conf also does not have any reference to packages to exclude. I do have a number of repo's that are not enabled - which was done by the CloudLinux installer.
  5. Matt N

    Resolved 18.0.40 - killed DB as well... all sites now down

    @Peter Debik /var/log/messages shows the following detail for Mariadb: I am assuming that because the CloudLinux MySQL Governor didn't load, that that is the reason for MySQL/Mariadb not starting.
  6. Matt N

    Resolved 18.0.40 - killed DB as well... all sites now down

    output of df -H doesn't look like a disk space issue
  7. Matt N

    Resolved 18.0.40 upgrade killed postfix, now no mail

    using the command : ./plesk-installer --source http://autoinstall.plesk com and then attempting to install postfix still reports the same error. this install has completely killed my server - MariaDB is also dead :(
  8. Matt N

    Resolved 18.0.40 upgrade killed postfix, now no mail

    I am using CloudLinux 7 - but not sure how, or if i should, be changing to install source or even how to check.
  9. Matt N

    Resolved 18.0.40 - killed DB as well... all sites now down

    yep... and it just informs me <snip> Downloading file PHP55_17/php55-cos7-x86_64.plesk17.inf3: 0% Downloading file PHP55_17/php55-cos7-x86_64.plesk17.inf3: 100% was finished. Downloading file PHP56_17/php56-cos7-x86_64.plesk17.inf3: 0% Downloading file...
  10. Matt N

    Resolved 18.0.40 - killed DB as well... all sites now down

    so further to my issues with Postfix/Qmail etc... I've rebooted the server and now, plesk does not work, mariadb is not working... not able to get anything up.... All customer sites are down. when starting the Mariadb service, it stops with the following : when attempting to start the...
  11. Matt N

    Resolved 18.0.40 upgrade killed postfix, now no mail

    Hi All, today, in the middle of the day, no less, my Plesk Obsidian server updated from 18.0.39 > 18.0.40. Well, it attempted to. but encountered an error, and rolled back. This resulted in Postfix having issues. there was multiple packages for postfix installed, which I've managed to clean...
  12. Matt N

    Resolved CentOS 7.x - Stderr:dnssec-keygen: fatal: unknown algorithm EC/AP384SHA384 when attempting to sign DNSSEC

    removing then reinstalling the extension fixed it .... weird! :) Thanks @IgorG!
  13. Matt N

    Resolved CentOS 7.x - Stderr:dnssec-keygen: fatal: unknown algorithm EC/AP384SHA384 when attempting to sign DNSSEC

    according to the extension itself, it shows as Version 1.2.3-93. just wondering whether I should remove and re-add it to see if something failed to update properly.
  14. Matt N

    Resolved CentOS 7.x - Stderr:dnssec-keygen: fatal: unknown algorithm EC/AP384SHA384 when attempting to sign DNSSEC

    Hi All! when attempting to sing my domain using Plesk's DNSSEC setup, I get the following error: The DNSSEC plugin set up okay, and accepted all of the available Encryption types. However, I get this, with almost any of the available Encryption types (I have not tried them all). System is...
  15. Matt N

    Question Curl update using build from source - safe or not?

    Yup - that is why I don't want to do that again .... it was such a pain ... took a while to repair the package manager etc afterward.
  16. Matt N

    Question Curl update using build from source - safe or not?

    Thanks Igor - that is kinda what I was concerned about .... I know that when I had upgraded my older Plesk server (which was running Onyx, but not CloudLinxux), I did upgrade from the City-Fan repo - and run for a while successfully... just not sure whether I am game to do it with CL as well...
  17. Matt N

    Question Curl update using build from source - safe or not?

    Hi All, I am stuck between a rock, a hard place, and a OS that hasn't updated curl in ages! :) Firstly, here's some details : OS : CloudLinux 7.7 (Valery Bykovsky)‬ OS : Centos 7.7 Plesk : Plesk Obsidian Version 18.0.24, last updated on Feb 19, 2020 08:16 PM Curl...
  18. Matt N

    Resolved AWS Route 53 extension with White Label DNS servers

    it seems the the following steps might have actually resolved this: removed all zone records from AWS (using Plesk Mass Management removed Reusable Delegation set that was created previously Create new Reusable Delegation set Mark new Reusable delegation set as default Force "Sync of all...
  19. Matt N

    Resolved AWS Route 53 extension with White Label DNS servers

    Hi All, I am hoping that someone can provide some pointers on using the AWS Route 53 extension with Plesk and AWS to deliver WhiteLabel DNS servers using AWS for my hosted domains. I am running Plesk Obsidian 18.0.20 (although the same behaviour exists in Onyx 17.8.11 as well). Following the...
  20. Matt N

    Resolved Migration failed - rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.2]

    not a problem at all! forums are a LOT more useful when they have suggestions, and when something fixes it, a resolution! :) nothing worse than people coming back saying 'Fixed it' but not leaving answers for anyone else having the same problem :)
Back
Top