dropped because peer didn’t respond

I've been getting this error quite frequently "dropped because peer didn’t respond". Most of the errors are associated with duplicate names for the logs themselves. The issue seems to stem from the server attempting to rename the file, which causes the whole process to come to a halt.  When the log is renamed by checking the (Rename existing files on conflict) box , the file gets hung up and never reaches the destination. When the log is overwritten by not checking the box, I’m losing data. Anyone else experiencing this issue?

Parents
  • FormerMember
    0 FormerMember over 8 years ago

    I was getting multiple tries to transfer the file via TFTP from the Linux Server doing the PUT command.  It ended up being that the firewall (IPTABLES) was blocking the traffic back, so I just shutdown iptables via "service iptables stop" to get the transfers going.

    Once done I restarted the firewall

    service iptables start"

    Hope that helps JOJO, although I know this is way late.

Reply
  • FormerMember
    0 FormerMember over 8 years ago

    I was getting multiple tries to transfer the file via TFTP from the Linux Server doing the PUT command.  It ended up being that the firewall (IPTABLES) was blocking the traffic back, so I just shutdown iptables via "service iptables stop" to get the transfers going.

    Once done I restarted the firewall

    service iptables start"

    Hope that helps JOJO, although I know this is way late.

Children
No Data