FreeBSD Package

January 28, 2019

error message?

you need to be in the jails shell

pkg install mono libass fontconfig freetype2 fribidi gnutls iconv opus samba48 sqlite3 libtheora libva libvorbis webp libx264 libzvbi librawpkg

pkg install mono libass fontconfig freetype2 fribidi gnutls iconvopus samba48 sqlite3 libtheora libva libvorbis webp libx264 libzvbi librawpkg

The package management tool is not yet installed on your system.

Do you want to fetch and install it now? [y/N]: y

Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly, please wait...

Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done

[Emby] Installing pkg-1.10.5_5...

[Emby] Extracting pkg-1.10.5_5: 100%

Updating FreeBSD repository catalogue...

pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory

[Emby] Fetching meta.txz: 100% 944 B 0.9kB/s 00:01

[Emby] Fetching packagesite.txz: 100% 6 MiB 516.3kB/s 00:13

Processing entries: 100%

FreeBSD repository update completed. 32373 packages processed.

All repositories are up to date.

Updating database digests format: 100%

pkg: No packages available to install matching 'librawpkg' have been found in the repositories

Edit: # ifconfig

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

ether ::a6:f2:3a:c5

hwaddr ::a6:f2:3a:c5

inet 192.168.1.33 netmask 0xffffff00 broadcast 192.168.1.255

nd6 options=9<PERFORMNUD,IFDISABLED>

media: Ethernet autoselect (1000baseT <full-duplex>)

status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>

inet6 ::1 prefixlen 128

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

inet 127.0.0.1 netmask 0xff000000

nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

groups: lo

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

ether :e0:be:22:00

nd6 options=1<PERFORMNUD>

groups: bridge

id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15

maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200

root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0

member: vnet0:6 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

ifmaxaddr 0 port 5 priority 128 path cost 2000

member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

ifmaxaddr 0 port 1 priority 128 path cost 20000

vnet0:6: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

description: associated with jail: Emby

options=8<VLAN_MTU>

ether ::60:c0:af:79

hwaddr ::10:00:05:0a

nd6 options=1<PERFORMNUD>

media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)

status: active

groups: epair

Edited January 28, 2019 by hjason7812

January 28, 2019

Execute the following command from the jail's command line:

echo '# $FreeBSD: releng/11.1/etc/pkg/FreeBSD.conf 320745 2017-07-06 17:22:33Z gjb $\
#\
# To disable this repository, instead of modifying or removing this file,\
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:\
#\
#   mkdir -p /usr/local/etc/pkg/repos\
#   echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf\
#\
\
FreeBSD: {\
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",\
  mirror_type: "srv",\
  signature_type: "fingerprints",\
  fingerprints: "/usr/share/keys/pkg",\
  enabled: yes\
}' > /usr/local/etc/pkg/repos/FreeBSD.conf

You may also need to make the directory first:

mkdir -p /usr/local/etc/pkg/repos

And after that try to install the packages again.

Edited January 28, 2019 by quicktrick

January 28, 2019

Execute the following command from the jail's command line:

echo '# $FreeBSD: releng/11.1/etc/pkg/FreeBSD.conf 320745 2017-07-06 17:22:33Z gjb $\
#\
# To disable this repository, instead of modifying or removing this file,\
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:\
#\
#   mkdir -p /usr/local/etc/pkg/repos\
#   echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf\
#\
\
FreeBSD: {\
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",\
  mirror_type: "srv",\
  signature_type: "fingerprints",\
  fingerprints: "/usr/share/keys/pkg",\
  enabled: yes\
}' > /usr/local/etc/pkg/repos/FreeBSD.conf

You may also need to make the directory first:

mkdir -p /usr/local/etc/pkg/repos

And after that try to install the packages again.

Didn't work

All repositories are up to date.

pkg: No packages available to install matching 'librawpkg' have been found in the repositories

January 28, 2019

pkg install mono libass fontconfig freetype2 fribidi gnutls iconvopus samba48 sqlite3 libtheora libva libvorbis webp libx264 libzvbi librawpkg

The package management tool is not yet installed on your system.

Do you want to fetch and install it now? [y/N]: y

Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly, please wait...

Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done

[Emby] Installing pkg-1.10.5_5...

[Emby] Extracting pkg-1.10.5_5: 100%

Updating FreeBSD repository catalogue...

pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory

[Emby] Fetching meta.txz: 100%    944 B   0.9kB/s    00:01

[Emby] Fetching packagesite.txz: 100%    6 MiB 516.3kB/s    00:13

Processing entries: 100%

FreeBSD repository update completed. 32373 packages processed.

All repositories are up to date.

Updating database digests format: 100%

pkg: No packages available to install matching 'librawpkg' have been found in the repositories

Edit: # ifconfig

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

        options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>

        ether ::a6:f2:3a:c5

        hwaddr ::a6:f2:3a:c5

        inet 192.168.1.33 netmask 0xffffff00 broadcast 192.168.1.255

        nd6 options=9<PERFORMNUD,IFDISABLED>

        media: Ethernet autoselect (1000baseT <full-duplex>)

        status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>

        inet6 ::1 prefixlen 128

        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

        inet 127.0.0.1 netmask 0xff000000

        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

        groups: lo

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

        ether :e0:be:22:00

        nd6 options=1<PERFORMNUD>

        groups: bridge

        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15

        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200

        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0

        member: vnet0:6 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

                ifmaxaddr 0 port 5 priority 128 path cost 2000

        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>

                ifmaxaddr 0 port 1 priority 128 path cost 20000

vnet0:6: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

        description: associated with jail: Emby

        options=8<VLAN_MTU>

        ether ::60:c0:af:79

        hwaddr ::10:00:05:0a

        nd6 options=1<PERFORMNUD>

        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)

        status: active

        groups: epair

Eureka, you got your vnet adapter

I messed up the copy and past earlier here are the correct ones execute within the emby jail:

#enter the jail shell
pkg install mono libass fontconfig freetype2 fribidi gnutls iconv opus samba48 sqlite3 libtheora libva libvorbis webp libx264 libzvbi libraw
pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.0.1.0/emby-server-freebsd_4.0.1.0_amd64.txz 

sysrc -f /etc/rc.conf emby_server_enable="YES"
service emby-server start 2>/dev/null
restart jail

After that worked please e try these:

freenas shell

cd /tmp
wget https://raw.githubusercontent.com/ma-karai/iocage-plugin-emby/master/emby-server.json
iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'master'

Edited April 26, 2019 by makarai

January 28, 2019

the package is downloading now, hopefully it all goes without a hitch..

Edited January 28, 2019 by hjason7812

January 28, 2019

I think the second method should now also work. Give it a try afterwards. I am guessing the Create Jail from hand method fixed some borked network configurations within freenas.

January 28, 2019

I think the second method should now also work. Give it a try afterwards. I am guessing the Create Jail from hand method fixed some borked network configurations within freenas.

The pkg install is now installing 93 packages i guess..

January 28, 2019

normal, the "by hand jail" is very bare bones

Edited January 28, 2019 by makarai

January 28, 2019

i'm doing the second method now to see if it works.. i hope i don't have to go through this every single time i have to update emby.

January 28, 2019

nope, as i said a couple of times before, freenas networking is at fault and not really emby. If you get your jail up and running updates will be easy.

January 28, 2019

normal, the "by hand jail" is very bare bones

ok i have a new install called emby_server but where it says version is has N/A

January 28, 2019

ok i have a new install called emby_server but where it says version is has N/A

thats normal, that only works for official plugins that you can find in the plugins part.

But its good news that you have now a functioning emby server

January 28, 2019

thats normal, that only works for official plugins that you can find in the plugins part.

But its good news that you have now a functioning emby server

Yes i just set it up and it is the new version.. thank you so much for the help.. i would've never got this done lol..

Thank you

January 28, 2019

Yes i just set it up and it is the new version.. thank you so much for the help.. i would've never got this done lol..

Thank you

no biggie.

January 28, 2019

nvm delete please

Edited January 28, 2019 by hjason7812

January 28, 2019

nvm delete please

just restart the jail

check also this post for question regarding updating or restarting or similar

https://emby.media/community/index.php?/topic/60971-new-freenas-package-for-testing/page-7&do=findComment&comment=619899

Edited January 28, 2019 by makarai

February 5, 2019

First let me apologize if this should be a separate new thread, but I think this is the right place.

I'm a total noob when it comes to all this stuff (FreeNAS, Emby, Kodi, everything). As such am still on FreeNAS 11.1 running Emby from the plugin (so 3.3.1.0). I have NEVER installed/upgraded Emby without doing the simple plugin method. And yes, things are getting nasty since my Kodi for Emby clients are on the latest releases.

So I know I must upgrade and do it the right way as described in this thread. I have read and reread this thread (as well as others) but again I'm just not knowledgeable enough so I'm very concerned and want confirmation I'm doing this right.

I'm fine (and would prefer) to start from scratch and do a fresh new install of the Emby server so that it's clean (and then add my libraries). I have done upgrades on FreeNAS before and do feel comfortable with upgrading from 11.1 to 11.2 so I'm planning on that and NOT a new fresh install and new ZFS pool.

So I believe these are the correct steps to take:

1) Upgrade my FreeNAS 11.1 to 11.2 Stable (I see the latest stable available is "11.2 Release U1")

This will maintain my pool and should have no impact on the data within that pool. My data is backed up (mainly just movies/tvshows anyway), so I have no worries about losing data if something bad happens.

2) Perform a clean fresh install of Emby following "Emby Server for FreeBSD" instructions on the main Emby website (which shows using the 4.0.1.0 version currently)

3) Connect my various clients (ShieldTV and Amazon FireTV boxes) to this new install of the server

All help is greatly appreciated.

February 5, 2019

First let me apologize if this should be a separate new thread, but I think this is the right place.

I'm a total noob when it comes to all this stuff (FreeNAS, Emby, Kodi, everything). As such am still on FreeNAS 11.1 running Emby from the plugin (so 3.3.1.0). I have NEVER installed/upgraded Emby without doing the simple plugin method. And yes, things are getting nasty since my Kodi for Emby clients are on the latest releases.

So I know I must upgrade and do it the right way as described in this thread. I have read and reread this thread (as well as others) but again I'm just not knowledgeable enough so I'm very concerned and want confirmation I'm doing this right.

I'm fine (and would prefer) to start from scratch and do a fresh new install of the Emby server so that it's clean (and then add my libraries). I have done upgrades on FreeNAS before and do feel comfortable with upgrading from 11.1 to 11.2 so I'm planning on that and NOT a new fresh install and new ZFS pool.

So I believe these are the correct steps to take:

1) Upgrade my FreeNAS 11.1 to 11.2 Stable (I see the latest stable available is "11.2 Release U1")

This will maintain my pool and should have no impact on the data within that pool. My data is backed up (mainly just movies/tvshows anyway), so I have no worries about losing data if something bad happens.

2) Perform a clean fresh install of Emby following "Emby Server for FreeBSD" instructions on the main Emby website (which shows using the 4.0.1.0 version currently)

3) Connect my various clients (ShieldTV and Amazon FireTV boxes) to this new install of the server

All help is greatly appreciated.

From what i was told it is better to start from scratch on emby. Because the new version is totally different from the old.

I had trouble getting it to work with the code for a while until i reset the network on the server console of freenas.. once i did that i was able to install the new version and repositories..

Just look at my posts and Makarai's on the last few pages and you will get it done. It took us 2 days to finally get it installed and working. But only do most of this if you are having trouble like i was..

February 6, 2019

As soon as we have the ports tree updated it will be much easier. Thanks guys.

February 6, 2019

From what i was told it is better to start from scratch on emby. Because the new version is totally different from the old.

I had trouble getting it to work with the code for a while until i reset the network on the server console of freenas.. once i did that i was able to install the new version and repositories..

Just look at my posts and Makarai's on the last few pages and you will get it done. It took us 2 days to finally get it installed and working. But only do most of this if you are having trouble like i was..

Thanks hjason7812

Yep, literally created bookmarks of all Makarai's posts to review as I go thru this. Not too worried about the emby server side of things, since as you mention better to do from scratch, so worst case I redo it a few times, just wanted to make sure my generic steps are correct and not missing anything.

Thanks again.

February 6, 2019

No problem gmacman

February 6, 2019

I wondered the same thing when making the jump from warden to iocage. I installed via plugin (3.5.3.0) and then continued to upgrade manually. The only additional package you need to download is libraw. I am now running 4.0.1.0 without issue.

There were initially some ffmpeg issues on the first upgrade, but the devs have those issues handled now. Simple solution is install the plugin, run pkg install libraw, then run the upgrade command (I’m sure it’s on several threads, including several posts by makarai).

Of note, if you have Emby premiere, install the backup and restore plugin and you can preserve most of your server settings. Saved me a TON of time.

Edited February 6, 2019 by gbarone123

February 6, 2019

I do need to update what I said in my original post to say that since I am running FreeNAS I did follow makarai's "Simple Installation" from post #202 instead of what I wrote for my step 2 (...following "Emby Server for FreeBSD" instructions on the main Emby website).

And that installed the iocage jail and emby server perfectly for my newly updated FreeNAS 11.2.

Again, I'd like to thank makarai and hjason7812 as well as others. When you're like me and all this stuff is like a foreign language you've never even heard before, it's very gratifying when things work out fairly easily.

February 6, 2019

Glad it all worked out for you gmacman.

February 8, 2019

As soon as we have the ports tree updated it will be much easier. Thanks guys.

Is this why beta builds stalled after 4.1.0.4?

FreeBSD Package

Recommended Posts

hjason7812 26

Link to comment

Share on other sites

quicktrick 0

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

makarai 108

Link to comment

Share on other sites

gmacman 3

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

Luke 38108

Link to comment

Share on other sites

gmacman 3

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

gbarone123 4

Link to comment

Share on other sites

gmacman 3

Link to comment

Share on other sites

hjason7812 26

Link to comment

Share on other sites

unhooked 17

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in