Search results

Hello everyone. I've 2 servers that are running scheduled backup into a 3rd server via ftp using Plesk Onyx scheduled backups. Suddenly the first server has started to send error mails about aborted backups on multiple domains, while the second server was running backups normally... The messages...

Thank you for your help and for explanation. On my server i don't have so many backup running to be involved in a problem like the one you have described. Furthermore after disabling the compression it seems that the process is very fast also for FTP backups like mines.

You were talking about the number of concurrent backup processes... you said not lower it to 1 (I did)

Is there a reason for that?

Hello Peter, hello everyone. Same problem here. This morning at 4.41 the server was down, when i woke up i immediatly started to search the problem. The TOP command was like that: The only way to have control of the server is to stop mysql service and everything back to normal in few...

Same problem here. I think this is the right article where you can find a solution: It is not possible to log into phpMyAdmin: failed to read session data: files (path: @@PMA_TEMP_DIR@@/session)

To explain better... let's take a Wordpress website on this server like Livia Marasso – Porcelain Creations ...as you can see the website is perfectly working. If i want to access the Wp backend and i open this link https://www.liviamarasso.it/wp-admin the webserver redirect me to...

Look at this: New Server is randomly adding port 7081 on HTTPS requests

This morning i've found all WP websites (not yet manually upgraded to 5.0.1) upgraded to 4.9.9. On one of our two servers the front end works but i can't login in the backend. i try to access https://www.MYDOMAIN.com/wp-admin/ but after waiting long time the browser says "impossible to reach...

In the last days i've received notice that on one domain hosted on our Plesk server there is a problem receiving mails from a specified domain. This is the delivery error message: Original-Recipient: <[email protected]> Action: failed Diagnostic-Code: smtp; 442 Unable to deliver message within...

Same problem here, but with more than 500 mailbox it's really hard to think to do this trick manually.... so please check if the migration manager is ok

At the moment the following lines seem to be a patch... cp /etc/mysql/my.cnf /etc/mysql/my.cnf.old and in my.cnf under the line [mysqld] add : Code: open_files_limit = 4096 and under the line [mysqld_safe] add : Code: open_files_limit = 4096 And after reboot the server Also my advice is to...

Take a look here: Resolved - ERROR: Zend_Db_Statement_Exception: SQLSTATE[HY000]: General error: 23 Out of resources when open...

Same identical problem here. Ovh Vps with Plesk Onyx 17.8.11 #29 on Debian 8.11. Is it a bug? @Bénédicte you have finally solved the issue with that file limit modification? @360webfirm what about you?

@IgorG i think you are right.... now i'm desperate. Look at the following lines... In the last two days i setup a new VPS with the same OVH PLESK ONYX image on Debian 8. Totally new. Than i've migrated about 10 websites today (very light, no overload). I hoped to have a fully functional server...

here is the result PS. i cut some of the warnings to stay in 10000 char post limit What do you think about that?

NEWS! Just bought on OVH a new VPS, same size, same os, same plesk.... just logged in the first time and ran upgrades. This is what i got (see image). I think is not normal, and i'm thinking that buying a new vps and migrate all domain will not solve the problem.... Help!!

Thank you very much for your help. I think to have an idea about the event started the problem, i could be useful to find a solution. About 3 days ago on this VPS i noticed that usage statistics were not updated (disk space, traffic...). So recommended by someone here in the forum i ran this...

# plesk repair db -y should fix all issues with the database - if the database is online. This is a production server, running. Is it safe? I can't risk to make damages

SERVICE MYSQL STATUS bind-address = 127.0.0.1 Yes, my /etc/mysql/my.cnf has that line