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

    SELinux policy is not updated

    OK, I'm a bit closer to a solution now. Thought qmail.pp was disabled already before, but it wasn't. So i disabled it and then could load the plesk module without errors. Don't use qmail anyway (Postfix FTW!) ;-D Doesn't looks too bad now. Had to add some SELinux rules to prevent some other...
  2. U

    SELinux policy is not updated

    Is the plesk.te file available somewhere?
  3. U

    SELinux policy is not updated

    Oh, the plesk module could not be enabled after updating the policy because of the errors... # semodule -v -e plesk Attempting to enable module 'plesk': Ok: return value of 0. Committing changes: libsemanage.semanage_direct_commit: WARNING: genhomedircon is disabled...
  4. U

    SELinux policy is not updated

    Very good idea! i disabled the module, that was enough: setenforce 0 semodule -d plesk yum downgrade selinux-policy selinux-policy-targeted yum update selinux-policy selinux-policy-targeted semodule -e plesk sentenforce 1 Downgrade and update because i didn't knew how to rebuild the...
  5. U

    SELinux policy is not updated

    Oh, and btw. The policies do not update anymore since i have updated Plesk the last time...
  6. U

    SELinux policy is not updated

    Unfortunately i can't install my own module because for that to work i need the most current policy from the system, which fails because of these errors. The problem has to come from Plesk because dozens of other CentOS installations just update fine, only our three Plesk servers all have the...
  7. U

    SELinux policy is not updated

    Plesk 11.5.30 Update #32, CentOS 6.5, x86_64 Today i deployed an additional SELinux module to all our CentOS 6.5 machines by Puppet to fix a small problem with our monitoring agent. All machines worked fine, except all Plesk machines. So i tried to updated selinux-policy and...
  8. U

    10.4.4 | Fatal Error | Changing subscription owners

    OK, after looking at the tables again today i recognized that the "cl_id" and "vendor_id" of the domain (which caused the problem) were reversed in the domains table . The vendor_id in the record didn't exist at all in the system and that caused the error message. After changing that manually in...
  9. U

    10.4.4 | Fatal Error | Changing subscription owners

    Same error here after upgrading to 10.4.4 last weekend. There is only one user in the table "clients" which has a NULL vendor_id, and that's the user "admin". "admin" isn't the current and not the new owner of the subscription. If i set the vendor_id to 3 or 4, which is the id the most...
  10. U

    Spam sent by our server using SMTP AUTH

    1. Dump some traffic with tcpdump or snort (whatever you like) f.ex. like this # tcpdump -w /home/whatever/dump_1 not port ssh and port smtp (This dumps in raw format to load the file into wireshark after download) or maybe something like this if you want it readably directly in a file...
  11. U

    Spam sent by our server using SMTP AUTH

    OK, seems that the bin which checks the passwords does not work well: # /usr/local/psa/admin/sbin/checkpw admin /usr/local/psa/etc/dict: magic mismatch checkpw: System Error: unable to open dictionary files at path: /usr/local/psa/etc/dict.* checkpw: System Error: unable to open dictionary...
  12. U

    Spam sent by our server using SMTP AUTH

    The password check option was enabled all the time. But don't seems to really work. I didn't had time to look why it does not work. Maybe tomorrow. I disabled an re-enabled the option, but still can set the password "admin". We will see....
  13. U

    Spam sent by our server using SMTP AUTH

    I now found out that the communication is base64 encoded. So it is very simple to decode it and find out the user: aW5mbw== ==> info YWRtaW4= ==> admin (great password....) To find out which user and domain it is from i used this MySQL query within the psa database: select...
  14. U

    Spam sent by our server using SMTP AUTH

    Hello Has no one any ideas? Today the same Problem started again. Only solution was to disable SMTP-Authentication. Can i somehow enable some more debugging on qmail to see which users are trying to connect over SMTP-Auth?? Or is there at least a possibility to block a recipient domain...
  15. U

    Spam sent by our server using SMTP AUTH

    Hello Since today we have a big problem. Multiple spammers (most from china) are able to send spam through our server using smtp authentication. As soon i disable the smtp authentication they can not send spam anymore. Two possibilities: 1. qMail has a bug with smtp auth 2. Someone...
Back
Top