[patseguin]

I use OpenElec and ever since beta 3, I've had freezing issues and I had to revert to beta 2. I posted a log with no responses but I am wondering now if it's an issue with NFS?

[Prof Yaffle]

FWIW, it's not something I'm getting using B3 on either of my OE boxes, both connecting via NFS to my 'buntu server with a shared mysql database.

Try today's B4 and see if that's any better?

[patseguin]

I used today's build and that one froze. Here is my log from last time it froze up.

http://pastebin.com/ZFFzWDTu

[Prof Yaffle]

I'm not good enough at reading log files, I'm afraid - nothing obvious to my uneducated eyes. Have you tried disabling some addons, though? When things freeze, can you still ssh into the box (as that would determine whether it's XBMC or the OS that's locking up)?

[.:B:.]

It looks like you don't have debugging enabled, the log as it is now looks pretty useless (the error messages in there don't provide any clues).

I am running an NFS setup myself here, XBMC 13 beta 3, no issues here. NFS server is an up to date Debian Jessie.

[thd042]

Could be you have an issue with connecting to your NFS-server.
On IBM pages I found a hint about NFS soft and hard mounts. On my Linux box I found in nfs(5);

Code:

soft / hard    Determines the recovery behavior of the NFS client after an NFS request times out.  If neither option is  specified
                      (or if the hard option is specified), NFS requests are retried indefinitely.  If the soft option is specified, then
                      the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to  return
                      an error to the calling application.

                      NB: A so-called "soft" timeout can cause silent data corruption in certain cases. As such, use the soft option only
                      when client responsiveness is more important than data integrity.  Using NFS over TCP or increasing  the  value  of
                      the retrans option may mitigate some of the risks of using the soft option.

Not sure if this goes in the right direction, but can you give some more details about your NFS-setup? I mount NFS-directories on my client via /etc/fstab like this:

Code:

192.168.178.11:/export/Mediadisk        /media/Mediadisk        nfs     auto    0       0

Here "auto" would be he parameter to change for further experiments.
Can you ssh into your client? Are client and server connected via cable, wlan or whatever, what is in between? NFS address via hardcodeded IP (as in my example) or names? Some authentification between client and server? All these questions can broaden or narrow the possible reasons.

Ciao
Tom