About two weeks ago I installed one of my Wandboards (a Dual) at a
friends house. I just reconfigured the Wandboard with a fixed IP
address for my friends network and I modified fstab to mount a share on
his NAS instead of my NAS. Next I did a clear library and rescan
everything so that LMS would create a database with my friends music.
I left my Wandboard with him so that he could evaluate the system. He
soon complained that the system was very slow and it would lose its
database from time to time. I found that very strange since I dont
have such experiences with none of my Wandboards.
So I decided to install my Wandboard Quad at his home yesterday. I had a
look into the messages log file of the Dual he used and found some
strange entries in there. Here are a few strange ones (to me):
1)
Code:
--------------------
Jan 26 09:57:51 msqueeze jivelite: ERROR net.http - SocketHttp.lua:258
SocketHttp {Music on msqueeze_Chunked}:t_sendConnect: Network is unreachable
--------------------
The above entry is complaining about Music which is my share of music. I
wonder why the Wandboard is complaing about that since I removed that
entry from fstab and replaced it with my friends network share.
2)
Code:
--------------------
Jan 26 00:52:25 msqueeze kernel: [26043.695123] CIFS VFS: Unexpected lookup
error -112
Jan 26 01:59:33 msqueeze kernel: [30071.316829] PHY: 1:01 - Link is Down
Jan 26 01:59:33 msqueeze NetworkManager[225]: <info> (eth0): carrier now OFF
(device state 100, deferring action for 4 seconds)
--------------------
I guess the above has something to do with the mounted network share. My
friends NAS is configured to switch itself off during the night. Would
that cause any issues?
3)
Code:
--------------------
Jan 26 02:00:15 msqueeze jivelite: ERROR net.http - SocketTcp.lua:96
SocketTcp:t_connect: Network is unreachable
Jan 26 02:00:15 msqueeze jivelite: stack traceback:
Jan 26 02:00:15 msqueeze jivelite:
#011/usr/share/jive/jive/net/SocketTcp.lua:96: in function 't_connect'
Jan 26 02:00:15 msqueeze jivelite:
#011/usr/share/jive/jive/net/SocketHttp.lua:255: in function
</usr/share/jive/jive/net/SocketHttp.lua:252>
Jan 26 02:00:15 msqueeze jivelite:
#011/usr/share/jive/jive/net/SocketHttp.lua:159: in function 't_nextSendState'
Jan 26 02:00:15 msqueeze jivelite:
#011/usr/share/jive/jive/net/SocketHttp.lua:221: in function
</usr/share/jive/jive/net/SocketHttp.lua:207>
Jan 26 02:00:15 msqueeze jivelite:
#011/usr/share/jive/jive/net/SocketHttp.lua:159: in function 't_nextSendState'
Jan 26 02:00:15 msqueeze jivelite: #011/usr
--------------------
After the 2) event, the log is filled with blocks as indicated in 3)
Does this suggest that the Wandboard has issues with the NAS being
switched off during the night?
In any case, the Wandboard keeps on spitting the above blocks until 8:19
in the morning. The next events suggest that the Wandboard crashed and
reboots itself.
Any idea what this means?
1 x SB3, 1 x SB Boom, 1 x SB Radio and 2 x SB Touch - all wireless
1 x Wandboard Dual behind the bedroom ceiling
1 x Wandboard Dual for 'msqueeze' (http://www.msqueeze.co.nf/index.html)
project
ReadyNAS NVX running LMS 7.7.3. w iTunes plugin
iPeng 7 on iPhone.
SqueezePad & iPeng 7 on iPad.
http://www.last.fm/user/phibon
------------------------------------------------------------------------
Pascal Hibon's Profile: http://forums.slimdevices.com/member.php?userid=7969
View this thread: http://forums.slimdevices.com/showthread.php?t=99395
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
