Search results

You can start with this: http://alvinalexander.com/blog/post/linux-unix/linux-lsof-command Then check http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/

Try to see how many open files are allowed. Could be this, but this I think require a deep research ...

Because security reason :-) 777 or 775 was not safe.

Check that your folder skin have 755 right and the user is your username.

You need to restart apache, just deleting the file will not help. Usually I do not delete the file, cause can still there, I overwrite it like cp /dev/null /var/www/vhosts/domainname/logs/error_log

This is happening all the time. 1. You can ignore it, 140MB is not a lot, logrotate should solve it. 2. You can see where you get a lot of entries and solve it via Fail2Ban or firewall, if you think is an attack. 3. If is a DNS entry like in this case I see, you can eventually try to log only...

Try to see which folder has generated a lot of files, I think it was a PLESK backup or could be log files in /var/www/vhosts/ (like error_log).

https://serversupportforum.de/forum/mail/46417-error-queue-file-write-error.html

No major problem can get from this, except if a vulnerability in Magento, can be easily hacked.

try plesk repair installation plesk repair mail

Try to repair/reinstall Postfix. Or if is hard, start autoinstaller switch to qmail and then switch back with a second install. Usually this work. Not a nice way, but work.

You should not have in php-fpm or fastCGI environment anymore 777 or 775 files/folders. Because apache is executed as a user, you can have safely 644 for files and 755 for folders.

Not in all case work :-) Don't ask me why, usually I use the same, but I got sometimes when it not work.

Go to domains list and there is a Disk Usage column. If you click on it, will order it.

I use automysqlbackup to create a daily/weekly/monthly backup. It is not the perfect solution, but in years saved my *** a few times (or a lot of times). wget -O /etc/cron.daily/automysqlbackup.sh http://www.grafxsoftware.com/download/backup-plesk/automysqlbackup.sh chmod 700...

An another solution, in case if your ISP cannot provide IPv6 reverse DNS is to switch postfix to IPv4 only. Change the following line in the postfix main.cf file and restart postfix: inet_protocols=all into inet_protocols=ipv4

The issue was that it was installed 32 and 64 bit MySQL, I made a symlink from 32 to 64 and worked ...

Please contact me on PM. I will try to help you in private.

yum list mysql* should show if was installed or not mysqlclient, I think yes. if exist, I think it was from ART repo and match this version. If yes, then you should install it again (update). it is easier to me to do it, hard to presume what you have there :-)

http://www6.atomicorp.com/channels/atomic/centos/5/x86_64/RPMS/mysqlclient16-5.1.59-2.el5.art.x86_64.rpm Could this help?