• 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

Recent content by jacco

  1. J

    Resolved Start spamassassin.service Failed with result 'timeout'.

    For the ones who might be interested: The problem was related to the firewall. It did actually crossed my mind yesterday, but I ruled that out. I assumed (i know WRONG!! Never assume) there couldn't be a problem as the connection is made to localhost. Apparently something got awry there. After I...
  2. J

    Resolved Start spamassassin.service Failed with result 'timeout'.

    Thanks, I did bought the license via a reseller and I'm already in contact with them also.
  3. J

    Resolved Start spamassassin.service Failed with result 'timeout'.

    Some extra info I found: https://support.plesk.com/hc/en-us/articles/12387645632791-The-SpamAssassin-service-is-always-stopped-when-the-Plesk-Email-Security-extension-is-installed I do use this extension, so, that would mean the not started SpamAssassin is correct. Then I have to go back to the...
  4. J

    Resolved Start spamassassin.service Failed with result 'timeout'.

    Hi @Peter Debik , It's not. Only the link local (obviously) is on 127.0.0.1. Also, it's not a container. It's a VPS running on a QEMU layer. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00...
  5. J

    Resolved Start spamassassin.service Failed with result 'timeout'.

    After a technical issue in the datacenter, my VPS refuse to receive email. I've hunted the issue down to a failing start of Spamassasin. I can't get it started. It tries and then a timeout occurs. IN /var/log/maillog: Jun 26 19:34:34 vps postfix/smtpd[50634]: warning: connect to Milter service...
  6. J

    Scan finishes immediately

    Replying to myself. I've found the culprit. I have a remote filesystem mounted (SSHFS). That causes the toolkit to not perform a scan. So, devs... I guess the toolkit tries to scan remote filesystems which apparently is denied. Do ignore those. I actually would suggest only scan the root dirs...
  7. J

    Scan finishes immediately

    I’ve been migrating my Ubuntu server (no Plesk) with several WordPress installs to a band new AlmaLinux server with Plesk on it. After I moved over a WordPress install I just performed a scan and all was fine. Suddenly after I migrated the 5th one it stopped working. When I press ‘Scan’ it...
Back
Top