Bug NFS failure after resume from standby | Context timeout ->reinit - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228) +---- Thread: Bug NFS failure after resume from standby | Context timeout ->reinit (/showthread.php?tid=155303) |
NFS failure after resume from standby | Context timeout ->reinit - upsite - 2013-02-08 Hi, I switched from SMB to NFS for performance gain which works perfect. But after resuming from Standby(one hour or more) i can't browse my NFS shares because the NFS-server "session" is timeouted but XBMC thinks its still valid. And since NFS is UDP (stateless) there is no validation mechanism which ensures a reconnect. I looked into the code an maybe it's a good idea to call a NFSConnection:eInit() at OnSleep or OnWake to kill all NFS-context. So that after resume XBMC will automaticly reastablish a NFS-"session" Can anyone(dev) look into this ? Thank you RE: NFS failure after resume from standby | Context timeout ->reinit - nefilim - 2013-03-22 I have the same problem. Good suggestion, wonder if it's being included in an upcoming release? RE: NFS failure after resume from standby | Context timeout ->reinit - gigius - 2013-05-03 Hi, same problem here with latest official release. I have to reboot after a resume from standby (mysql connectivity OK, but NFS down) Gigius RE: NFS failure after resume from standby | Context timeout ->reinit - Milhouse - 2013-05-03 Confirming with OpenELEC 3.0.x on x64 with FreeNAS 8.3.x - switching to OS NFS mounts is another solution. Always have to reboot after a suspend to restore NFS access when using XBMC NFS mounts. RE: NFS failure after resume from standby | Context timeout ->reinit - tripkip - 2013-05-06 This is a very widespread issue and I've never seen so few interest from the devs to fix this... Similar threads: https://github.com/OpenELEC/OpenELEC.tv/issues/1178 http://openelec.tv/forum/65-storage/44590-nfs-shares-missing-on-resume-1-95-5-and-higher http://trac.xbmc.org/ticket/13286 http://openelec.tv/forum/76-network-filesystems/63282-problem-with-network-shares-after-sleep-or-wake-up http://forum.xbmc.org/showthread.php?tid=157848 http://openelec.tv/forum/69-network/59958-no-samba-shares-after-resume-from-sleep http://openelec.tv/forum/65-storage/44590-nfs-shares-missing-on-resume-1955-and-higher http://openelec.tv/forum/69-network/62755-invalid-argument-error-smb-issues-after-suspend https://github.com/OpenELEC/OpenELEC.tv/issues/1012 https://github.com/OpenELEC/OpenELEC.tv/issues/1178 RE: NFS failure after resume from standby | Context timeout ->reinit - Ned Scott - 2013-05-06 You assume it's easy to fix, or that people replying to posts indicates dev interest or not. It also appears to be a mostly OE-related problem. I can't say that I've ever had such an issue on other platforms. RE: NFS failure after resume from standby | Context timeout ->reinit - Memphiz - 2013-05-06 Lol - this is the first time i even read about it ... sorry ... *cis* (ohh and no - i won't start reading openelec forums or issue trackers ...) Interesting that it not only affects nfs but samba too... @upsite did you test your approach by any chance? I think this issue might even be an OpenElec kernel thingy or something. Cause the NFS implementation already invalidates timed out contexts (every 4 mins!). So tbh i doubt that the approach upsite proposed will fix this. And the fact that smb has the same issue (which is tcp and not stateless!) makes me think its more of a driver / network stack issue. RE: NFS failure after resume from standby | Context timeout ->reinit - Memphiz - 2013-05-06 Does weather data get pulled after sleep? (so is anything networking related working?) RE: NFS failure after resume from standby | Context timeout ->reinit - devkid - 2013-05-06 I am gathering references to this problem here in the OE forum since a while: http://openelec.tv/forum/76-network-filesystems/63282-problem-with-network-shares-after-sleep-or-wake-up I am still not sure if it is a XBMC problem or an OpenELEC problem. Most references are mentioning OE though. The most interesting part for me is that its 100% reproducable after a suspend time of quite exactly 90 seconds. If I wake up before 90 seconds SMB is working instantly. If I sleep more than 90 seconds then SMB is gone after wakeup. RE: NFS failure after resume from standby | Context timeout ->reinit - devkid - 2013-05-20 Well, I tested lots of different stuff and did some tests with the XBMC source code. Here is what I currently think is happening: It does only happen on Linux, not on Windows cause Windows is using a different SMB code (WINFileSMB.cpp). Linux uses libsmbclient. The problem seems to be that XBMC is not calling smb.Deinit() before going to suspend which makes libsmbclient go nuts upon wakeup. After 90 seconds of idle time the SMB interface deinits itself. So the problem does not occur if there was no SMB access for 90 seconds before going to suspend. Some addons (like library watchdog) permanently keep SMB connections open so the idle time will never apply and the problem will occur on every suspend Im still playing around with it but hopefully the above information is correct and some XBMC devs have a good idea what to do about it. RE: NFS failure after resume from standby | Context timeout ->reinit - reddy - 2013-07-10 I also experience the same issue but on a standard XBMC Frodo 12.2 installation (also visible on Gotham Alpha 5 I had for a while) over Ubuntu minimal (kernel 3.8.0-22-generic), so it's not just OpenElec problem. RE: NFS failure after resume from standby | Context timeout ->reinit - devkid - 2013-07-10 Yeah it happens on all Linux distros. If you are willing to help, I am desperately searching for someone to test a fix: http://openelec.tv/forum/76-network-filesystems/63282-problem-with-network-shares-after-sleep-or-wake-up?start=60 So if you are able to reproduce the issue on OpenELEC 3.1.2 I will provide a (possibly) fixed version for you to try out. RE: NFS failure after resume from standby | Context timeout ->reinit - reddy - 2013-07-11 Ok, so I tried with stock OpenELEC Testing - ION x86_64 Version:3.1.2 from http://openelec.tv/get-openelec/download/viewdownload/3/162 started from USB (live boot on the same machine I have my Ubuntu mini installation with XBMC). So far I tried to suspend it for 30min only and it successfully resumed NFS after waking it up. So, it looks really promising Any chance for integration of the patch to the standalone XBMC soon? My configuration:Asus EeeBox PC EB1012P connected wirelessly to NAS running OpenMediaVault. Code: OpenELEC:~ # lspci Code: root@nas:/# nfsstat -o net RE: NFS failure after resume from standby | Context timeout ->reinit - reddy - 2013-07-12 Well, when resuming after ~8h of hibernation on that OpenELEC I got "Could not connect to network server" error again. So I was able to reproduce it on OpenELEC 3.1.2 taken directly from their site. RE: NFS failure after resume from standby | Context timeout ->reinit - devkid - 2013-07-12 It might sound odd but that is a good thing since my patch in the stock OE 3.1.2 does not patch NFS. I would be confused if NFS would have been fixed in there already. Please have a try with the image in this post: http://openelec.tv/forum/76-network-filesystems/63282-problem-with-network-shares-after-sleep-or-wake-up?start=60#79376 Thats the vanilla 3.1.2 version + NFS-patch. |