Search results

this may be related to the openssl version in use, resp. the ciphers accepted. on newer os (like almalinux 9 resp. centos) this error is caused by the default crypto policies applied. in this case openssl does neither create nor verify sha1 signatures. a quick workaround is to switch to weak...

bug in Ressource-limit-Notifications I am also receiving this kind of messages as i've posted Confusing-Ressource-limit-Notifications-on-UNLIMITED-subscription-plans This bug occured with 11.5.3, it worked as intended in 11.0. Meanwhile i think, that the notifications is sent, once it is...

1. your failregex is wrong, try this failregex = LOGIN FAILED,(.*)ip=\[<HOST>\]$ 2. you might want to test your filters with fail2ban-regex /path/to/logfile /etc/fail2ban/filter.d/myfilter.conf

steps to reproduce backup issue with ansi-encoded *.conf files :~ # cat /proc/version Linux version 2.6.18-274.el5 ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Fri Jul 22 04:43:29 EDT 2011 :~ # cat /etc/redhat-release CentOS release 5.10 (Final)...

you find the logs below $PRODUCT_ROOT_D/PMM/sessions (on linux /usr/local/psa/PMM/sessions) in timestamped directories, the interesting one is psadump.log 1. to do a quick test if you are affected by the encoding bug i encountered or just to find the problematic domain you can run a fast...

see my post and quick fix here http://forum.parallels.com/showthread.php?293317-plesk-backup-failing-after-MU-23

after applying #23 pleskbackup fails on some domains with "Unable to create dump". in verbose mode the psa_dump.log shows an XML Parser Error [25284]: 13:32:52 DEBUG Exec: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/sbin/backup_restore_helper --backup-subscription domain.tld...

Since upgrading to 11.5.3 i'm receiving notifications on exceeded ressource limits, though the corresponding subscription plans are in fact unlimited. As you see, the unlimited ("unbegrenzt") status is properly saved and detected, but the confusing warning is sent to the client anyway, I'd...

# interpreted as comment the password contains a character '#' (NUMBER SIGN). according to mysql option file docs this is read as beginning of a '#comment, ;comment' if not enclosed in quotes. As far as i have tested plesk allows all characters in passwords, among them numbersign '#' ...

Backup Error MU#44 SOLVED! (Solution included) Finally found the root cause and a solution for this problem. It is caused by changes made by MU#44 in file $PRODUCT_ROOT_D/PMM/agents/shared/Db/MysqlShellBackend.pm Required password for the mysqldump command is now written to an option file...

Error occured suddenly and unattended! 1. I found solution for the missing credentials, when running the sql query from this post: On most of my databases no default user is set (default_user_id in table data_bases is 0). Solved this with: mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa...

seems there are no credentials in the database Dear Igor, following your advice i get no credentials. result: +---------------------+-----------+-------+-----------------+-------+----------+ | name | host | type | name | login | password |...

Plesk Version 10.4.4, Centos 5.8 my backup cronjobs suddenly started to fail after the latest microupdates. (first occurence 9.Oct.2012) CL utilitiy finishes with error: Runtime error: The backup failed with errors! GUI backup finishes without an error message, but on examining log files...