• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Change qmail/mysql directory

cmaxwell

Regular Pleskian
One of our disk partitions was filling up so we changed the location of qmail and mysql by making symlinks as follows:

/var/qmail => /home/var/qmail
/var/lib/mysql => /home/var/lib/mysql

Everything works fine, except the psadump backup fails to backup the mail or database files.

Do we need to make a hard link instead or is there a better way of doing it?

Thanks.
 
You can't hardlink directories, so if psadump is that sensitive then you are SOL.

I don't use psadump, but atleast I can tell you hardlinks for directories are not possible :).

You could split the second disk into two partitions and mount each partition in /var/qmail and /var/lib/mysql.


Another thing I thought of was the /etc/psa/psa.conf file, I have no idea if tweaking the QMAIL_ROOT_D, QMAIL_MAILNAMES_D, MYSQL_VAR_D variables will fix it -- or make it even worse.
 
Thanks for your reply. It gave me an idea to run the psadump manually (not from cron) and here is the error I found:

/usr/bin/mysqldump: Can't get CREATE TABLE for table `monitor_agent_reports` (Can't open file: 'monitor_agent_reports.MYD'. (errno: 145))

I ran a repair on that MySQL table and it all works fine now. False alarm!

Thanks for the good ideas.
 
Good to know that psadump will freak out if there is table/index corruption.
 
Back
Top