Application clone failure

General
1

Good day,

Backendless Version (3.x / 6.x, Online / Managed / Pro )

4.3.7 Pro

Application ID

EC9D1799-7BD0-D64B-FFFF-1C20C9E9D100

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. App clone is triggered.
  2. Email notification is received that clone is finished.
  3. New application is fully functional.

Actual Behavior

  1. App clone is triggered.

  2. Email notification is received that clone is finished.

  3. Empty screen and error shown after clone completion:
    Backendless encountered an error while handling the request. An internal trouble ticket with ID B87978BB-96CE-0FB6-FF75-0BBDF4935A00 has been created and we will be investigating the issue.

  4. Message in the logs:

    During clone no errors:

Jul 22 11:35:08 ip-10-0-1-92 taskman[19587]: [INFO] - 2022-07-22 11:35:08,447 - from TaskManager in Thread-5 - Received task from redis - com.backendless.tasks.impex.AppCloneTask, UID - 75769be8-22e2-4c31-9764-ea330eead69d, queue length = 2
Jul 22 11:35:08 ip-10-0-1-92 taskman[19587]: [DEBUG] - 2022-07-22 11:35:08,448 - from TaskManager in Thread-5 - Task status for 75769be8-22e2-4c31-9764-ea330eead69d is QUEUED
Jul 22 11:35:08 ip-10-0-1-92 taskman[19587]: [DEBUG] - 2022-07-22 11:35:08,448 - from TaskManager in Thread-193165 - Updating task status for 75769be8-22e2-4c31-9764-ea330eead69d. New task status is RUNNING
Jul 22 11:38:26 ip-10-0-1-92 taskman[19587]: [DEBUG] - 2022-07-22 11:38:26,879 - from TaskManager in Thread-193165 - Updating task status for 75769be8-22e2-4c31-9764-ea330eead69d. New task status is COMPLETE

When app is opened on UI:

Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: [INFO] - 2022-07-22 11:39:00,191 - from TaskManager in Thread-5 - Received task from redis - com.backendless.tasks.ExceptionNotificationTask, UID - 07841e00-b829-464d-a25f-8aba904c8c1e, queue length =
2
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: [DEBUG] - 2022-07-22 11:39:00,192 - from TaskManager in Thread-5 - Task status for 07841e00-b829-464d-a25f-8aba904c8c1e is QUEUED
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: [DEBUG] - 2022-07-22 11:39:00,192 - from TaskManager in Thread-193170 - Updating task status for 07841e00-b829-464d-a25f-8aba904c8c1e. New task status is RUNNING
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: [ERROR] - 2022-07-22 11:39:00,193 - from InternalNotification in Thread-193170 - subject: [Unhandled] Table ‘EC9D1799-7BD0-D64B-FFFF-1C20C9E9D100.EmailSettings’ doesn’t exist
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: Address: 10.0.1.92
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: Time: 2022-07-22 11:39:00.189 UTC
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: Message: org.hibernate.exception.SQLGrammarException: could not extract ResultSet
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: Application ID: EC9D1799-7BD0-D64B-FFFF-1C20C9E9D100
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: Internal Server Error ID: B87978BB-96CE-0FB6-FF75-0BBDF4935A00
Jul 22 11:39:00 ip-10-0-1-92 taskman[19587]: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet

DB of newly cloned app is empty:

mysql> use EC9D1799-7BD0-D64B-FFFF-1C20C9E9D100;
Database changed
mysql> show tables;
Empty set (0.00 sec)

mysql>

Let us know, what could be the reason of such behavior.
Thank you

2

Hi, @Irina_Prozhoha1

In order to understand the issue, I would like to clarify a few additional questions:

  • Has it worked before ?
  • Have you checked the logs of bl-server and bl-taskman? Any clues there?

If you find some issues there please provide us them.You can check the logs using the commands:

docker service logs bl-swarm_bl-server

docker service logs bl-swarm_bl-taskman

Regards,
Marina

3

Hello, Marina

I’ve shared the logs from taskman/play server during clone operation and during app check.
We are hosted on VMs, not in swarm environment.

Yes, it worked before. We cloned some application around a year ago.

4

@Irina_Prozhoha1

This is only the part of the log. We need the entire log folder bl-taskman and preferably the bl-server as well. You can send us them to support@backendless.com with a link to this topic.

Regards,
Marina