FreeNAS plugin

[Eddie 12]

Let's say i am able to get emby running in a new plugin... is there an easy way to update it or will i have to repeat this 30 min process for every update?

[adrianwi 279]

Assuming you mean running in a jail, and not using the plugin, you can just update the emby port as soon as it's released.  Just a couple of commands and it shouldn't take more than 5-10 minutes

[Baenwort 118]

I thought Josh had done some additional customizations to fix things and add features that didn't translate to the FreeBSD port because they were FreeNAS specific that leveraged the ZFS file system?

[josh4trunks 70]

I thought Josh had done some additional customizations to fix things and add features that didn't translate to the FreeBSD port because they were FreeNAS specific that leveraged the ZFS file system?

I compile ffmpeg with the options mentioned in the emby for freebsd instructions. I also include a patch for mono for realtime filesystem monitoring.

[dolphin 17]

Thanks Josh, I just updated the FreeNAS Emby plug-in to 3.2.36.0!

 

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

[Eddie 12]

Ty josh

[Baenwort 118]

So I've started to learn more about FreeBSD that FreeNAS is based upon and have now signed up at Freeports.org to monitor when software I've installed gets updated. I've noticed that Josh always updates the pbi plug in after someone has updated the base FreeBSD package. 

 

@@Josh, is the bottle neck for our releases the version of the program on FreeBSD? If so is there somewhere we can donate to help speed that process? 

 

We're getting a rather large number of versions behind the main Emby and I've noticed an increase in issues with some of the apps that have been updating in concert with the main release when I use them with my FreeNAS emby server. I don't see the same issues when connecting to a test Windows server so I think it has something to do with the difference between expected server version and the one we have available.

[josh4trunks 70]

So I've started to learn more about FreeBSD that FreeNAS is based upon and have now signed up at Freeports.org to monitor when software I've installed gets updated. I've noticed that Josh always updates the pbi plug in after someone has updated the base FreeBSD package. 

 

@@Josh, is the bottle neck for our releases the version of the program on FreeBSD? If so is there somewhere we can donate to help speed that process? 

 

We're getting a rather large number of versions behind the main Emby and I've noticed an increase in issues with some of the apps that have been updating in concert with the main release when I use them with my FreeNAS emby server. I don't see the same issues when connecting to a test Windows server so I think it has something to do with the difference between expected server version and the one we have available.

No, I don't need to wait for the official port to update. I update my own local version of the port in my build environment and can do this as soon as a new version of emby is released.

 

I see only 2 (non-beta) releases since the FreeNAS version (3.2.36), 3.2.40 and 3.2.50. Is that what you consider the rather large amount? I just want to make sure I am understanding the versioning properly and not missing some.

 

I can work on getting 3.2.50 built/uploaded today, which would be available tomorrow. If I got notified of non-beta versions, that could help me getting new FreeNAS builds out when I have time. Posting to this thread would notify me by email. And if anyone did want to donate to keep me motivated to work on these updates here's a link.

https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=joshruehlig%40gmail%2ecom&item_name=JRuehlig%20Technologies

[Eddie 12]

Josh usually stays within a couple of releases of the whatever is the latest release for emby not a huge deal for me even though my OCD always wants the latest and greatest... i think the problem isnt josh but the update mechanism...

Emby updates for all major platforms like windows and linux and freebsd.... freenas isnt really included in that and has to be done manually via a plugin that relies soley on the available freetime of josh... freenas needs a better way to sync to the freebsd port instead of relying on plugins but they just cant seem to get rid of them...

I thought freenas was going to get rid of plugins for version 10 and 11 but they seem to stick around.

 

on a side note madsonic has an update dont really know what method to use to let you know in the future if you would prefer a pm or not

https://www.freshports.org/www/madsonic/

 

thanks in advance

[Luke 42077]

I think once there is a .NET Core runtime available for BSD, then we will look to revamp both the FreeBSD and FreeNAS packages. Thanks guys.

[dolphin 17]

I just made a donation to Josh for his work on the FreeNAS Emby plug-in. I believe work should be compensated.

 

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

[josh4trunks 70]

I appreciate it @@dolphin

 

@@Luke I was trying to run 3.2.50.0 using mono 4.6.1 and getting the below crash. Is there a minimum version of mono needed for emby 3.2.50.0? I was able to run emby 3.2.40.0 fine.

/usr/local/bin/mono /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server
Info Main: Emby
        Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server
        Operating system: Unix 9.3.0.0
        64-Bit OS: True
        64-Bit Process: True
        User Interactive: False
        Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Mon Jun 12 05:20:14 UTC 2017)
        Processor count: 1
        Program data path: /var/db/emby-server
        Application directory: /usr/local/lib/emby-server
* Assertion at threadpool-ms-io.c:344, condition `fd >= 0' not met

Stacktrace:


=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Abort trap (core dumped)

[Luke 42077]

@@josh4trunks is any emby log file created at all?

[Luke 42077]

To answer the question, mono 4.8.1 would be best if possible. Thanks.

[josh4trunks 70]

Yes a log file is created with the below only.

2017-12-09 10:14:21.371 Info Main: Emby
        Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server
        Operating system: Unix 9.3.0.0
        64-Bit OS: True
        64-Bit Process: True
        User Interactive: False
        Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Mon Jun 12 05:20:14 UTC 2017)
        Processor count: 1
        Program data path: /var/db/emby-server
        Application directory: /usr/local/lib/emby-server

Ok, 4.8.1 is available for FreeBSD... but I have been trying to keep this patch which enables filesystem scanning on FreeBSD.

https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176608&action=diff

 

I'll see if 4.8.1 works, and try updating this patch. This release will take me longer then normal =/

[Baenwort 118]

No, I don't need to wait for the official port to update. I update my own local version of the port in my build environment and can do this as soon as a new version of emby is released.

 

I see only 2 (non-beta) releases since the FreeNAS version (3.2.36), 3.2.40 and 3.2.50. Is that what you consider the rather large amount? I just want to make sure I am understanding the versioning properly and not missing some.

 

I can work on getting 3.2.50 built/uploaded today, which would be available tomorrow. If I got notified of non-beta versions, that could help me getting new FreeNAS builds out when I have time. Posting to this thread would notify me by email. And if anyone did want to donate to keep me motivated to work on these updates here's a link.

https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=joshruehlig%40gmail%2ecom&item_name=JRuehlig%20Technologies

 

I didn't realize that it was only two revisions. I've only recently started paying attention to Emby's versioning and since I did it seemed to increment in smaller ones than that. I had thought it was 14 different versions between as it seemed to be going 3.2.19 to 3.2.20 and 3.2.26 to 3.2.27 to 3.2.30 and I thought I had just missed some version in between as I don't expect a volunteer like Josh to immediately rush to implement.

[Luke 42077]

Yes a log file is created with the below only.

2017-12-09 10:14:21.371 Info Main: Emby
        Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server
        Operating system: Unix 9.3.0.0
        64-Bit OS: True
        64-Bit Process: True
        User Interactive: False
        Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Mon Jun 12 05:20:14 UTC 2017)
        Processor count: 1
        Program data path: /var/db/emby-server
        Application directory: /usr/local/lib/emby-server

Ok, 4.8.1 is available for FreeBSD... but I have been trying to keep this patch which enables filesystem scanning on FreeBSD.

https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176608&action=diff

 

I'll see if 4.8.1 works, and try updating this patch. This release will take me longer then normal =/

 

A tester has helped narrow it down to some startup code that uses the Mono.Posix library to make syscalls to query the OS information. This allows us to differentiate between freebsd and linux. The problem is I have no explanation for the sudden failure because the code hasn't changed, nor have the included libraries.

 

So I am just going to remove it and have you guys add a command line param to specify freebsd customizations from the outside in. Might as well do it now because the library will not be usable anyway down the road with .net core.

[josh4trunks 70]

A tester has helped narrow it down to some startup code that uses the Mono.Posix library to make syscalls to query the OS information. This allows us to differentiate between freebsd and linux. The problem is I have no explanation for the sudden failure because the code hasn't changed, nor have the included libraries.

 

So I am just going to remove it and have you guys add a command line param to specify freebsd customizations from the outside in. Might as well do it now because the library will not be usable anyway down the road with .net core.

great, once there is a stable version with this update i can build an updated emby plugin for freenas.

[Luke 42077]

great, once there is a stable version with this update i can build an updated emby plugin for freenas.

 

One small adjustment will be needed to the startup command line. Please see my comments here:

https://github.com/MediaBrowser/Emby/issues/3062

 

Thanks.

[eraser8 55]

Hi guys,

 

I know you working hard on that to improve this. I hope you will be able to find the way to fix this to be able to upgrade to the last version!

 

Thanks a lot

[Luke 42077]

Hi guys,

 

I know you working hard on that to improve this. I hope you will be able to find the way to fix this to be able to upgrade to the last version!

 

Thanks a lot

 

We have it figured out, thanks

[eraser8 55]

We have it figured out, thanks

 

Cool! Thanks! So, can we hope to have plugin updates in the same time than others?

 

THanks

[josh4trunks 70]

Emby version 3.2.60.0 update is in my local repo, and should be available from the public FreeNAS repo tomorrow.

Thanks for everyone's patience on this one.

[dolphin 17]

Emby version 3.2.60.0 update is in my local repo, and should be available from the public FreeNAS repo tomorrow.

Thanks for everyone's patience on this one.

Thanks Josh, that is a Christmas gift we all appreciate!

 

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

[Luke 42077]

Thanks @@josh4trunks