• 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.

Recent content by Brian Taylor

  1. B

    Resolved Unable to run plesk commands

    This has now been resolved by Plesk Support, Copy of the transcript saying what they needed to do. This is the steps that have taken to resolve the issue I found out that Plesk database could not be extracted, I got some warning in logs: 2020-12-17 23:53:40 140071953798912 [Warning] InnoDB...
  2. B

    Resolved Unable to run plesk commands

    Talking to my server provider, they found a warning message in the upgrade log [2020-11-02 09:01:02.225576] Warning: Failed to attach to cgroup /sys/fs/cgroup/systemd/user/root/tasks, installer might be unexpectedly killed later by the system and pointed out a help article related to this...
  3. B

    Resolved Unable to run plesk commands

    Checking through for space issues, everything looks ok for that
  4. B

    Resolved Unable to run plesk commands

    Thanks for having a look. At least I know for certain the upgrade was interrupted, just need to find the cause.
  5. B

    Resolved Unable to run plesk commands

    See attached. df shows there should be space available. parted shows the partition uses lvm, is it ok to use fsck to check further?
  6. B

    Resolved Unable to run plesk commands

    Yes stops there, nothing further after that. /var/log/messages doesn't go back far enough, the oldest one I've got is 20201122. Whatever error there was from the 2nd, I have no idea
  7. B

    Resolved Unable to run plesk commands

    Yes, looks like it. last entries are Running Transaction Check Updating: 1:plesk-php73-7.3.24-1centos.7.201030.1238.x86_64 [1/250] Updating: plesk-php74-7.4.12-1centos.7.201030.1238.x86_64 [2/250] Updating: 1:plesk-php73-pdo-7.3.24-1centos.7.201030.1238.x86_64 [3/250] Updating...
  8. B

    Resolved Unable to run plesk commands

    I have been away from this server for over a month and come back to it to find I cannot access Plesk in any form. The control panel just gives me 'Unable to connect' Typing into the command line, gives no response other than giving me the command prompt The website that is run on the server is...
  9. B

    Scheduled task failing with Connection Refused

    Thank you, that has fixed the problem. I have no idea why those entries were there in the first place, not something I had added.
  10. B

    Scheduled task failing with Connection Refused

    /etc/hosts contains 127.0.0.1 kingdom-sales.co.uk kingdom-sales localhost.localdomain localhost.localdomain localhost4 localhost4.localdomain4 localhost ::1 kingdom-sales.co.uk kingdom-sales localhost.localdomain localhost.localdomain localhost6 localhost6.localdomain6 localhost
  11. B

    Scheduled task failing with Connection Refused

    Hosting Settings has domain set to kingdom-sales.co.uk with that as the preferred domain Web Hosting Access set to the ip address allocated and all match in the dns settings. Kingdom-sales.co.uk is the domain used for the server so I have access ok to the plesk control panel
  12. B

    Scheduled task failing with Connection Refused

    Trying to run scheduled tasks (cron) which worked fine on an easyspace virtual server using plesk 11.5 , we're now on a dedicated server using Plesk 12 and the same jobs are now failing with a Connection Refused error. I cannot find any mention of the error in any log files, the cron log just...
See more
Back
Top