• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Backup: Server settings skipped - error msg

Oliver Marugg

Basic Pleskian
Hi
Using 17.5.3 #6 Ubuntu 16.04.2 I started a FULL backup through the WebGui. Plesk backup my user data, but didnt include any server settings. Following entry was in "view log":
Code:
Warning: server "server"
Server settings are skipped from backup due to error: 'undef' value passed to XmlNode::setAttribute for 'name' at /opt/psa/PMM/agents/shared/XmlNode.pm line 110.

Any ideas or a bug?

-oliver
 
Try to enable debug mode and find more details in backup logs. It may be related to database inconsistency. Try to fix it with 'plesk repair db' at least.
 
Hi Igor

Many thanks for your hint. Ive checked with debug log and I did also a plesk db repair, also with -v flag, and I did a plesk repair all.

In debug mode I receive following errors in /opt/psa/PMM/sessions/2017-05-24-170834.523/psadump.log:
Code:
[8068]: 2017-05-24 17:09:24.366 TRACE SQL: SELECT * FROM dns_recs_t: Params:
[8068]: 2017-05-24 17:09:24.374 TRACE SQL: SELECT c.id FROM certificates c, Repository r WHERE c.id=r.component_id AND r.rep_id=? ORDER BY c.id: Params: 1
[8068]: 2017-05-24 17:09:24.379 TRACE SQL: SELECT * FROM certificates WHERE id=?: Params: 1
[8068]: 2017-05-24 17:09:24.385 TRACE SQL: SELECT * FROM certificates WHERE id=?: Params: 3
[8068]: 2017-05-24 17:09:24.393 TRACE SQL: SELECT id FROM custom_buttons WHERE level=? AND level_id=?: Params: 1, 0
[8068]: 2017-05-24 17:09:24.398 TRACE SQL: SELECT * FROM Templates WHERE owner_id = ? AND type = '?': Params: 1, domain
[8068]: 2017-05-24 17:09:24.404 TRACE SQL: SELECT * from PlanItems: Params:
[8068]: 2017-05-24 17:09:24.408 TRACE SQL: SELECT element, value FROM TmplData WHERE tmpl_id=?: Params: 3
[8068]: 2017-05-24 17:09:24.415 TRACE SQL: SELECT * FROM log_rotation WHERE id=?: Params: 2
[8068]: 2017-05-24 17:09:24.420 TRACE SQL: SELECT propertyName, propertyValue FROM smb_apsBundleFilterItems WHERE filterId = ?: Params: 0
[8068]: 2017-05-24 17:09:24.425 TRACE SQL: SELECT type FROM smb_apsBundleFilters WHERE id = ?: Params: 0
[8068]: 2017-05-24 17:09:24.431 TRACE SQL: SELECT element, value FROM TmplData WHERE tmpl_id=?: Params: 1
[8068]: 2017-05-24 17:09:24.437 TRACE SQL: SELECT * FROM log_rotation WHERE id=?: Params: 1
[8068]: 2017-05-24 17:09:24.442 TRACE SQL: SELECT propertyName, propertyValue FROM smb_apsBundleFilterItems WHERE filterId = ?: Params: 0
[8068]: 2017-05-24 17:09:24.447 TRACE SQL: SELECT type FROM smb_apsBundleFilters WHERE id = ?: Params: 0
[8068]: 2017-05-24 17:09:24.453 TRACE SQL: SELECT element, value FROM TmplData WHERE tmpl_id=?: Params: 5
[8068]: 2017-05-24 17:09:24.460 TRACE SQL: SELECT * FROM log_rotation WHERE id=?: Params: 4
[8068]: 2017-05-24 17:09:24.465 TRACE SQL: SELECT propertyName, propertyValue FROM smb_apsBundleFilterItems WHERE filterId = ?: Params: 0
[8068]: 2017-05-24 17:09:24.469 TRACE SQL: SELECT type FROM smb_apsBundleFilters WHERE id = ?: Params: 0
[8068]: 2017-05-24 17:09:24.476 TRACE SQL: SELECT element, value FROM TmplData WHERE tmpl_id=?: Params: 4
[8068]: 2017-05-24 17:09:24.482 TRACE SQL: SELECT * FROM log_rotation WHERE id=?: Params: 3
[8068]: 2017-05-24 17:09:24.488 TRACE SQL: SELECT propertyName, propertyValue FROM smb_apsBundleFilterItems WHERE filterId = ?: Params: 0
[8068]: 2017-05-24 17:09:24.493 TRACE SQL: SELECT type FROM smb_apsBundleFilters WHERE id = ?: Params: 0
[8068]: 2017-05-24 17:09:24.499 TRACE SQL: SELECT element, value FROM TmplData WHERE tmpl_id=?: Params: 15
[8068]: 2017-05-24 17:09:24.506 DEBUG Unfinished SQL query:
[8068]: 2017-05-24 17:09:24.506 TRACE SQL: SELECT name, value FROM PhpSettingsParameters WHERE id=?: Params: 6
[8068]: 2017-05-24 17:09:24.511 TRACE SQL: SELECT `value` FROM PhpSettingsCustom WHERE `id`=?: Params: 6
[8068]: 2017-05-24 17:09:24.516 TRACE SQL: SELECT name, value FROM WebServerSettingsParameters WHERE webServerSettingsId=?: Params: 13
[8068]: 2017-05-24 17:09:24.521 TRACE SQL: SELECT * FROM log_rotation WHERE id=?: Params: 21
[8068]: 2017-05-24 17:09:24.526 TRACE SQL: SELECT propertyName, propertyValue FROM smb_apsBundleFilterItems WHERE filterId = ?: Params: 14
[8068]: 2017-05-24 17:09:24.531 TRACE SQL: SELECT type FROM smb_apsBundleFilters WHERE id = ?: Params: 14
[8068]: 2017-05-24 17:09:24.536 WARN 293afc92-4bc5-4726-8fe0-2adb2e75be7f Server settings are skipped from backup due to error: 'undef' value passed to XmlNode::setAttribute for 'name' at /opt
/psa/PMM/agents/shared/XmlNode.pm line 110.

[8068]: 2017-05-24 17:09:24.536 DEBUG Server settings are skipped from backup due to error: 'undef' value passed to XmlNode::setAttribute for 'name' at /opt/psa/PMM/agents/shared/XmlNode.pm li
ne 110.
:
 at /opt/psa/PMM/agents/shared/Logging.pm line 165.
    Logging::debug("Server settings are skipped from backup due to error: 'undef'"..., "fatal") called at /opt/psa/PMM/agents/PleskX/PleskX.pm line 888
    PleskX::excludeProblemServerFromBackup(PleskX=HASH(0x38e0338), "'undef' value passed to XmlNode::setAttribute for 'name' at /"...) called at /opt/psa/PMM/agents/PleskX/PleskX.pm line 5
93
    PleskX::dump(PleskX=HASH(0x38e0338)) called at /opt/psa/admin/bin/plesk_agent_manager line 742
    main::__ANON__() called at /usr/share/perl5/Error.pm line 416
    eval {...} called at /usr/share/perl5/Error.pm line 408
    Error::subs::try(CODE(0x3ceb418), HASH(0x3ce20d0)) called at /opt/psa/admin/bin/plesk_agent_manager line 756
    main::perform("owner-uid", "00000000-0000-0000-0000-000000000000", "split-size", undef, "session-path", "/opt/psa/PMM/sessions/2017-05-24-170834.523", "gzip", 1, "server", ...) called
at /opt/psa/admin/bin/plesk_agent_manager line 1381
    main::__ANON__() called at /usr/share/perl5/Error.pm line 416
    eval {...} called at /usr/share/perl5/Error.pm line 408
    Error::subs::try(CODE(0x1bf16d8), HASH(0x366cf20)) called at /opt/psa/admin/bin/plesk_agent_manager line 1389
    main::main() called at /opt/psa/admin/bin/plesk_agent_manager line 1393

And this in same file psadump.log, where for each domain the same message is shown:

Code:
8068]: 2017-05-24 17:09:24.537 DEBUG Free reserved disk space at /var/lib/psa/dumps/.fs_NaN_0
[8068]: 2017-05-24 17:09:24.542 DEBUG Writing dump file: /
===>> This line 42 times:
[8068]: 2017-05-24 17:09:24.551 DEBUG Use of uninitialized value in addition (+) at /opt/psa/PMM/agents/PleskX/Packer.pm line 466.
 
 [8068]: 2017-05-24 17:09:24.551 DEBUG Create repository index: INDEXNUMBERS_domain.ext
 [8068]: 2017-05-24 17:09:24.551 DEBUG Save domain dump resellers/testreseller/clients/user2/domains/domain.ext
 [8068]: 2017-05-24 17:09:24.551 DEBUG Writing dump file: /var/lib/psa/dumps/resellers/testreseller/clients/user2/domains/domain.ext/backup_info_1705241708.xml
===>>> next is shown normally 38 times:
 [8068]: 2017-05-24 17:09:24.554 DEBUG Use of uninitialized value in addition (+) at /opt/psa/PMM/agents/PleskX/Packer.pm line 466.
 [8068]: 2017-05-24 17:09:24.555 DEBUG Create repository index: INDEXNUMBERS_domain.ext
 [8068]: 2017-05-24 17:09:24.555 DEBUG Save domain dump resellers/testreseller/clients/user3/domains/domain.ext

 [8068]: 2017-05-24 17:09:25.472 DEBUG The check dump stderr:
 [8068]: 2017-05-24 17:09:25.475 DEBUG The dump have been validated successfully

And in stderr you will find following error:
Code:
 == STDERR ====================
 Smartmatch is experimental at /opt/psa/PMM/agents/PleskX/Packer.pm line 6880.

Any ideas from your side, I do not know whats next. Many thanks.
 
Last edited:
I suppose that this issue related to the fact that in one of the parameters in database empty field which is parsed by xml as 'undef'. It is very difficult to find it in the scope of forum discussion without investigation directly on your server. Therefore I suggest you contact Plesk Support Team. Experienced supporters with find the reason of this problem and fix it directly on your server.
 
What I've done: I setup a service plan called "NULL" in the meaning of "nothing/zero", because that service plan did/and still should do only DNS for a handful domains. I have other fully pleskified webhosting domains on that system.

What happened: The backup script interpreted the name of the service plan "NULL" as an empty value in MySQL database, as previously suggested in best answer above by @IgorG.

Solution: After renaming the service plan from "NULL" to "NULL_1" and the backup went through without any problem.

Findings: Do not name an service plan "NULL"!;-)

Thanks again tech support and @IgorG!
 
Hi Oliver Marugg,

your description and the solution points to a bug, which should be passed over to the developpers of Plesk - I hope that you don't mind, that I marked your thread as "unsolved" again, even that you solved your issue by renaming the service plan. ;)
 
Back
Top