Luke 37110 Posted October 29, 2015 Author Share Posted October 29, 2015 With the latest version 3.0.5768.7 I do have some problems. Currently I cannot add anything to my collection. When trying to add something Emby is not reacting any longer... any ideas ? Hi there, Please provide the complete server log and also be more descriptive about what you were doing in the interface. thanks! Link to comment Share on other sites More sharing options...
cherup 3 Posted October 29, 2015 Share Posted October 29, 2015 (edited) hmm these are all the server logs... I also attached a screenshot of the action I would like to do... server-63581729680.txt server-63581729938.txt server-63581730349.txt server-63581733481.txt server-63581733527.txt server-63581733656.txt Edited October 29, 2015 by cherup Link to comment Share on other sites More sharing options...
Luke 37110 Posted October 29, 2015 Author Share Posted October 29, 2015 do you know which log is from when you tried to create a collection? i do not see any errors relating to that. i also just did some testing of that myself and it seems to be fine. Link to comment Share on other sites More sharing options...
cherup 3 Posted October 29, 2015 Share Posted October 29, 2015 hmm I did some additional checks - with my Android Phone using Emby I can add collections. When using Webgui (With Chromecast, or Edge or IE) it is not working. There is no reaction in the Gui when trying to add something... It seems that log files are not pointing out any error... The logs are all done in roughly 30 mins - so in all Log files there should be the problem... Link to comment Share on other sites More sharing options...
cherup 3 Posted October 29, 2015 Share Posted October 29, 2015 I have seen in Console of Chrome that there is a timeout when trying to create a new collection. Maybe this is something for a deeper analyse ? Link to comment Share on other sites More sharing options...
Luke 37110 Posted October 29, 2015 Author Share Posted October 29, 2015 yes, looking into it, thanks. Link to comment Share on other sites More sharing options...
Hisma 15 Posted November 23, 2015 Share Posted November 23, 2015 (edited) guys, live TV plugin "emby TV" is apparently broken in the last 2 updates. Since the previous update, I cannot get the guide to work. Latest update doesn't fix it either. When I go to settings for "schedules direct", I enter my login info (which I verified is correct), my country and zip code, and "lineup" does not populate. I cannot select my local provider, which is comcast. The schedule simply doesn't populate as a result. "refresh guide data" is greyed out. Here is the relevant log entries - 2015-11-23 01:02:47.1600 Error - App: Error getting headends2015-11-23 01:02:47.1608 Info - HttpServer: HTTP Response 200 to 192.168.0.145. Time: 72ms. http://192.168.0.3:8096/mediabrowser/LiveTv/ListingProviders/Lineups?Id=b9147b73e36a48a0bc4294af5a3e7f56&Location=77007&Country=USA2015-11-23 01:02:48.4677 Info - App: HttpClientManager POST: https://json.schedulesdirect.org/20141201/token2015-11-23 01:02:48.5857 Info - EmbyTV: Authenticated with Schedules Direct token: e21d044f471c9419f69df915e1f8bdfe2015-11-23 01:02:48.5857 Info - EmbyTV: Channel Station ID is: 107662015-11-23 01:02:48.5860 Info - App: HttpClientManager POST: https://json.schedulesdirect.org/20141201/schedules2015-11-23 01:02:48.9240 Info - App: HttpClientManager POST: https://json.schedulesdirect.org/20141201/programs2015-11-23 01:02:49.2733 Info - App: HttpClientManager POST: https://json.schedulesdirect.org/20141201/metadata/programs2015-11-23 01:02:49.7357 Info - EmbyTV: Finished with EPGData Everything looks fine here, but it's still not working. I may be looking in the wrong place though, I attached the entire log so someone smart can look. Does the incorrect time/date have something to do with this? How can I fix that?? I use the exact same schedules direct info for mythtv, which I use with kodi, and I get schedule data just fine, so this is definitely an emby issue, not a schedules direct issue. I updated to the latest version of emby server, Version 3.0.5781.1, but it was happening in the previous revision as well. I was hoping an update would fix it, but it has not. Annoying since I like to stream TV remotely when I am at work sometimes (lol). When I'm at home I just use kodi w/ mythtv plugin. Can someone take a look at this? emby.log Edited November 23, 2015 by Hisma Link to comment Share on other sites More sharing options...
Luke 37110 Posted November 23, 2015 Author Share Posted November 23, 2015 Thanks for the report. We're going to have a patch release tomorrow that I know will address some of the failures i see in your log, so stay tuned for that. 1 Link to comment Share on other sites More sharing options...
Hisma 15 Posted November 23, 2015 Share Posted November 23, 2015 Thanks for the report. We're going to have a patch release tomorrow that I know will address some of the failures i see in your log, so stay tuned for that. Thanks Luke! Yes, there appeared to be some missing files or something? I do not notice any lack of functionality other than non-working guide for emby TV, but I did see several errors that seem to be related to mono & other libraries. Appreciate your work. I will keep on the lookout for updates. If you want me to provide any more data let me know. Link to comment Share on other sites More sharing options...
Hisma 15 Posted November 23, 2015 Share Posted November 23, 2015 It may help that I add that when emby TV first released, it did work just fine w/ my emby server. I was able to download schedules & have full functionality. So something done in a recent update broke it. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 5, 2016 Share Posted January 5, 2016 (edited) Could the maintainer of the FreeNAS plugin please apply the following patch to the bundled Mono version? https://github.com/mono/mono/compare/mono:mono-4.2.1.124...razzfazz:mono-4.2.1.124-increase_maxfds.diff This should fix real-time library monitoring for libraries with >200 files/folders as outlined in http://emby.media/community/index.php?/topic/29216-consistent-server-crashing-on-freenas/ EDIT: Update link. Edited January 9, 2016 by razzfazz Link to comment Share on other sites More sharing options...
josh4trunks 70 Posted January 5, 2016 Share Posted January 5, 2016 Could the maintainer of the FreeNAS plugin please apply the following patch to the bundled Mono version? https://github.com/r...3470ecea44fd165 This should fix real-time library monitoring for libraries with >200 files/folders as outlined in http://emby.media/community/index.php?/topic/29216-consistent-server-crashing-on-freenas/ I can try applying this and pushing out an update when I get home in a few days. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 5, 2016 Share Posted January 5, 2016 I opened a FreeBSD PR for this (https://bugs.freebsd...g.cgi?id=205919); you should be able to just download the patch from there and drop it into lang/mono/files. 1 Link to comment Share on other sites More sharing options...
josh4trunks 70 Posted January 7, 2016 Share Posted January 7, 2016 @@razzfazz I built an updated emby with the patch, do you or someone else mind verifying that it worked? Thanks! https://www.jruehlig.com/owncloud/index.php/s/SGTGH4X9lByrfNJ Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 8, 2016 Share Posted January 8, 2016 (edited) There were actually a bunch of other issues hiding behind this; see the following branches: https://github.com/razzfazz/mono/tree/mono-4.2.1.124-fix_dllimport https://github.com/razzfazz/mono/tree/mono-4.2.1.124-handle_eintr https://github.com/razzfazz/mono/tree/mono-4.2.1.124-native_realpath https://github.com/razzfazz/mono/tree/mono-4.2.1.124-fix_rename https://github.com/razzfazz/mono/tree/mono-4.2.1.124-increase_maxfds You can find a single commit with all the changes combined here: https://github.com/mono/mono/compare/mono:mono-4.2.1.124...razzfazz:mono-4.2.1.124-freebsd_fixes.diff With that applied, my logs are now clear of any watcher-related exceptions; however, I haven't really had time to do extensive testing, and I'm on plain FreeBSD, not FreeNAS. EDIT: Update links. Edited January 9, 2016 by razzfazz Link to comment Share on other sites More sharing options...
josh4trunks 70 Posted January 8, 2016 Share Posted January 8, 2016 (edited) There were actually a bunch of other issues hiding behind this; see the following branches: https://github.com/razzfazz/mono/tree/mono-4.2.1.124-fix_dllimport https://github.com/razzfazz/mono/tree/mono-4.2.1.124-handle_eintr https://github.com/razzfazz/mono/tree/mono-4.2.1.124-native_realpath https://github.com/razzfazz/mono/tree/mono-4.2.1.124-fix_rename https://github.com/razzfazz/mono/tree/mono-4.2.1.124-increase_maxfds You can find a single commit with all the changes combined here: https://github.com/razzfazz/mono/commit/b18273b354ade6baf1b0f763bc495a63f7c423c7 With that applied, my logs are now clear of any watcher-related exceptions; however, I haven't really had time to do extensive testing, and I'm on plain FreeBSD, not FreeNAS. great work! Any idea when you will have everything verified and in a single patch/commit for FreeBSD/upstream mono? I'd prefer to release a plugin when you or someone else knows it all works so I don't have a bunch of users with crashing installs. @@kjp4756 you don't happen to run FreeNAS do you? Edited January 8, 2016 by josh4trunks Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 8, 2016 Share Posted January 8, 2016 I think some of these changes are not going to be acceptable for upstream Mono; in particular the fix_rename change modifies the handling of renames and leads to slightly different (but ok for Emby) behavior, including on Darwin. I'll try and submit pull requests for the other changes this weekend if I can find the time. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 8, 2016 Share Posted January 8, 2016 (edited) Also, as mentioned in the other thread, there was one more issue that came up; new combined patch is here: https://github.com/mono/mono/compare/mono:mono-4.2.1.124...razzfazz:mono-4.2.1.124-freebsd_fixes.diff EDIT: Update URL to point to most recent version. Edited January 9, 2016 by razzfazz Link to comment Share on other sites More sharing options...
kjp4756 41 Posted January 8, 2016 Share Posted January 8, 2016 great work! Any idea when you will have everything verified and in a single patch/commit for FreeBSD/upstream mono? I'd prefer to release a plugin when you or someone else knows it all works so I don't have a bunch of users with crashing installs. @@kjp4756 you don't happen to run FreeNAS do you? Yes I run freenas. I use a regular jail for emby instead of the plugin because I use a bunch of custom scripts to handle the library updates currently. Once the built-in library monitor is working then I'll likely switch to the plugin. Link to comment Share on other sites More sharing options...
kjp4756 41 Posted January 9, 2016 Share Posted January 9, 2016 Ok library monitor works great for me on freenas 9.3 in a standard jail using the latest commits for mono from razzfazz. You probably could go ahead and update the plugin using the fixes for mono if you think it's a good idea. I've had zero issues in almost 24 hours. The only thing I'm not sure on is how mono updates will work if all of razzfazz's mono changes aren't accepted upstream. Should there be a forked version of mono just for emby? Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 9, 2016 Share Posted January 9, 2016 Well, the good news is that I think most of the changes are actually fine for upstreaming, and the rest is relatively simple stuff, so probably something that can just go into the FreeBSD ports tree. 2 Link to comment Share on other sites More sharing options...
scharbag 15 Posted January 9, 2016 Share Posted January 9, 2016 A big thank you to all of you who make Emby work on FreeNAS!! Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 9, 2016 Share Posted January 9, 2016 (edited) The complete set of changes, which have been working without issues for me for almost two days now, are in the last commit on the following branch: https://github.com/razzfazz/mono/tree/mono-4.2.1.124-freebsd_fixes This is against the Mono version that the current FreeBSD port is based on (4.2.1.124). Here's a branch with the same changes applied to upstream master: https://github.com/razzfazz/mono/tree/freebsd_fixes It's virtually identical with the exception of the removal of two lines (kevent_notimeout is no longer DllImport'ed in master). I see that getting these changes into upstream Mono would require me to go through their CLA process, which I can't do right now. The changes are pretty simple and all within a single file, so @@josh4trunks if you could just drop the patch into your ports tree when building the plugin, that would probably be the easiest way forward. It should be pretty straightforward to keep the change up to date with Mono master; KeventWatcher.cs hasn't exactly been seeing a ton of activity. Edited January 9, 2016 by razzfazz Link to comment Share on other sites More sharing options...
pprezzla 2 Posted January 9, 2016 Share Posted January 9, 2016 there's so many thing's I love about emby over plex and I am eager to make the jump but I just can't get it work for me.I'm having major issues with the plugin switching off and media disappearing. I can see in other posts it might be something to do with mono but 'm a bit of a novice. I had more luck installing it through ports in a standard jail but can someone point me in the right direction how to patch with the github commits?i've only ever updated using portupgrade and whether it's unrelated or not, i'm getting 'portupgrade -a: command not found' Link to comment Share on other sites More sharing options...
josh4trunks 70 Posted January 10, 2016 Share Posted January 10, 2016 Thanks @@razzfazz I had to edit the patch you linked slightly for it to work. Building the PBI now, and will soon post it here for testing. Once we confirm it works as intended I'll post it to the FreeNAS repo. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now