Backup's not working - Broken Pipe

[vlt]

I keep getting this error for a specific PBX, i've searched the forums, about making idle times and all that stuff to 0. All of our other PBX's can backup to this FTP fine.

Still having same issue, even just backing up the FQDN and settings, which is small is causing issues.


Your 3CX backup failed due to the following reason(s):

System.IO.IOException: Unable to write data to the transport connection: Broken pipe.

---> System.Net.Sockets.SocketException (32): Broken pipe

at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

--- End of inner exception stack trace ---

at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at FluentFTP.FtpSocketStream.Write(Byte[] buffer, Int32 offset, Int32 count)

at FluentFTP.FtpDataStream.Write(Byte[] buffer, Int32 offset, Int32 count)

at System.IO.Stream.CopyTo(Stream destination, Int32 bufferSize)

at _3cxNetBackupAndRestore._3cxBackup.UploadTemptoDestination()

at _3cxNetBackupAndRestore._3cxBackup.FinishingTask()

Please Advise.

 

[VasilisV_3CX]

Hi @vlt,

A few questions if I may:

1. Firstly, I'd like more information: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/
2. Is this SFTP or FTP?
3. What if you point the backup to a different FTP server? Does the same error happen?

 

[veiliant]

1.Version Number 18.0 (Build 314)
Server OS (Debian 10 Buster)
Firewall Check passed

2. this is FTP
3. No we don't have another FTP Server, we have 5 other PBX's backing up fine to this FTP server with no issues.

All our other PBX's is the same, latest 3cx and Debian 10

 

[VasilisV_3CX]

Hi @veiliant,

Can you update the PBX to the latest version and try again?

 

[vlt]

18.0 (Build 450) still same error, just updated.

 

[NickD_3CX]

@vlt @veiliant
I assume you 2 are at the same company.
I will contact you shortly via PM.

[EDIT]
FYI, the latest build is 18.0 (build 461) and you are best to upgrade to that.

 

[vlt]

18.0 (build 461) Oh yes, sorry the hotfix came up like 20 minutes later, i updated to that and tried again, same issue, thanks