• 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.

Question Plesk Restore: warning (52): duplicate key name?

burnley

Regular Pleskian
I've been trying to pin down and get rid of the following error but so far can't locate it, has anyone else encountered it?

Details Warning: Restore hosting "xxx.tld"
Unable to read backup settings, default settings will be used instead. Details: <unspecified file>(52): duplicate key name

I did come across this issue but its regarding BOM encoded panel.ini file and doesn't appear to be related. I've had several reports across multiple Plesk servers all running ‪CentOS Linux 7.4 Plesk Onyx Version 17.5.3 Update #38 and its consistent on all restores.
 
Do you have any duplicated sections in /usr/local/psa/admin/conf/panel.ini ?
 
Hi Igor, Thanks for the reply. We checked the panel.ini file and there are no duplicate sections; the ones we have are below;

[debug]
[log]
[promos]
[facebook]
[aps]
PHP:
[webserver]

lines 51 to 53 contain the following;

settings.performance.memory_limit.values[]=64M
settings.performance.memory_limit.values[]=96M
settings.performance.memory_limit.values[]=128M

but these values have been in there form before keys were used on backups so we suspect the error doesn't refer to a line in panel.ini
 
settings.performance.memory_limit.values[]=64M
settings
.performance.memory_limit.values[]=96M
settings
.performance.memory_limit.values[]=128M
Anyway, try to leave here only one line.
 
ok removing all the settings.performance.memory_limit.values[]= and simular entries where there was more than one value specified got rid of the message. However that's not exactly a solution as how do we then populate a drop down list with a range of acceptable 'limits' for assorted php settings. Not exactly keen on devs being able to specify whatever they like as most will just try and max anything out, memory limit =5G time out of 100000 seconds that sort of rubbish.
 
Back
Top