rawdrewage 14 Posted June 3, 2019 Share Posted June 3, 2019 4.1.1 crashes when I attempt to connect with web app or anything else. By crash I mean it shuts down (mono-sgen). It does not work at all. Log files show nothing at time of crash. Nothing is logged. The handling of freebsd sucks and now my setup doesn't work at all. Why are you releasing BROKEN software into the ports tree? You need new management on the Freebsd version. It just is not being handled. Thanks for wasting more of my time. What am I supposed to do go to the beta version now? Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted June 3, 2019 Share Posted June 3, 2019 It's probably worth a try to install the beta. The instructions are on the download page in the freebsd section. I've been running a slightly older beta flawlessly for the past month or so. Very happy with it. Link to comment Share on other sites More sharing options...
rawdrewage 14 Posted June 3, 2019 Author Share Posted June 3, 2019 Thanks but I should not have to. I am paying for this software and the port maintainer is not doing a good job, if at all. WTF! I am not paying to beta test their busted software. Why put a busted port into the ports tree? Has anyone been able to run 4.1.1 from the ports tree? Link to comment Share on other sites More sharing options...
Luke 37010 Posted June 3, 2019 Share Posted June 3, 2019 You already had an existing post saying this. Where was that? It will be easier to merge and keep existing conversations together. Thanks Link to comment Share on other sites More sharing options...
rawdrewage 14 Posted June 3, 2019 Author Share Posted June 3, 2019 Because I know someone will ask I ama running FreeBSD 11.2 nothing custom. I used portmaster to install portmaster -a which showed an update and I hit y to inst0all, service emby-server start, go to homepage and BOOM! Server shuts down. Easily replicated. Link to comment Share on other sites More sharing options...
rawdrewage 14 Posted June 3, 2019 Author Share Posted June 3, 2019 That other conversation got hijacked and the issue was never resolved at all. This ports tree thing happened in the past few days from your latest update to the ports tree and it is busted. So isn't this a new issue? Link to comment Share on other sites More sharing options...
makarai 108 Posted June 3, 2019 Share Posted June 3, 2019 Because I know someone will ask I ama running FreeBSD 11.2 nothing custom. I used portmaster to install portmaster -a which showed an update and I hit y to inst0all, service emby-server start, go to homepage and BOOM! Server shuts down. Easily replicated. quarterly or latest ports branch? Link to comment Share on other sites More sharing options...
rawdrewage 14 Posted June 3, 2019 Author Share Posted June 3, 2019 uname -a FreeBSD 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 04:32:14 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 1 Link to comment Share on other sites More sharing options...
raidflex 9 Posted June 3, 2019 Share Posted June 3, 2019 (edited) 4.1.1 crashes when I attempt to connect with web app or anything else. By crash I mean it shuts down (mono-sgen). It does not work at all. Log files show nothing at time of crash. Nothing is logged. The handling of freebsd sucks and now my setup doesn't work at all. Why are you releasing BROKEN software into the ports tree? You need new management on the Freebsd version. It just is not being handled. Thanks for wasting more of my time. What am I supposed to do go to the beta version now? I was able to successfully update to 4.1.1.0 and it does seem to be working without crashing. But I agree that if Emby is supporting Freebsd then they need to maintain the port properly. It should not take over a month when a new release is out until its in the ports. I am running Freenas 11.2U4, Emby is in stock jail. It's probably worth a try to install the beta. The instructions are on the download page in the freebsd section. I've been running a slightly older beta flawlessly for the past month or so. Very happy with it. While the beta may fix things, there should be a stable version that just works. Edited June 3, 2019 by raidflex Link to comment Share on other sites More sharing options...
Luke 37010 Posted June 3, 2019 Share Posted June 3, 2019 @@raidflex, it does not take us a month to submit new releases to FreeBSD ports. We submit them immediately, but sometimes it takes a little while for them to be accepted and merged in. Link to comment Share on other sites More sharing options...
raidflex 9 Posted June 3, 2019 Share Posted June 3, 2019 @@raidflex, it does not take us a month to submit new releases to FreeBSD ports. We submit them immediately, but sometimes it takes a little while for them to be accepted and merged in. 4.1.1 was released on April 30th and did not show up in ports until June 1st. That is over a month until its possible to upgrade the package. Link to comment Share on other sites More sharing options...
Luke 37010 Posted June 3, 2019 Share Posted June 3, 2019 4.1.1 was released on April 30th and did not show up in ports until June 1st. That is over a month until its possible to upgrade the package. I understand, but we submitted it to FreeBSD ports within 1-2 days of releasing. Link to comment Share on other sites More sharing options...
rawdrewage 14 Posted June 4, 2019 Author Share Posted June 4, 2019 I have NEVER had issues with using ports like I do with Emby and I have been using it for like 20 years. The ports maintainer is not doing a good job. Pointed question: Will Emby EVER get on the ball and handle FreeBSD correctly or are you just wasting all of our time? Link to comment Share on other sites More sharing options...
jinie 4 Posted June 4, 2019 Share Posted June 4, 2019 Wow... just wow. 4.1.1 was released 3 days ago, to the "current" branch, and 4.1.1.0_1 was released today. from https://www.freshports.org/multimedia/emby-server/ 01 Jun 2019 06:05:18 4.1.1.0 04 Jun 2019 14:17:39 4.1.1.0_1 Bad releases happen, and 3 days to receive feedback, fix errors, and release a new build isn't bad at all. Considering the ton of dependencies that Emby has, which all have to be "just the right version" for it to work, i'd say the maintainer is doing a great job. Also, when running on -current, YMMV. Personally i always make a snapshot of my jails before applying updates. If something breaks, i just roll back to the previous working state and be done with it. 1 Link to comment Share on other sites More sharing options...
specsnow 3 Posted June 5, 2019 Share Posted June 5, 2019 I upgraded to 4.1.1.0_1 from 4.0.2.0 using ports yesterday and had no issues at all. The only thing I noticed was that I had to manually restart the emby-server service after because it didn't happen automatically, but I'm not sure if it was even supposed to. Been about 24 hours and have no issues. The interface is noticeably faster but I haven't noticed any other changes. I'm running FreeNAS 11.2U3 and my jail is 11.2. All this jail runs is Emby and it's dependencies, plus python for an IPTV script download I use. Link to comment Share on other sites More sharing options...
metsuke 27 Posted June 6, 2019 Share Posted June 6, 2019 I have NEVER had issues with using ports like I do with Emby and I have been using it for like 20 years. The ports maintainer is not doing a good job. Pointed question: Will Emby EVER get on the ball and handle FreeBSD correctly or are you just wasting all of our time? We really should be grateful that Emby is supporting FreeBSD as well as they are. This is a complex piece of software and considering all the platforms that Emby supports with all its various dependencies, it is amazing that Emby works as well as it does (very well!) and that lesser populated platforms like FreeBSD aren't dropped. That being said, if you have constructive suggestions or experience with the ports submitting process that could help the Emby team, then we should divulge that information. In this last iteration, there was a 22 day delay which did not appear to be the fault of Emby: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237801 Emby team, Would earmarked donations for a faster or bare-metal build server be an available avenue for helping to solve this issue? 1 Link to comment Share on other sites More sharing options...
sluggo45 47 Posted June 6, 2019 Share Posted June 6, 2019 I don't know that the slow build VM is the reason for the delays when they happen. Other port maintainers encounter delays too, the whole thing is a volunteer-driven project (port maintenance in general) and, well, it happens. Keep in mind too that Emby still has to deal with Mono because there is no .Net Core/.Net5 equivalent for FreeBSD. Most of the other Emby server builds for OS's like Linux have long switched away from Mono, so we still have that legacy bit to deal with, and believe me, it is a big difference and adds complications. I'm helping test the new betas as they come out and we already caught one mono-specific bug (that was quickly fixed). Users on other platforms wouldn't have encountered it. Point being if you want to run Emby on FreeBSD, having a little patience and willingness to help along with a good attitude about problems and understanding that it is a smaller group of users goes a long way. Otherwise, stand up a Linux or Windows server, or run the docker. Link to comment Share on other sites More sharing options...
Luke 37010 Posted June 6, 2019 Share Posted June 6, 2019 We really should be grateful that Emby is supporting FreeBSD as well as they are. This is a complex piece of software and considering all the platforms that Emby supports with all its various dependencies, it is amazing that Emby works as well as it does (very well!) and that lesser populated platforms like FreeBSD aren't dropped. That being said, if you have constructive suggestions or experience with the ports submitting process that could help the Emby team, then we should divulge that information. In this last iteration, there was a 22 day delay which did not appear to be the fault of Emby: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237801 Emby team, Would earmarked donations for a faster or bare-metal build server be an available avenue for helping to solve this issue? Thanks for the offer. I think our build system for freebsd is in a good place now. Link to comment Share on other sites More sharing options...
jinie 4 Posted June 6, 2019 Share Posted June 6, 2019 or run the docker. I'm not that brave/stupid/foolish/clever/ignorant to dare run Docker on an internet facing machine. One thing is running Emby, and should someone find their way into that, i'm fairly confident that my jail configuration will keep them from doing any harm. Emby has read-only access to the media files, so worst case someone downloads all my files. Docker on the other hand.... runC alone, which is the lowest layer of virtualization that runs the docker container executable, has had 3 privilege escalation bugs so far the past year. All exploitable from inside the container. No thanks 1 Link to comment Share on other sites More sharing options...
sluggo45 47 Posted June 6, 2019 Share Posted June 6, 2019 I'm not that brave/stupid/foolish/clever/ignorant to dare run Docker on an internet facing machine. One thing is running Emby, and should someone find their way into that, i'm fairly confident that my jail configuration will keep them from doing any harm. Emby has read-only access to the media files, so worst case someone downloads all my files. Docker on the other hand.... runC alone, which is the lowest layer of virtualization that runs the docker container executable, has had 3 privilege escalation bugs so far the past year. All exploitable from inside the container. No thanks Not everyone runs Docker on public-facing machines and anyway my point wasn't "use Docker" it was "there are other options for Emby Server besides FreeBSD, if dealing with FreeBSD specific problems is irritating". I run in a FreeBSD jail myself and have for years but I'm not blind to the fact that it is a smaller community with its own unique ways of doing some things and with Emby in particular. Link to comment Share on other sites More sharing options...
Baenwort 97 Posted June 7, 2019 Share Posted June 7, 2019 I think part of the frustration was that before Emby went closed source the FreeBSD side of things worked a lot more smoothly as numerous people (and FreeBSD has a pretty vicious Open Source clique) who helped keep things going smoothly for people left for Jellyfin. I'm obviously not stepping up myself to volunteer for a closed source, for profit company myself but I'm still here as a user. You (Sluggo45) have been part of why this sub-forum has kept working and I for one salute you. 1 Link to comment Share on other sites More sharing options...
FreeBSD_Lover 13 Posted August 2, 2019 Share Posted August 2, 2019 We really should be grateful that Emby is supporting FreeBSD as well as they are. This is a complex piece of software and considering all the platforms that Emby supports with all its various dependencies, it is amazing that Emby works as well as it does (very well!) and that lesser populated platforms like FreeBSD aren't dropped. That being said, if you have constructive suggestions or experience with the ports submitting process that could help the Emby team, then we should divulge that information. In this last iteration, there was a 22 day delay which did not appear to be the fault of Emby: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237801 Emby team, Would earmarked donations for a faster or bare-metal build server be an available avenue for helping to solve this issue? I agree. And I haver never had an issue with Emby on FreeBSD. That just said I don't get all hot n excited and gotta have it now when a new release comes out. I too have been using software for 20 years and I learned 19 years ago that software can come with bugs. So I wait, and when I see that a release is a few weeks old, and the forum is not on fire I will then do the upgrade. That 'wisdom' has served me well, and that 'wisdom' with Emby has served me very well. Link to comment Share on other sites More sharing options...
Luke 37010 Posted September 30, 2019 Share Posted September 30, 2019 For non-beta users who wish to run the stable release, the suggested approach is installing the IOCage plugin: 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