Every few months or so, there's an update to Plesk which overwrites the my.ini settings for MySQL. I have customised these settings significantly, as the defaults have waaaaay to low max connection settings for my server.
However, when these changes are overwritten, my sites are inaccessible because I get so many connection errors and poor InnoDB performance.
How can I prevent the my.ini file from being overwritten? It's not acceptable to have to restore a backup of the file each time there is a change, as suggested by the KB article:
Custom changes in my.ini file are overwritten after microupdate
This takes my sites offline for several hours each time this happens.
However, when these changes are overwritten, my sites are inaccessible because I get so many connection errors and poor InnoDB performance.
How can I prevent the my.ini file from being overwritten? It's not acceptable to have to restore a backup of the file each time there is a change, as suggested by the KB article:
Custom changes in my.ini file are overwritten after microupdate
This takes my sites offline for several hours each time this happens.
Hi @Ales , thank you for this clarification. The Plesk support team came back to me today with the same information : (and this is a good thing to have two thoughts on this shamefully poorly-documented topic by Plesk) :
The file you need to modify is :
C:\Program Files (x86)\Plesk\Databases\MySQL\my.ini
Side-note : So now we know which file to use in Plesk Obsidian, noone seems to be able to tell the exact role of C:\Program Files (x86)\Plesk\Databases\MySQL\Data ...
The file you need to modify is :
C:\Program Files (x86)\Plesk\Databases\MySQL\my.ini
Side-note : So now we know which file to use in Plesk Obsidian, noone seems to be able to tell the exact role of C:\Program Files (x86)\Plesk\Databases\MySQL\Data ...
You can create a custom my.ini file and place it in the /etc/mysql/conf.d directory. Plesk will not overwrite this file, so any changes you make to it will persist through updates.
- Page :
- 1
- 2
There are no replies made for this post yet.