(wpb?) Internal error: The site with UUID "8ebcd209-31de-94b0-f6bd-d73df9c0eb77" was not found.

[burnley]

Hi, running Plesk 12.5.30 with the latest #15 and pp-sitebuilder-12.5.29-15081314 we see the Plesk error in the subject when trying to access certain domains in the panel. The error appears to affect all the sitebuilder sites, old and new and seems to have been triggered after deploying a new site in Plesk yesterday around 4:34pm local time.
This specific error has a corresponding KB article - https://kb.odin.com/en/123585 - but the fix doesn't apply in our case because the database data doesn't follow the same pattern. Details:
E.g. domain.com has a sitebuilder site attached. Following the KB steps I'm trying to trace the uuid in the db:
mysql> select dp.dom_id, d.name, dp.val from domains d, dom_param dp where d.id=dp.dom_id and dp.param='site_builder_site_id' and d.name like '%example.com%';
+--------+-----------------+--------------------------------------+
| dom_id | name | val |
+--------+-----------------+--------------------------------------+
| 2391 | example.com | 7c7f4243-421e-7f37-b601-dbf34a28513a |
+--------+-----------------+--------------------------------------+
1 row in set (0.00 sec)
mysql> select target_url from sitebuilder5.site_publish_settings where url like '%example.com%';
+-------------------------------------------+
| target_url |
+-------------------------------------------+
| pp://7c7f4243-421e-7f37-b601-dbf34a28513a |
+-------------------------------------------+
1 row in set (0.00 sec)

So in our case both are identical! We have a fair number of broken sitebuilder domains which come up with that error in Plesk and all of them display the very same uuid: "8ebcd209-31de-94b0-f6bd-d73df9c0eb77". It keeps coming up even after running:
delete from sitebuilder5.session where data like '%8ebcd209-31de-94b0-f6bd-d73df9c0eb77%';
This uuid belongs to the new Sitebuilder site deployed yesterday, let's call it anotherexample.net.au.
Then, I've enabled debugging and sql logging in panel.ini, where I could find these SQL commands, among others:
[...]
mysql> SELECT p.val FROM domains d, dom_param p WHERE (d.id = 2391 OR d.webspace_id = 2391) AND d.id = p.dom_id AND p.param = "site_builder_site_id" and p.val <> "";
+--------------------------------------+
| val |
+--------------------------------------+
| 7c7f4243-421e-7f37-b601-dbf34a28513a |
+--------------------------------------+
1 row in set (0.00 sec)

mysql> SELECT p.val FROM domains d, dom_param p WHERE d.id = p.dom_id AND p.param = "site_builder_site_id" and p.val <> "";
[... last 10 results displayed]
| e46bfb6f-86b5-ed0c-96ff-cb7794594a33 |
| 3d06ae2e-8f6a-7bbd-7cf6-a7c27a7024c6 |
| 7d8301e9-e1dc-c8f7-c662-0fdba77dcf04 |
| dde64d7f-89ce-daa8-a9db-801500322173 |
| 7c7f4243-421e-7f37-b601-dbf34a28513a |
| 4014a972-f7a5-7a76-e1d9-765eeb5edaf7 |
| 75d159fa-6356-4c0b-314a-027b148abfe9 |
| 77ca2298-93fb-067f-faa2-1c655a52083b |
| 5a2b47c5-35c2-cd1a-d484-8e9be1fdc6e4 |
| 8ebcd209-31de-94b0-f6bd-d73df9c0eb77 |
+--------------------------------------+
222 rows in set (0.00 sec)

These queries, with different domain/webspace id of course, are executed for all the affected domains and the last one in the result set of the last query is 8ebcd209-31de-94b0-f6bd-d73df9c0eb77.
New bug in Sitebuilder?

 

[burnley]

Odin ticket ID #2036452

 

[burnley]

I think we got this one sorted by deleting the spurious 8ebcd209-31de-94b0-f6bd-d73df9c0eb77 entry in dom_param. This site_builder_site_id 8ebcd209-31de-94b0-f6bd-d73df9c0eb77 was added in the dom_param table for a new site. The problem was, there was a previous trial which was expired, however this hasn't been picked-up via the API and the upgrade from trial to full was applied on a non-existent trial site, which led to the whole drama.
One of our developers is looking closely at what has actually happened.
So far looks like the problem is resolved at our end after deleting the dom_param entry, we still need to investigate why this happened.