The error "Connection reset by peer(104) 28.122 to 10.66.204.170:5660,, fid 2049.16.2, upd 0" means Errno 104 ECONNRESET which is system call on a socket. So it means that the node 10.10.10.11:5660 is dead or not reachable.

The "upd 0" means this is an attempt to fetch data from the server (as opposed to writing data to it).

Solution

1. Need to check whether the node 10.10.10.11 is reachable or not, if not then troubleshoot OS/network part.

ping 10.10.10.11

2. Check if mfs is running on node 10.10.10.11 or not. If not then restart the MFS service.

ps -ef | grep mfs

telnet 10.10.10.11:5660

3. It might also worth to check if mfs got crashed last time. If recent core available under /opt/cores with prefix "mfs" then there was a mfs crash happened. In that situation please collect support dump, core trace and core file and open support ticket.

The error "Connection reset by peer(104) 28.122 to 10.66.204.170:5660,, fid 2049.16.2, upd 0" means Errno 104 ECONNRESET which is system call on a socket. So it means that the node 10.10.10.11:5660 is dead or not reachable.

The "upd 0" means this is an attempt to fetch data from the server (as opposed to writing data to it).

Solution

1. Need to check whether the node 10.10.10.11 is reachable or not, if not then troubleshoot OS/network part.

ping 10.10.10.11

2. Check if mfs is running on node 10.10.10.11 or not. If not then restart the MFS service.

ps -ef | grep mfs

telnet 10.10.10.11:5660

3. It might also worth to check if mfs got crashed last time. If recent core available under /opt/cores with prefix "mfs" then there was a mfs crash happened. In that situation please collect support dump, core trace and core file and open support ticket.