Problem when uploading using comet backup software

Developer Discussions troubleshooting
1

Hi,

Seems to be getting alot of issues when uploading using Comet backup, of anyone can help, that would be great. See log below.
Job History › Report | COMET

Time Type Message
2022-11-16 09:13:55 Info Looking up account settings…
2022-11-16 09:14:00 Info Starting backup…
2022-11-16 09:14:09 Info Checking Storage Vault free space…
2022-11-16 09:14:09 Info This Storage Vault contains 112.308 MB.
2022-11-16 09:14:12 Info Scanning 1 path(s)…
2022-11-16 09:14:12 Info Found 2071 files (278.957 MB) in 324 directories. (took 0:00)
2022-11-16 09:14:19 WARNING Couldn’t save data chunk: uplink: stream: ecclient: successful puts (0) less than or equal to repair threshold (35), ecclient: failed to dial (node:1mm3dafAGq4vCdS2YH9B5R8ShJPmeCiQkX9P8mqxd6hwyvEUk7): piecestore: rpc: tcp connector failed: rpc: write tcp 192.168.1.191:50002->213.114.228.215:28972: write: no buffer space available; ecclient: upload failed (node:1XkiDATpYV6Pi5HbzLLoGwWRGuvjQ2YtrhR2sUAwguF6Ltd69S, address:132.145.49.149:28967): protocol: write tcp 192.168.1.191:50054->132.145.49.149:28967: write: no buffer space available; write tcp 192.168.1.191:50054->132.145.49.149:28967: write: no buffer space available; piecestore: piecestore close: write tcp 192.168.1.191:50054->132.145.49.149:28967: write: no buffer space available; ecclient: upload failed (node:1pcXyYz2DvbFicbPJSEbHpwvgyAeGe4nzKNKF1YH9QZtnE4wyr, address:193.22.98.155:28967): protocol: write tcp 192.168.1.191:50071->193.22.98.155:28967: write: no buffer space available; write tcp 192.168.1.191:50071->193.22.98.155:28967: write: no buffer space available; ecclient: failed to dial (node:12mBw4kB78F9qWkCFzTTpo43wr8i1FgZZfhP11uUvsmFWZ8uGDa): piecestore: rpc: tcp connector failed: rpc: write tcp 192.168.1.191:49974->85.30.145.61:28967: write: no buffer space available; ecclient: upload failed

It continues like this…

Thanks

Paul

2

Hello @tmm22 ,
Welcome to the forum!

I believe you already solved this issue by rebooting your router.
For other readers - these errors related to the problems with the local network (network card/router/ISP). They appear when the network is not capable to handle hundreds of connections. The native integration opens hundreds parallel transfers per each 64MB (or less), so if your network is unable to handle this, you likely will see such errors. It also possible to receive a similar error (but different underlaying errors - mostly “context cancelled” or “using a closed connection”), if your upstream bandwidth is lower, than 20 Mbit.

One of the solution is to reboot a router when it’s overloaded, the other is to use an S3-compatible integration instead. If you would use an S3-compatible integration, please be aware that it uses server-side encryption unlike the native integration with a client-side encryption, but it opens much less connections and will not overload your network.

3 Likes