• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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