Jump to content

FreeNAS plugin


Luke

Recommended Posts

makarai

@@Luke

 

At present the Emby-Server Stable 5.3.5.0 will not properly install on Freenas-Stable release a couple of days ago.

https://www.freenas....-2-has-arrived/

 

The reason seems to be the FreeBSD version used in your installation json (11.1_p11) if changed to 11.2 the installation functions properly! 

 

Secondly could you create a beta branch on your repository and change it to whatever i have so you could have a stable version installation on your repo and a beta version installation via

iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'master' 
# or 
iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server-beta.json --branch 'beta'
Edited by makarai
  • Like 1
Link to comment
Share on other sites

  • 2 months later...

I have not had success using emby on freenas 11.2 for a while so i have been using a second computer with ubuntu on it running great...

Today i updated my FreeNAS 11.2-U2 and tried the instructions mentioned by @@makarai and got this error

Any ideas?

root@freenas:~ # cd /tmp
root@freenas:/tmp # wget https://raw.githubusercontent.com/bott0r/iocage-plugin-emby/master/emby-server.json
--2019-02-18 23:32:57--  https://raw.githubusercontent.com/bott0r/iocage-plugin-emby/master/emby-server.json
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 199.232.32.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|199.232.32.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 798 [text/plain]
Saving to: ‘emby-server.json’

emby-server.json                                                    100%[==================================================================================================================================================================>]     798  --.-KB/s    in 0s      

2019-02-18 23:32:57 (91.6 MB/s) - ‘emby-server.json’ saved [798/798]

root@freenas:/tmp # iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'master'
Plugin: emby-server
  Official Plugin: False
  Using RELEASE: 11.2-RELEASE
  Using Branch: master
  Post-install Artifact: https://github.com/bott0r/iocage-plugin-emby.git
  These pkgs will be installed:
    - lang/mono
    - multimedia/libass
    - x11-fonts/fontconfig
    - print/freetype2
    - converters/fribidi
    - security/gnutls
    - converters/iconv
    - audio/opus
    - net/samba48
    - databases/sqlite3
    - multimedia/libtheora
    - multimedia/libva
    - audio/libvorbis
    - graphics/webp
    - multimedia/libx264
    - graphics/libraw
    - devel/libzvbi
Exception: UnboundLocalError:local variable 'bridge_cmd' referenced before assignment occured, destroyed emby-server.
root@freenas:/tmp # 

Link to comment
Share on other sites

makarai

Hey @@Eddie,

 

I have not yet update to U2, will do so soon. In the mean time could you:

  • install the irrsi from the plugin catalog and check if that properly installs. (leave it installed, for the time being) 
  • send me the print out from ifconfig
  • try installing Emby in a jail from scratch: codebox

 

 

Create an empty jail -> use GUI and enter jail shell

#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.2.0/emby-server-freebsd_4.0.2.0_amd64.txz 

sysrc -f /etc/rc.conf emby_server_enable="YES"
service emby-server start 2>/dev/null
restart jail
Edited by makarai
Link to comment
Share on other sites

hjason7812

Looks like he's having the same issue i had. I had to reset the network settings from the freenas console ( direct from freenas server via monitor)

Link to comment
Share on other sites

hjason7812

updated freenas to the new update and now emby doesn't work.. i get an error called unbound loacal error..

 

local variable 'bridge_cmd' referenced before assignment

 

Error: concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/process.py", line 175, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 128, in main_worker
    res = loop.run_until_complete(coro)
  File "/usr/local/lib/python3.6/asyncio/base_events.py", line 468, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 88, in _run
    return await self._call(f'{service_name}.{method}', serviceobj, methodobj, params=args, job=job)
  File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 81, in _call
    return methodobj(*params)
  File "/usr/local/lib/python3.6/site-packages/middlewared/worker.py", line 81, in _call
    return methodobj(*params)
  File "/usr/local/lib/python3.6/site-packages/middlewared/schema.py", line 668, in nf
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/jail.py", line 581, in start
    iocage.start()
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/iocage.py", line 1663, in start
    callback=self.callback
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 66, in __init__
    self.__start_jail__()
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 415, in __start_jail__
    vnet_err = self.start_network(vnet)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 598, in start_network
    err = self.start_network_interface_vnet(nic, net_configs, jid)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 624, in start_network_interface_vnet
    membermtu = self.find_bridge_mtu(bridge)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_start.py", line 975, in find_bridge_mtu
    su.check_call(bridge_cmd, stdout=su.PIPE, stderr=su.PIPE)
UnboundLocalError: local variable 'bridge_cmd' referenced before assignment
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 165, in call_method
    result = await self.middleware.call_method(self, message)
  File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1141, in call_method
    return await self._call(message['method'], serviceobj, methodobj, params, app=app, io_thread=False)
  File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1078, in _call
    return await self._call_worker(serviceobj, name, *args)
  File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1105, in _call_worker
    job,
  File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1036, in run_in_proc
    return await self.run_in_executor(self.__procpool, method, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 1021, in run_in_executor
    return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
UnboundLocalError: local variable 'bridge_cmd' referenced before assignment
 

 

 

I restarted emby and freenas server but i still get this error when trying to manage emby

Link to comment
Share on other sites

hjason7812

@@hjason7812

Literally the post above you talks about this fix

i fixed it by rolling back the update. the new update breaks the network port so i went ahead and rolled it back to the previous update and deleted the new one.. i don't have time for bs updates from freenas

  • Like 1
Link to comment
Share on other sites

makarai
/bin/sh -c 'export JAILS="$(iocage list -h | cut -f 2)"; for jail in $JAILS; do iocage set vnet_default_interface=auto $jail; done; iocage set vnet_default_interface=auto default'

For Reference to fix the missing bridge, requires a restart.

 

or 

 

Stop all jails, edit one jail's properties, go to Network Properties, set vnet_default_interface to auto, from none. Save - you may need to uncheck and recheck DHCP Autoconfigure in Basic before Save becomes available. Start your jail(s).

Edited by makarai
Link to comment
Share on other sites

gbarone123

Freenas 11.2u2 has a bug where it breaks VNET in iocage jails, though the jails do start. Strangely, existing warden jails seem to be unaffected. You should roll back to u1 until they get this fixed. It’s not an Emby issue, it’s a freenas issue.

Link to comment
Share on other sites

sluggo45

I was the one that opened the bug for U2's VNET problem. It's easy to fix:

 

Update to U2.

 

In the shell (either ssh or open the console from the WebUI) run the following:

/bin/sh -c 'export JAILS="$(iocage list -h | cut -f 2)"; for jail in $JAILS; do iocage set vnet_default_interface=auto $jail; done; iocage set vnet_default_interface=auto default'

Done.

 

U2 fixed one problem with VNET not correctly picking the right interface but introduced another by not resetting previously created jails. The problem boils down to VNET not being set to auto select for users who didn't specify an interface. The above command corrects that, and will also fix it for new jails you add/modify.

 

The permanent fix is slated for U3 which is 3 weeks away currently if you prefer to wait.

 

Note: The above command will only work if you are on U2 - don't try to run it on U1 or lower before upgrading. Upgrade first.

 

Rolling back in Freenas is dead simple if you mess up, just pick the earlier image at boot.

Edited by sluggo45
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
lolzor

4.1.0.12 is asking about whether you want to ignore a kernel mismatch (i'm running 11.2 U2.1)  - and after you go ahead the emby crashes and doesn't recover even if you revert to a previous version. The only fix so far was to delete the jail and recreate and reinstall emby 3.5.3.0 .

Edited by lolzor
Link to comment
Share on other sites

hjason7812

i have a problem with emby now not working at all.. I am on 11.2 u1 i can't go to emby at all for some reason, just says unable to connect. i have restarted the server and emby but still doesn't work..

 

  • Like 1
Link to comment
Share on other sites

i have a problem with emby now not working at all.. I am on 11.2 u1 i can't go to emby at all for some reason, just says unable to connect. i have restarted the server and emby but still doesn't work..

 

How did you install the server?

Link to comment
Share on other sites

hjason7812

Through shell.. everything worked fine until today it just stopped working on every device can't even go to the url

Edited by hjason7812
Link to comment
Share on other sites

eraser8

How did you install the server?

 

Hi Luke,

 

I do have the same sympthom. I was on 4.1.0.8 and update it by the same way I did from couple of month now. "Pkg add -f .....". I also did try to install the latest version 4.1.0.12 yesterday night and I got the same error than above. I was able to start the server but no movie was playing. I did rollback my instal to 4.1.0.10 and now it's working just like before (4.1.0.8)

 

Thansk

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...