pyTivo Discussion Forum
Answers and the development of pyTivo a TiVo transcoding server

 pyTivo shares disappear after a little while Goto page 1, 2, 3  Next
Author Message
hspindel

Joined: 19 Nov 2011
Posts: 26

hspindel

Joined: 19 Nov 2011
Posts: 26

 Posted: Sat Jun 29, 2013 8:01 am    Post subject: Just a couple addenda: I saw in another post that an interaction between UDP on port 5353 and Windows Firewall could be an issue. I'm not using Windows Firewall (I have Comodo). I tried changing beacon to the broadcast address (192.1.1.255). No shares work at all that way. I tried changing beacon to 255.255.255.255. This works the same as the original conf file above - the Premiere sees the shares for a while, then they disappear, the Series 2 sees the shares. I tried changing beacon to "listen". I get this in the log: Unhandled exception in thread started by ERROR:pyTivo:Exception in pyTivo Traceback (most recent call last): File "D:\pytivo\beacon.py", line 165, in server TCPSock.bind(('', 2190)) File "d:\python\lib\socket.py", line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted
wmcbrine

Joined: 04 Jan 2008
Posts: 2623
Location: Maryland

 Posted: Sat Jun 29, 2013 7:37 pm    Post subject: Your last error there just says that something else has already grabbed port 2190 -- probably either TiVo Desktop or another instance of pyTivo, but there's no way to tell from this. Anyway, "beacon: listen" isn't going to solve your problem. If you've read enough to know that this is a common problem that can sometimes be addressed by disabling Zeroconf (and by the way: thank you for doing that reading), then you can probably predict my next recommendation: replace wi-fi links with hard-wired Ethernet, wherever possible. Even MoCA would be a likely improvement. Wi-fi is just not consistent, even when it's fast, due to interference. In your case, you know that the problem correlates with new wi-fi hardware (although I gather that you were successfully using wi-fi before?). So I don't think I'm out of line to suggest that this probably isn't a problem you can correct on the pyTivo end of things._________________My pyTivo fork . My pageLast edited by wmcbrine on Tue Jul 02, 2013 3:23 am; edited 1 time in total
hspindel

Joined: 19 Nov 2011
Posts: 26

 Posted: Sun Jun 30, 2013 1:45 am    Post subject: Thank you for the response. Yes, Tivo Desktop is also running, so that would be responsible for the port 2190 conflict. Yes, I was running WiFi before, using the Tivo Adapter. I don't know for sure whether the new Netgear equipment installation is responsible for the issue arising. I'm not sure exactly when I first saw the problem, but the recent change in my WiFi setup is the only thing that occurred to me as a possible cause. (It could also conceivably be some unrelated software change on the machine running pyTivo.) I suppose temporarily going back to the Tivo Adapter would be a good test. Hate to sacrifice the additional speed that 802.11ac gives me. Regrettably, neither hardwired Ethernet nor MoCA is feasible for me. No way to pull cables. I do notice that the Tivo Desktop share is stable on the Premiere even though the pyTivo shares disappear. So there's something different in the interaction between the Premiere and Tivo Desktop vs. pyTivo. That's what lead me to hope that there was a config option in pyTivo that might address this. Also, both the pyTivo shares and the Tivo Desktop share are stable on the Series 2 hooked to the same bridge as the Premiere, so I'm not convinced this is solely a WiFi problem.
hspindel

Joined: 19 Nov 2011
Posts: 26

 Posted: Sun Jun 30, 2013 7:22 am    Post subject: I was able to verify that with the Tivo N-adapter installed that the pyTivo shares are correctly displayed without interruption. While it's tempting to blame this totally on a WiFi quirk, the fact that the Tivo Desktop share works correctly and that both the pyTivo and the Tivo Desktop shares work correctly on the adjacent Series 2 says to me that there is something a little more subtle going on. Can you suggest anything to debug why Tivo Desktop shares work and pyTivo shares don't? (I'm not claiming this is a pyTivo problem, but I'd like to understand what the problem is if possible.)
lucasnz

Joined: 13 Sep 2010
Posts: 387

 Posted: Mon Jul 01, 2013 7:19 am    Post subject: If you want to understand the underlying protocol, and what's going on, you could try a packet capture on your PC. This isn't for the faint hearted and is quite complex but may be the only way to determine what's going on (of course wmbrine may correct me on this point). If you don't know what a packet capture is, or how to do one, I'm not offering assistance because it's a bit complex. And the logs pulled from the capture are both large, tricky to filter and understand.
philhu

Joined: 04 Jan 2008
Posts: 815
Location: Boston, MA

 Posted: Mon Jul 01, 2013 1:45 pm    Post subject: I had the same problems trying to get it to keep the shares displayed when installing on a QNAP file server (NAS). I finally gave up and built a small/simple Centos6 shell only virtual machine on my server. I run PYTIVO/FFMPEG on it and all problems went away. Somewhere/somehow, there has to be some kind of timing conflict between network devices that shows up in pytivo or the tivo losing the shares. I've always had good luck using a Linux box/vm/etc, so I went back to that and it works fine. Centos is free!
wmcbrine

Joined: 04 Jan 2008
Posts: 2623
Location: Maryland

 Posted: Mon Jul 01, 2013 4:43 pm    Post subject: Reminds me of the infamous photo plugin errors that only showed up under Windows and really slow systems, that turned out to be due to differences in how the socket traffic was buffered by the OS (along with ridiculous overzealousness on the part of the TiVo in rejecting a connection with timing it didn't like). In that case, I was able to work around the problem by buffering within pyTivo. I wonder..._________________My pyTivo fork . My page
wmcbrine

Joined: 04 Jan 2008
Posts: 2623
Location: Maryland

 Posted: Tue Jul 02, 2013 11:13 pm    Post subject: OK, try the version that's in my repos now. I'll be surprised if it makes a difference, but who knows._________________My pyTivo fork . My page
wmcbrine

Joined: 04 Jan 2008
Posts: 2623
Location: Maryland

 Posted: Wed Jul 03, 2013 12:46 am    Post subject: BTW, I did look at this with WireShark, and I didn't notice anything except the missing '\n' at the end of the TiVoConnect beacons (which clearly didn't matter in normal use), but I did find one interesting thing: It looks like the Premieres no longer broadcast old-style, port 2190 TiVoConnect beacons, only Zeroconf. They will still respond to the old-style beacons, though._________________My pyTivo fork . My page
hspindel

Joined: 19 Nov 2011
Posts: 26

 Posted: Fri Jul 05, 2013 6:09 am    Post subject: Not a definitive test yet, but with the new pyTivo code the shares have stayed visible for more than an hour. Previously they were gone in 15 minutes or less. I'll see if the shares are still there tomorrow.
hspindel

Joined: 19 Nov 2011
Posts: 26

 Posted: Fri Jul 05, 2013 11:24 pm    Post subject: The pyTivo shares stayed visible for more than 24 hours straight now, so thank you very much for the fix!
hspindel

Joined: 19 Nov 2011
Posts: 26

 Posted: Sat Jul 06, 2013 11:25 pm    Post subject: Further update: After 48 hours, the pyTivo shares had disappeared. However, simply unplugging and replugging the Tivo's network cable restored them. If they only disappear every couple days, that's still a major improvement and the workaround is easy.
wmcbrine

Joined: 04 Jan 2008
Posts: 2623
Location: Maryland

 Posted: Sat Jul 06, 2013 11:53 pm    Post subject: You could try reenabling Zeroconf at this point, if you haven't already. I assume the TiVo Desktop shares didn't go away?_________________My pyTivo fork . My page
hspindel

Joined: 19 Nov 2011
Posts: 26

Posted: Mon Jul 08, 2013 7:01 am    Post subject:

 wmcbrine wrote: You could try reenabling Zeroconf at this point, if you haven't already. I assume the TiVo Desktop shares didn't go away?

Correct, the TiVo Desktop shares did not go away.

I will try re-enabling Zeroconf. Will report in a while.
 Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First
 All times are GMTGoto page 1, 2, 3  Next Page 1 of 3

 Jump to: Select a forum General----------------General Support----------------SupportHacks Development----------------pyTivoOther Apps Miscellaneous----------------Miscellaneous
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum
Site is in NO WAY affiliated with TiVo Inc