Failed to backup
Solved
Support
-
My cloudron instance is failing to backup daily for some time.
I got the message I copy below. When I backup manually the individual apps, they complete ok, so It seems that the failure is in the box itself (more concretely in the mongodb database).
I haven't any clue of the cause, could you please help me? Thanks.
May 28 23:27:57 box:services backupAddons: backing up ["localstorage","mongodb","ldap","sendmail","turn"] May 28 23:27:57 box:services Backing up mongodb May 28 23:28:57 box:taskworker Task took 1724.669 seconds May 28 23:28:57 box:tasks setCompleted - 8799: {"result":null,"error":{"stack":"BoxError: Could not pipe http://172.18.0.9:3000/databases/<uuid>/backup?access_token=<token> to /home/yellowtent/appsdata/<uuid>/mongodbdump: Request timedout\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1245:47)\n at ClientRequest.emit (node:events:390:28)\n at ClientRequest.emit (node:domain:475:12)\n at Socket.socketErrorListener (node:_http_client:447:9)\n at Socket.emit (node:events:390:28)\n at Socket.emit (node:domain:475:12)\n at emitErrorNT (node:internal/streams/destroy:157:8)\n at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)","name":"BoxError","reason":"Network Error","details":{},"message":"Could not pipe http://172.18.0.9:3000/databases/<uuid>/backup?access_token=<token> to /home/yellowtent/appsdata/<uuid>/mongodbdump: Request timedout"}} May 28 23:28:57 box:tasks update 8799: {"percent":100,"result":null,"error":{"stack":"BoxError: Could not pipe http://172.18.0.9:3000/databases/<uuid>/backup?access_token=<token> to /home/yellowtent/appsdata/<uuid>/mongodbdump: Request timedout\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1245:47)\n at ClientRequest.emit (node:events:390:28)\n at ClientRequest.emit (node:domain:475:12)\n at Socket.socketErrorListener (node:_http_client:447:9)\n at Socket.emit (node:events:390:28)\n at Socket.emit (node:domain:475:12)\n at emitErrorNT (node:internal/streams/destroy:157:8)\n at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)","name":"BoxError","reason":"Network Error","details":{},"message":"Could not pipe http://172.18.0.9:3000/databases/<uuid>/backup?access_token=<token> to /home/yellowtent/appsdata/<uuid>/mongodbdump: Request timedout"}} Could not pipe http://172.18.0.9:3000/databases/<uuid>/backup?access_token=<token> to /home/yellowtent/appsdata/<uuid>/mongodbdump: Request timedout at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1245:47) at ClientRequest.emit (node:events:390:28) at ClientRequest.emit (node:domain:475:12) at Socket.socketErrorListener (node:_http_client:447:9) at Socket.emit (node:events:390:28) at Socket.emit (node:domain:475:12) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21)
-
@andres-moya I think just giving mongodb some more memory should make it work. Can you try that?
-
Good point. I checked the services and some of them are yellow (without error, but stalled in loading). I've restarted one app that uses mongodb and now the backup works. But it's very close to the memory limit. If this happens again, I'll increase the memory assigned.
Thanks for pointing it out.
-
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on