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

[Backup manager] Suitebuilder - psadump.log - Cannot execute query to database.

Noturns

Regular Pleskian
Has anyone have seen this issue before?
Any recommendations how i can get rid of this message?

Plesk Message:
ap7fPpl.jpg


If you click on View the Log:
Code:
Backup Task backup_info_1504100306.xml Details
Warning: server "server"
Return code of sitebuilder bru utility: 1. Some errors occured during sitebuilder backup. Please see psadump.log file for more information

note: I don't understand why it shows "sitebuilder" in the logfile because we do not use nor develop sites with "sitebuilder".

# backup_info_1504100306.xml file:
Code:
#tail /var/lib/psa/dumps/backup_info_1504100306.xml
            <include-item>action.d/</include-item>
            <include-item>filter.d/</include-item>
            <include-item>jail.d/</include-item>
            <include-item>jail.conf</include-item>
            <include-item>jail.local</include-item>
          </cid>
        </content>
      </fail2ban>
    </server>
  </migration-dump>
 
Last edited:
Try to find log in /usr/local/psa/PMM/sessions/<session>/psadump.log and find more details there.
 
Try to find log in /usr/local/psa/PMM/sessions/<session>/psadump.log and find more details there.

Code:
 tail /usr/local/psa/PMM/sessions/2015-04-10-030602.464/psadump.log

== STDERR ====================
1+0 records in
1+0 records out
31457280 bytes (31 MB) copied, 0.0529176 s, 594 MB/s
==========================================================================================================================
# Error: Cannot execute query to database.                                                                                 #
==========================================================================================================================

==============================


I think it might be related to another issue i found on the Plesk WordPress Installations
as it shows a WP config that does not exist in /httpdocs/BACKUP -- I'm unable to delete it from this page.

I looked in the PSA DB and noticed it had ID=96.

Would it be safe to delete it?

2n9zu5v.jpg


Some developer had literally created a folder called BACKUP including WP directory.
The person will be fired by the end of this day :)

In order to solve the WP issue i had to

  1. Delete the directory BACKUP httpdocs
  2. Go back in the WP Installation
  3. Select WP site link and click Detach

Correction: Sorry about that guys - this Wordpress was not relevant to the issue of Backup Manager
 
Last edited:
The Plesk Backup Manager still generates the error "No task found with task_id=" when doing backup

I have a daily backup of the important files and logs on a special dedicated sftp repository.
Is there any way of resetting or clearing the backup manager (or cache) ?

Can i simply remove all files in /var/lib/psa/dumps/


sHEmruj.jpg


Correction: After i have removed all backups through Plesk Backup Manger.
These are gone now !and only the warning message as seen in my first post remains
 
Last edited:
Hi Noturns,

this KB - article might help to understand the backup - structure:


Plesk lists ( "reads" ) backups in your Control Panel from the folder "/var/lib/psa/dumps/" and it's depending XML - files, that Plesk generated. There is no storage in the psa - database for these files, so you can delete what ever you would like to in this folder, without the risk to have an inconsistent system.
 
Thanks much appreciated! @UFHH01

I found this KB http://kb.odin.com/en/6080 (did not work)

Code:
step 1
# find /var/lib/psa/dumps/ -name '*info_1503270306.xml'
(...couple of results....)
/var/lib/psa/dumps/backup_info_1503270306.xml

step 2
# cd /var/lib/psa/dumps
# /usr/local/psa/admin/sbin/backup_sign verify backup_info_1503270306.xml > backup_info_1503270306-verified.xml

step 3
# xmllint --format backup_info_1503270306-verified.xml > backup_info_1503270306-formatted.xml

step 4
# cd /usr/bin
# /usr/bin/xmllint --noout --schema /usr/local/psa/PMM/plesk.xsd backup_info_1503270306.xml-formatted.xml


This did not work and would generate this error.....

Code:
warning: failed to load external entity "backup_info_1503270306.xml-formatted.xml"
 
Last edited:
I have setup an email log notification and received a notification email with attachment

Code:
Backup task finished on host vps2.mywebsite.com

Task was created by server Plesk | Admin Account with guid (2ec83dfc-cf82-47df-a0cf-a95c3ba3343f)

Creation date is: 2015-Apr-10 03:06:04
Task status is: warnings

Dump full name is: backup_info_1504100306.xml

Attachment:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="warnings" log-location="/usr/local/psa/PMM/sessions/2015-04-10-030602.464/migration.result">
<object name="server" type="server">
<message id="5cbb588b-0bef-4085-86a4-b783a82a7707" severity="warning" code="UtilityError">
<description>Return code of sitebuilder bru utility: 1. Some errors occured during sitebuilder backup. Please see psadump.log file for more information</description>
</message>
</object>
</execution-result>

I added more detail and better pictures to this topic
and applied some corrections
 
Last edited:
I thought maybe this KB http://kb.odin.com/en/115756 would solve the issue (did not work)

Code:
# plesk db
SHOW VARIABLES LIKE 'old_passwords';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| old_passwords | OFF   |
+---------------+-------+

Added these lines in my.cnf
Code:
[mysqld]
old_passwords=0

Code:
# service mysql restart
Shutting down MySQL..                                      [  OK  ]
Starting MySQL.                                            [  OK  ]

Code:
# sw-engine /usr/local/sb/utils/post_configure.php

Warning: require_once(Zend/Loader/Autoloader.php): failed to open stream: No such file or directory in /usr/local/sb/include/init.php on line 16

Fatal error: require_once(): Failed opening required 'Zend/Loader/Autoloader.php' (include_path='/usr/local/sb/include:.::/usr/local/sb/include:/usr/local/sb/include/PEAR') in /usr/local/sb/include/init.php on line 16
 
Last edited:
Hi Noturns,

you could try the suggestion from the KB - article 119 027 ( even if the suggestion is for "Parallels Plesk 11.5 for Linux and Parallels Business Automation - Standard 4.3" ) and set the limits for all Web Presence Builder ( formerly named as Sitebuilder ) in the subscriptions to "0":

If the suggested MYSQL - command is not valid for Plesk 12, please wait for a Plesk Team Member, to correct the MySQL - command for you into the Plesk 12 usage, or adjust the limit - setting over the Plesk Control Panel for all subscriptions manually.

Afterwards either wait for the next scheduled backup, or initiate a manual backup over the Plesk Control Panel to see if that solved your issue, as stated in the first post of this thread.
 
Thanks again @UFHH01
Code:
# mysql -Ns -uadmin -p`cat /etc/psa/.psa.shadow` psa -Ne" select d.name from domains d JOIN Subscriptions s on (s.object_id=d.id and s.object_type='domain' and d.webspace_id=0) LEFT JOIN SubscriptionProperties sp on (s.id=sp.subscription_id and sp.name='limitsId') LEFT JOIN Limits l on (l.id=sp.value and sp.name='limitsId') where l.limit_name='max_site_builder' and l.value<>0;"|while read d;do /usr/local/psa/bin/domain_pref -u $d -max_site_builder 0;done

The command above to set a limit for "Sites published with Plesk Presence Builder" to 0 seems to be valid in the terminal. I did not see any command errors.
However the error message in Backup Manager is still there when i have started a manual backup.

To make it more strange i cannot locate the psadump.log while it refers to "Please see psadump.log file for more information"
 
Last edited:
Hi Noturns,

  1. Install "locate" if not already existent on your server.
  2. Update the locate database with the command "updatedb"
  3. Locate possible files named as "psadump.log" with the command "locate psadump.log"
... and 4. ... SMILE and see how easy it can be to find files on your server. :D
 
Hi Noturns,

  1. Install "locate" if not already existent on your server.
  2. Update the locate database with the command "updatedb"
  3. Locate possible files named as "psadump.log" with the command "locate psadump.log"
... and 4. ... SMILE and see how easy it can be to find files on your server. :D

Yeah. I happen to have the "locate" command as it was pre-installed on my vps.
I was able to restore the server snapshot from my previous attempt.

And low and behold i found three psadump.log files.
/usr/local/psa/PMM/sessions/2015-04-10-030602.464/psadump.log
/usr/local/psa/PMM/sessions/2015-04-11-030602.853/psadump.log
/usr/local/psa/PMM/sessions/2015-04-11-133601.68/psadump.log

I think i might have typed psdump.log instead of psadump.log - I would never know for sure putty log was not setup :( (don't like putty and it's current color scheme is sometimes hard to make out blue and black colors)

Code:
# tail /usr/local/psa/PMM/sessions/2015-04-11-030602.853/psadump.log
~~~ cut ~~~
# Error: Cannot execute query to database.
~~~ cut ~~~

Code:
tail /usr/local/psa/PMM/sessions/2015-04-10-030602.464/psadump.log
~~~ cut ~~~
# Error: Cannot execute query to database.
~~~ cut ~~~

Code:
tail /usr/local/psa/PMM/sessions/2015-04-11-133601.68/psadump.log
~~~ cut ~~~
# Error: Cannot execute query to database.
~~~ cut ~~~


If someone from the parallels team could please verify if this tutorial is suitable for my issue?
http://kb.odin.com/en/112453
 
Last edited:
Hi Noturns,

you have the choice to define some settings in the "/opt/psa/admin/conf/panel.ini", as for example:
[log]

; Log messages verbosity level (from 0 to 7)
; 0 - only critical errors, 7 - all including debug messages, default - 3
filter.priority = 7
; Enable logging of SQL queries
show.sql_query = on
... which might help to investigate the cause far better, when you do manual backups over the Plesk Control Panel.

As well, you could define a better log - level for backups with the help of the following KB - article:

 
Thanks @UFHH01 i really appreciate your assistance.

Uhmmmmmmmmm.... i tried "# vi /opt/psa/admin/conf/panel.ini" but it does not exist.
I did a "locate panel.ini" and i found "/opt/psa/admin/conf/panel.ini.sample"

What is supposed to contain in this file and what is it's function?

I did however found ....
Web Presence Builder
  • Logs
    • Error log: /usr/local/psa/admin/logs/sitebuilder.log
Code:
# tail sitebuilder.log
line: 144
code: 1049
2015-04-11T03:33:26+02:00       [EMERG]         Zend_Db_Adapter_Exception: SQLSTATE[HY000] [1049] Unknown database 'sitebuilder5'
file: /usr/local/psa/admin/externals/Zend/Db/Adapter/Pdo/Abstract.php
line: 144
code: 1049
2015-04-11T13:41:55+02:00       [EMERG]         SB_Exception: Cannot execute query to database.
file: /usr/local/sb/include/SB/Controller/Plugins/Sb/CheckDb.php
line: 30
code: 1049

i suppose that must be the faulty database that does not exist in my vps
How can i get rid of it?

I have not yet applied http://kb.odin.com/113956 -- would you still recommend this?
 
Hi Noturns,

please OPEN the sample... make the suggested changes and save it as "panel.ini". As you can imagine, SAMPLES are example files, which only do their work ( definitions/configurations ), when the extension ".sample" does not exist anymore.

What you do, or not do, Noturns, is absolutely your choice. The suggestions are to help to investigate the issues... and they should never do any harm to your system. As you might have noticed in the past, we mostly don't write tutorials, but push you to the way, where you are able to solve your issues.


Back to your issue.... as you can see:
2015-04-11T03:33:26+02:00 [EMERG] Zend_Db_Adapter_Exception: SQLSTATE[HY000] [1049] Unknown database 'sitebuilder5' file: /usr/local/psa/admin/externals/Zend/Db/Adapter/Pdo/Abstract.php
the database "sitebuilder5" seems to miss in MySQL, but Plesk ( psa ) stored an entry for it for a domain on your server. The next emergency log - entry, results from the first one... "a query can't be executed" ( because the database is missing ).
Did you delete a domain recently?

"Normally", I would suggest to go phpmyadmin ( database "psa" ), search for the term "sitebuilder5" and try to figure out, which entry the relevant one has to be. BUT ( !!! ), such deletions are delicate, if you don't know, if there are other depending tables/rows, which rely on the entry. So please... only delete entries, if you are SURE, that they are the ones, which caused the error(s)... and always make a dump from the whole database "psa", before you do this.
How would you know, if the entry is the one that causes the issue? Well... I gave the suggestion to log SQL - queries as well... so if you would make the suggested changes and repeat the backup procedure, then you should be able, to actually SEE in the panel - log which SQL query should have been executed and caused an error, because of the non-existent database "sitebuilder5". ;)
 
I try to learn as much as possible why i still can ;)
Found the documentation for panel.ini that i was looking for ---> http://kb.odin.com/en/120101

"Normally", I would suggest to go phpmyadmin ( database "psa" ), search for the term "sitebuilder5" and try to figure out, which entry the relevant one has to be. BUT ( !!! ), such deletions are delicatis.

Well.... it's probably not a good thing that i could not find "sitebuilder5" within the PSA
I've put all my money on the debug method and this is what i found. And for some reason it started at 2015-01-24.

Code:
[2015-04-10 03:22:48] ERR [panel] Error: SQLSTATE[HY000] [xxxx] Unknown database 'sitebuilder5'
[2015-04-11 03:29:56] ERR [panel] Error: SQLSTATE[HY000] [xxxx] Unknown database 'sitebuilder5'
[2015-04-12 03:55:41] ERR [panel] Error: SQLSTATE[HY000] [xxxx] Unknown database 'sitebuilder5'

I have deliberately hidden the [ID] tag with [xxxx]. At this moment i cannot really find more stuff which i can relate to. I wonder if the [xxxx] = ID ??


Update: OK, found a workaround.
- Created a empty db called Sitebuilder5.
- Run manual backup again.
- voila... :)
no more warning message in Backup Manager \o/

My conclusion database is missing in action or should i say K.I.A.....
Must have been deleted by someone.
I guess tomorrow our company has 1 employee less. :D

I checked Sitebuilder in system components. This check displays the component version that should be installed. It does not correspondent with something called "Sitebuilder5" at all.

ibbxbdP.jpg
 
Last edited:
Aaaaaarrrrgh....
I found KB http://kb.odin.com/en/112453 to recreate sitebuilder database.
However this is for Plesk 11.5 only. I tried the script anyway ...

Code:
# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/sb/utils/configure.php --init_db --merge_config --db_admin_name=admin --db_admin_passwd=`cat /etc/psa/.psa.shadow` --sb_db_user_passwd=<random_password>

Code:
bash: syntax error near unexpected token `newline'

update: i think this has to do with -- https://mariadb.com/kb/en/mariadb/sql_mode/
 
Last edited:
Hi Noturns,

due to the case, that you created the sitebuilder database manually, the database itself will be empty. I suggest to use bootstrapper repair, so that your empty database might be identified and ( hopefully ) re-created, without failures.

If this doesn't work, be aware that you still have some inconsistency and you should contact the Support - Team for help to solve this.


For your notice:
If you are familiar with manual installations, you could as well try to re-install all the sitebuilder packages, using the command: "apt-get install --reinstall package-name". Such a procedure will remove the package and re-installs it, without removing depending packages.

Have an eye on the following dependencies:
For pp-sitebuilder:
Code:
Depends: plesk-core (>= 10.3.0), wpb-core (>= 12.0.7), wpb-headers (>= 12.0.5), wpb-designs-00 (>= 12.0.0), wpb-designs-01 (>= 12.0.0), wpb-designs-03 (>= 12.0.0), wpb-designs-04 (>= 12.0.0), wpb-designs-05 (>= 12.0.0), wpb-designs-07 (>= 12.0.0), wpb-designs-09 (>= 12.0.0), wpb-designs-12 (>= 12.0.0), wpb-designs-14 (>= 12.0.0), wpb-designs-20 (>= 12.0.0)
For wpb-core:
Code:
Depends: psa-zendframework (>= 1.11.15), plesk-core (>= 10.3.0)
For wpb-headers:
Code:
Depends: wpb-core (>= 12.0.0)
 
Back
Top