meteohub.de

My Meteohub/SheevaPlug works great - I love it.

I cannot help but notice, however, that my SMB Server Log always shows problems. Can I impose on someone to explain how I may remedy these errors (most of which have to do with "Transport endpoint is not connected."

MANY thanks in advance for anyone's kind attention to this matter.

2012.08.15 13:05:52 log file cleared by user
[2012/08/15 13:09:08, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/15 13:09:08, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/15 13:09:08, 1] smbd/service.c:close_cnum(1409)
ingoglia-hp (::ffff:192.168.1.100) closed connection to service public
[2012/08/15 13:09:09, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
[2012/08/15 13:09:09, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/15 13:09:09, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/15 13:09:09, 1] smbd/service.c:make_connection_snum(1198)
ingoglia-hp (::ffff:192.168.1.100) connect to service public initially as user root (uid=0, gid=0) (pid 22766)
[2012/08/15 13:39:35, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/15 13:39:35, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/15 13:39:35, 1] smbd/service.c:close_cnum(1409)
ingoglia-hp (::ffff:192.168.1.100) closed connection to service public
[2012/08/15 16:43:07, 1] smbd/service.c:make_connection_snum(1198)
ingoglia-hp (::ffff:192.168.1.100) connect to service public initially as user root (uid=0, gid=0) (pid 13594)
[2012/08/15 17:43:35, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/15 17:43:35, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/15 17:43:35, 1] smbd/service.c:close_cnum(1409)
ingoglia-hp (::ffff:192.168.1.100) closed connection to service public
[2012/08/15 19:12:43, 1] smbd/service.c:make_connection_snum(1198)
ingoglia-hp (::ffff:192.168.1.100) connect to service public initially as user root (uid=0, gid=0) (pid 29831)
[2012/08/15 20:28:11, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/15 20:28:11, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/15 20:28:11, 1] smbd/service.c:close_cnum(1409)
ingoglia-hp (::ffff:192.168.1.100) closed connection to service public
[2012/08/16 10:14:33, 1] smbd/service.c:make_connection_snum(1198)
ingoglia-hp (::ffff:192.168.1.100) connect to service public initially as user root (uid=0, gid=0) (pid 30455)
[2012/08/16 12:32:38, 0] smbd/nttrans.c:call_nt_transact_ioctl(2019)
call_nt_transact_ioctl(0x90078): Currently not implemented.
[2012/08/16 15:23:21, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/16 15:23:21, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/16 15:23:21, 1] smbd/service.c:close_cnum(1409)
ingoglia-hp (::ffff:192.168.1.100) closed connection to service public
[2012/08/16 15:23:22, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
[2012/08/16 15:23:22, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/16 15:23:22, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/16 15:23:22, 1] smbd/service.c:make_connection_snum(1198)
ingoglia-hp (::ffff:192.168.1.100) connect to service public initially as user root (uid=0, gid=0) (pid 31577)
[2012/08/16 16:03:48, 0] lib/util_sock.c:read_socket_with_timeout(939)
[2012/08/16 16:03:48, 0] lib/util_sock.c:get_peer_addr_internal(1676)
getpeername failed. Error was Transport endpoint is not connected
read_socket_with_timeout: client 0.0.0.0 read error = Transport endpoint is not connected.
[2012/08/16 16:03:48, 1] smbd/service.c:close_cnum(1409)
ingoglia-hp (::ffff:192.168.1.100) closed connection to service public
[2012/08/16 19:01:10, 1] smbd/service.c:make_connection_snum(1198)
ingoglia-hp (::ffff:192.168.1.100) connect to service public initially as user root (uid=0, gid=0) (pid 22848)

WFPOST,

Many thanks for this suggestion, but I am so very new to all of this that I cannot even locate the smb config file that is mentioned in your answer (I have 0 experience with unix/linux hardware). How can I access this file (I do not see it anywhere in my SheevaPlug file structure)?

meteohub stores it in
/usr/share/samba

as mentioned this is only a cosmetic error and as the log files are wiped-out very often, there may not be any problem with logging itself.
and as mentioned the workaround can even have negative effects on samba performance ...
it´s always the same shitty thing with microsoft: changing the smb protocol with every new windows release ...

but if you wanna try

install WinSCP. You can access the internal file structure of your meteohub over SSH with this program ...

or use putty to access your meteohub via SSH.
On the command-line enter
nano /usr/share/samba/smb.conf

enter the line mentioned as bug fix
[global] stanza inside smb.conf

smb ports = 139

CTRL-X
Press Y (to save changes)

Restart SAMBA with
/etc/init.d/samba restart

WFPOST,

Thank you and I will take your advice - leave it alone if there may be a degradation in performance (I agree, Microsoft likes to foul things up).

If your opinion is that the errors are merely cosmetic, I can live with this.

I deeply appreciate both your knowledge and willingness to help me.