LOG ERRORS: read_data & getpeername failed


#1

Both my 2 WD World Book II (1T and 2T Raid) show these errors in the CIFS log:

2011/01/20 14:12:19  read_data: read failure for 4 bytes to client 192.168.1.12. Error = Connection reset by peer
 2011/01/19 19:23:31  read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
 2011/01/19 19:23:31  getpeername failed. Error was Transport endpoint is not connected
 2011/01/19 19:23:31  getpeername failed. Error was Transport endpoint is not connected
 2011/01/19 17:47:31  read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer

 2011/01/17 11:13:19  read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
 2011/01/17 11:13:19  getpeername failed. Error was Transport endpoint is not connected
 2011/01/17 11:13:19  getpeername failed. Error was Transport endpoint is not connected
 2011/01/17 11:11:18  Error writing 4 bytes to client. -1. (Connection reset by peer)
 2011/01/17 11:11:18  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
 2011/01/17 11:11:18  getpeername failed. Error was Transport endpoint is not connected
 2011/01/17 11:11:18  getpeername failed. Error was Transport endpoint is not connected

Both my devices are affected from the Accessibility Bug (after short usage only the ping works, hard reboot is required to get it back).

I’ve tried to move some of the init script files as suggested often in this board but the bug is still there.

What errors are these?

The disk status say: Good

PLEASE… HELP. I can’t go on with all of them useless like this.


#2

I’m sure i’m not the only one who has those errors in the log.

WD Support, could you explain us what are?


#3

I get the same error when I access the SMB share with my blu-ray cifs enabled player. But not when I access the smb share with another device. Result in my case is, my blu-ray player crashes, but my WD mybook remains accessible. I have tried googling the problem, but did not find anything usable.

Found something here that might explain the error:

http://samba.org/~tpot/articles/connection-reset-by-peer.html. But I don’t know how to solve this.


#4

Almost same exact information in  my WD ShareSpace logs.

Seems to be some info on a samba issue and XP Pro issue but nothing about how to resovle the issue on a WD device.

 59:41  getpeername failed. Error was Transport endpoint is not connected
 2011/02/22 15:59:38  getpeername failed. Error was Transport endpoint is not connected
 2011/02/22 15:57:50  read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
 2011/02/22 15:57:50  getpeername failed. Error was Transport endpoint is not connected
 2011/02/22 15:57:50  getpeername failed. Error was Transport endpoint is not connected

WD Support, can you tell us anything abou this error in teh log and how to resolve the issue on our NAS devices?

I have some serious concerns storing mission critical data on a machine that is logging errors 24/7…


#5

I have the same issue. Line after line of 

getpeername failed. Error was Transport endpoint is not connected

Any ideas?