meteohub.de

I see this data in smb server log:

...
[2008/03/26 16:43:46, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2008/03/26 16:43:46, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2008/03/26 16:43:46, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2008/03/26 16:43:46, 0] lib/util_sock.c: send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2008/03/26 16:44:25, 0] lib/util_sock.c:write_data(562)
...

Is this info OK? I didn't realize it before updating to v2.1d.

Chill,

Hi,

Is there anything I must do in order to stop these errors? I updated to v2.2c and still there:

Chill,

[2008/03/28 13:13:03, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2008/03/28 13:13:03, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2008/03/28 13:15:01, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2008/03/28 13:15:01, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.0.9. Error Connection reset by peer
[2008/03/28 13:15:01, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2008/03/28 13:15:02, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2008/03/28 13:15:02, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.0.2. Error Connection reset by peer
[2008/03/28 13:15:02, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)

dont worry, smb works fine, same reports here...

just don't look at it :laugh:

will inspect this later on (low prio).