Error during app restore (TT RSS): Addons Error - Error piping file (mysqldump)

[necrevistonnezr]

Hi,

during a restore of Tiny Tiny RSS, I get the following, repeated error on Cloudron 7.3.1:

Task Error
If a configuration, update, restore or backup action resulted in an error, you can retry the task.

An error occurred during the restore operation: Addons Error: Error piping file /home/yellowtent/appsdata/72914322-2a76-4682-873d-644f7aa948ba/mysqldump to request http://172.18.0.3:3000/databases/59ebf6fef01cfe61/restore?access_token=b0382c05056eaf6f517b0ada2e0c2b8613d44f37710e56303073112d34c38f2478113dfd2b462e8d911b2773c2c167ef16040636d3ab970e82284e4f855ba9e070ae443e39393435742cf645742cc008292b77c7c03006b053b5320998451039770e704d09778fc98c6a832fcf9b2e2e545a4a5ed67d82c1fd1c53f8a20cac34

From system logs:

2022-10-09T04:00:37.703Z box:tasks startTask: 10901 done. error: {
  stack: 'BoxError: Error piping file /home/yellowtent/appsdata/72914322-2a56-4682-873d-644f7aa948cb/mysqldump to request http://172.18.0.3:3000/databases/59ebf6fef01cfe61/restore?access_token=a40l72c05056eaf6f517b0ada2e0c2b8613d44f37710e56303073112d34c38f2478113dfd2b462e8d911b2773c2c167ef16040636d3ab970e23284e4f855ba9e070ae443e39393435742cf645742cc008292b77c7c03006b053b5320998459839770e704d09778fc98c6a832fcf9b2e2e545a4a5ed67d82c1fd1c53f8a20cac34\n' +
    '    at /home/yellowtent/box/src/services.js:1301:38\n' +
    '    at node:internal/util:443:5\n' +
    '    at finishImpl (node:internal/streams/pipeline:223:7)\n' +
    '    at finish (node:internal/streams/pipeline:203:5)\n' +
    '    at node:internal/streams/pipeline:242:13\n' +
    '    at node:internal/util:443:5\n' +
    '    at node:internal/streams/pipeline:81:5\n' +
    '    at finishImpl (node:internal/streams/pipeline:216:23)\n' +
    '    at finish (node:internal/streams/pipeline:203:5)\n' +
    '    at node:internal/streams/pipeline:242:13',
  name: 'BoxError',
  reason: 'Addons Error',
  details: {},
  message: 'Error piping file /home/yellowtent/appsdata/72914322-2a56-4682-873d-644f7aa948cb/mysqldump to request http://172.18.0.3:3000/databases/59ebf6fef01cfe61/restore?access_token=a40l2c05056eaf6f517b0ada2e0c2b8613d44f37710e56303073112d34c38f2478113dfd2b462e8d911b2773c2c167ef16040636d3ab970e23284e4f855ba9e070ae443e39393435742cf645742cc008292b77c7c03006b053b6205998451039770e704d09778fc98c6a832fcf9b2e2e545a4a5ed67d82c1fd1c53f8a20cac34'
}

[nebulon]

Are there any errors shown on the mysql service side? Also sometimes the import of large data sets requires a lot of memory, so maybe you can try to temporarily up the mysql service memory limit?

[necrevistonnezr]

@nebulon MySQL has 4 GB memory.

MySQL error log:

Oct 09 17:19:40 [POST] /databases
Oct 09 17:19:41 add: adding database 59ebf6fef01cfe61
Oct 09 17:19:41 [POST] /databases/59ebf6fef01cfe61/clear
Oct 09 17:19:41 clear: database 59ebf6fef01cfe61
Oct 09 17:19:59 [POST] /databases/59ebf6fef01cfe61/restore
Oct 09 17:19:59 restore: restoring database 59ebf6fef01cfe61
Oct 09 17:27:48 restore: error in pipline Error: Upload timedout
Oct 09 17:27:48 at IncomingMessage.<anonymous> (/app/code/service.js:282:45)
Oct 09 17:27:48 at IncomingMessage.emit (node:events:390:28)
Oct 09 17:27:48 at Socket.socketOnTimeout (node:_http_server:578:50)
Oct 09 17:27:48 at Socket.emit (node:events:390:28)
Oct 09 17:27:48 at Socket._onTimeout (node:net:501:8)
Oct 09 17:27:48 at listOnTimeout (node:internal/timers:557:17)
Oct 09 17:27:48 at processTimers (node:internal/timers:500:7)
Oct 09 17:27:48 node:events:368
Oct 09 17:27:48 throw er; // Unhandled 'error' event
Oct 09 17:27:48 ^
Oct 09 17:27:48 Error: write EPIPE
Oct 09 17:27:48 at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:98:16)
Oct 09 17:27:48 Emitted 'error' event on Socket instance at:
Oct 09 17:27:48 at Socket.onerror (node:internal/streams/readable:773:14)
Oct 09 17:27:48 at Socket.emit (node:events:390:28)
Oct 09 17:27:48 at emitErrorNT (node:internal/streams/destroy:157:8)
Oct 09 17:27:48 at emitErrorCloseNT (node:internal/streams/destroy:122:3)
Oct 09 17:27:48 at processTicksAndRejections (node:internal/process/task_queues:83:21) {
Oct 09 17:27:48 errno: -32,
Oct 09 17:27:48 code: 'EPIPE',
Oct 09 17:27:48 syscall: 'write'
Oct 09 17:27:48 }
Oct 09 17:27:48 2022-10-09 15:27:48,103 INFO exited: mysql-service (exit status 1; not expected)
Oct 09 17:27:48 2022-10-09 15:27:48,110 INFO reaped unknown pid 297
Oct 09 17:27:49 2022-10-09 15:27:49,119 INFO spawned: 'mysql-service' with pid 298
Oct 09 17:27:50 2022-10-09 15:27:50,124 INFO success: mysql-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Oct 09 17:27:51 MySQL service endpoint listening on http://:::3000

[necrevistonnezr]

@nebulon said in Error during app restore (TT RSS): Addons Error - Error piping file (mysqldump):

Are there any errors shown on the mysql service side? Also sometimes the import of large data sets requires a lot of memory, so maybe you can try to temporarily up the mysql service memory limit?

Can someone help me please? App is still down and I don’t know why and can’t finish the restore.

[nebulon]

This looks very similar to a postgresql issue we just fixed for the next patch release: https://git.cloudron.io/cloudron/postgresql-addon/-/commit/4adb2bcf59c740239515fbfb03d7636f6e60b745

How large is your mysqldump for the app? Also can you send a mail to support@cloudron.io with your dashboard domain and enable remote SSH so we can see if a similar patch might apply?

[nebulon]

Turns out we hit a socket timeout there. Increasing the timeout fixed the issue in this particular case, but we don't quite know why it is hit, despite the socket receiving data. So a full fix is still pending.

[girish]

I have bumped the timeouts for good measure to match the box code - https://git.cloudron.io/cloudron/box/-/commit/deb6d78e4dbeb00572e020f8758d024ef468ca11

[rpotopakhin]

Hello! When cloning the Bookstack application from a backup, I also get an error:

If a configuration, update, restore or backup action resulted in an error, you can retry the task.

An error occurred during the import operation: Addons Error: Error piping file /home/yellowtent/appsdata/fbbe0cca-5489-44de-919b-ec71c4a37297/mysqldump to request http://172.18.30.1:3000/databases/22848c85b3716b00/restore?access_token=62b396273220c163a6b4930bcc65a181123d9cf17bc3690e625a7d8020927e461642f41459cdf8cc2ab4c6a6b69f0ed6d4d4ca2759cb776db49ebbf01f1e96e5da08dde99a28f348732d2450b1ee42b8efc4e95556154435cab798c86e891473a68be397344bb6b56427cf84864661794ed2d51dd5e0773293da1cabf7e9a999

[nebulon]

Do you see any logs in the mysql service logs when that error happens? As a start maybe try to increase the memory limit for that service temporarily, in case the import requires a lot.

[rpotopakhin]

Thank you, it helped