Baenwort 97 Posted April 28, 2019 Share Posted April 28, 2019 @@Baenwort, Here is something to try. it'll sound stupid but worked for me just now. repeat pkg update pkg upgrade that should now install everything you need. You can check by trying to pkg install samba48 and pkg install ImageMagick6, but both should now be there. then service emby-server stop (it may already be stopped) pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.2.0.1/emby-server-freebsd11_4.2.0.1_amd64.txz When I tried to start the emby-server from within the jail after adding it I got an error message So, in the gui go to your jail, stop it, and restart it then, in the gui, go to plugins, installed and stop and restart the plugin. Then see if you can go to the management page. It just worked for me when I had some issue earlier. That particular jail had emby-server version 4.0.2.0 beforehand I'm willing to try anything. My attempt to follow @@sluggo45's method but this time to leap to the beta 4.2.0.1 did not improve things as I still get the mono crash. Using your method I get this error with your first command (I suspect you don't mean it as a command but just incase I tried it that way): root@emby_2:~ # repeat pkg update repeat: Badly formed number. Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 28, 2019 Share Posted April 28, 2019 (edited) I'm willing to try anything. My attempt to follow @@sluggo45's method but this time to leap to the beta 4.2.0.1 did not improve things as I still get the mono crash. Using your method I get this error with your first command (I suspect you don't mean it as a command but just incase I tried it that way): root@emby_2:~ # repeat pkg update repeat: Badly formed number. Sorry, I should have been more clear. I meant just to repeat the update so pkg update pkg upgrade another time. I think something happened to ports recently that seems to be fixed. Samba48 is added to the update/upgrade process now and I had to add it specifically a few days ago. There may be additional entries that make it through the process today that did not a few days ago. ETA: I just updated the server in my main jail and all worked well. Hopefully this means whatever was causing issues over the past few days has been resolved and you will be up and running again soon. Edited April 28, 2019 by PhilWhite Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 28, 2019 Share Posted April 28, 2019 (edited) Well, I take it back. Everything installed, the server starts, and I'm getting playback errors on most of my video data now. I take it this is an issue with ffmpeg? Edited April 28, 2019 by PhilWhite Link to comment Share on other sites More sharing options...
Luke 37065 Posted April 28, 2019 Share Posted April 28, 2019 Well, I take it back. Everything installed, the server starts, and I'm getting playback errors on most of my video data now. I take it this is an issue with ffmpeg? Server log? Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 28, 2019 Share Posted April 28, 2019 Yes, sorry, was trying to figure out what was going on. One minute and will post. Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 28, 2019 Share Posted April 28, 2019 (edited) @@Luke, Sorry I didn't post the logs straight away. And saying most are not playing is a huge overstatement; I sampled a few with many of those showing errors and few playing fine. It looks like most are playing well. Most of the error messages for recordings not playing report: Shared object "libsmbclient.so.0" not found, required by "libavformat.so.58 will upload in a few minutes, but is there an easy way to add this? Haven't had a chance to google it yet. ETA: <logs deleted> And one other thing that I can report -- I was playing with a couple test jails, one of which I deleted and restarted with makarai's github page. This created the jail but did not successfully install the server. When I installed the server (version 4.2.0.1) after pkg update and upgrade, all seems to be working. I could not get TV to direct stream with my old jail, but with the new jail it does. Videos that would not play in the old jail work fine in the new jail. So, I am guessing that what I may need to do is update my freenas version in the jail. I'll let you know if that has any effect. I think makarai was using the latest freenas version for jail creation, but I have avoided updates lately since I'm not certain about freenas issues with updates. I am using freenas 11.2, but I think I am still on U1. Edited April 30, 2019 by PhilWhite Link to comment Share on other sites More sharing options...
Baenwort 97 Posted April 28, 2019 Share Posted April 28, 2019 (edited) I tried your method PhilWhite and like the earlier attempts to update from 4.0.2.0_1 they go fine to the dashboard and all functions accessible to the dashboard but as soon as the webapp navigates to the home page of the library I get the mono crash. I think something that was done in one of the betas between the last stable (4.0.2.0_1) and the beta version that Sluggo45 started from included .db changes that aren't being allowed for in the upgrade to 4.1.0.26 or 4.2 betas. It must be something that makes mono crash when trying to serve up the library view home page. I recall mention of the 4.1 beta's having big changes in the dbs. There was a warning with the 4.1 beta's that you couldn't go back due to some changes made that resulted in not being able to revert to the stable channel until it caught up. Edited April 28, 2019 by Baenwort Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 28, 2019 Share Posted April 28, 2019 I tried your method PhilWhite and like the earlier attempts to update from 4.0.2.0_1 they go fine to the dashboard and all functions accessible to the dashboard but as soon as the webapp navigates to the home page of the library I get the mono crash. I think something that was done in one of the betas between the last stable (4.0.2.0_1) and the beta version that Sluggo45 started from included .db changes that aren't being allowed for in the upgrade to 4.1.0.26 or 4.2 betas. It must be something that makes mono crash when trying to serve up the library view home page. I recall mention of the 4.1 beta's having big changes in the dbs. There was a warning with the 4.1 beta's that you couldn't go back due to some changes made that resulted in not being able to revert to the stable channel until it caught up. Sorry, wish it worked. All is well on my end aside from a few videos that are not playing -- maybe I should have gone with the stable release.... Link to comment Share on other sites More sharing options...
Baenwort 97 Posted April 28, 2019 Share Posted April 28, 2019 (edited) Sorry, wish it worked. All is well on my end aside from a few videos that are not playing -- maybe I should have gone with the stable release.... Did you use ZFS to take a snapshot before you upgraded? I always do so before upgrades and it's been handy for a quick role back via the FreeNAS GUI and restart of the upgrade process. Edited April 28, 2019 by Baenwort Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 28, 2019 Share Posted April 28, 2019 Did you use ZFS to take a snapshot before you upgraded? I always do so before upgrades and it's been handy for a quick role back via the FreeNAS GUI and restart of the upgrade process. No, but will do in future. I have what looks like a fully functioning server with the other jail, so all is good. Link to comment Share on other sites More sharing options...
Baenwort 97 Posted April 29, 2019 Share Posted April 29, 2019 So I was thinking while getting pelted with snowballs. I'm running the latest pkg repository. For those who have successfully upgraded from 4.0.2.0 to either 4.1.0.26 or 4.2 are you running the quarterly repository? In the move to FreeNAS 11.2 they switched to the quarterly repository and I wonder if the Emby build target is set to the quarterly repository instead of the latest? Link to comment Share on other sites More sharing options...
Luke 37065 Posted April 29, 2019 Share Posted April 29, 2019 Yea you need to use the correct emby package for your version of FreeBSD, and then you also need your FreeBSD installation configured for latest packages. Keep in mind you can always install with freebsd ports, and that is the preferred install method unless you want to use the beta package. Link to comment Share on other sites More sharing options...
Baenwort 97 Posted April 29, 2019 Share Posted April 29, 2019 Rats, that kills my last idea. I'm now hoping you can help me figure out what it is about updating from 4.0.2.0 that is causing this crash issue only when entering the library homepage. I tried creating a fresh emby jail and restoring but FreeNAS has a current bug in 11.2-U3 that prevents the creation of new mount points for jails that have file paths that use a space in the zVol name. Unfortunately I named my 'TV Shows' zVol with a space in it. Older versions of FreeNAS would let you use /040 to replace the space (which is how my current Emby jail works) but currently new mounts are not accepting this or any other work around. It's scheduled to be fixed ~maybe~ in July. (https://jira.ixsystems.com/browse/NAS-101252 is their bug tracker) This means I can either: 1) Rebuild my NAS from scratch to remove all use of space as a character in names (using my backup as a working offload instead of a backup) 2) Find a way to update Emby stable to Emby Stable (maybe useful when you get the FreeNAS/freshports version updated to solve this first) 3) Hang on 4.0.2.0 for a few months and hope no security vulnerabilities exist.... 4) there is no four due to FreeNAS bug I'd like to keep up with the improvements in Emby but I can't troubleshoot this server crash without help. Tell me what information you need or logs to send to whom ever manages the crash cause and I will. Link to comment Share on other sites More sharing options...
Luke 37065 Posted April 29, 2019 Share Posted April 29, 2019 Rats, that kills my last idea. I'm now hoping you can help me figure out what it is about updating from 4.0.2.0 that is causing this crash issue only when entering the library homepage. I tried creating a fresh emby jail and restoring but FreeNAS has a current bug in 11.2-U3 that prevents the creation of new mount points for jails that have file paths that use a space in the zVol name. Unfortunately I named my 'TV Shows' zVol with a space in it. Older versions of FreeNAS would let you use /040 to replace the space (which is how my current Emby jail works) but currently new mounts are not accepting this or any other work around. It's scheduled to be fixed ~maybe~ in July. (https://jira.ixsystems.com/browse/NAS-101252 is their bug tracker) This means I can either: 1) Rebuild my NAS from scratch to remove all use of space as a character in names (using my backup as a working offload instead of a backup) 2) Find a way to update Emby stable to Emby Stable (maybe useful when you get the FreeNAS/freshports version updated to solve this first) 3) Hang on 4.0.2.0 for a few months and hope no security vulnerabilities exist.... 4) there is no four due to FreeNAS bug I'd like to keep up with the improvements in Emby but I can't troubleshoot this server crash without help. Tell me what information you need or logs to send to whom ever manages the crash cause and I will. Do you have a skia package installed ? Link to comment Share on other sites More sharing options...
Baenwort 97 Posted April 29, 2019 Share Posted April 29, 2019 (edited) Do you have a skia package installed ? I do not recall installing one and checking the list from pkg version I do not see one in the jail: (output from jail rolled back to 4.0.2.0 to keep Mutiny of the 4 Year olds from occurring) root@emby_2:~ # pkg version ImageMagick6-6.9.10.22_1,1 > adwaita-icon-theme-3.28.0 = apr-1.6.5.1.6.1_1 = argtable-2.13_2 = argyllcms-1.9.2_4 = at-spi2-atk-2.26.2 = at-spi2-core-2.28.0 = atk-2.28.1 = autoconf-2.69_2 = autoconf-wrapper-20131203 = automake-1.16.1_1 = avahi-app-0.7_2 = base64-1.5_1 = bash-5.0.7 > binutils-2.32,1 = bison-3.3.2,1 = ca_root_nss-3.43 > cairo-1.16.0,2 > ccextractor-0.85_12 > check-0.12.0_1 = cmocka-1.1.1_1 = colord-1.3.5 = compat10x-amd64-10.4.1004000.20181014 = compat9x-amd64-9.3.903000.20170608 = cups-2.2.11 > curl-7.64.1_1 > cvsps-2.1_2 = dav1d-0.2.2 > db48-4.8.30.0_2 = db5-5.3.28_7 = dbus-1.12.12 > dbus-glib-0.110 > dejavu-2.37_1 > desktop-file-utils-0.23 = dialog4ports-0.1.6 = docbook-1.5 = docbook-sgml-4.5_1 = docbook-xml-5.0_3 = docbook-xsl-1.79.1_1,1 = emby-server-4.0.2.0_1 > encodings-1.0.4_4,1 = expat-2.2.6_1 = fdk-aac-2.0.0 = ffmpeg-4.1.3_2,1 > fftw3-3.3.8_3 = flac-1.3.2 = font-bh-ttf-1.0.3_4 > font-misc-ethiopic-1.0.3_4 > font-misc-meltho-1.0.3_4 > font-util-1.3.1 = fontconfig-2.12.6,1 = freetype2-2.9.1 = frei0r-1.6.1 = fribidi-0.19.7 = gamin-0.1.10_10 = gcc-ecj-4.5 = gcc5-5.5.0_6 = gcc6-6.5.0_3 = gcc7-7.4.0_1 = gcc8-8.3.0_2 > gdbm-1.18.1_1 > gdk-pixbuf2-2.36.12 = gettext-0.19.8.1 = gettext-runtime-0.19.8.1_2 = gettext-tools-0.19.8.1_1 = ghostscript9-agpl-base-9.27 > ghostscript9-agpl-x11-9.27 > giflib-5.1.4 = git-2.21.0 > glib-2.56.3_4,1 > gmake-4.2.1_3 = gmp-6.1.2_1 = gnome_subr-1.0 = gnutls-3.6.7 > gobject-introspection-1.56.1,1 = graphite2-1.3.13 = gsfonts-8.11_8 = gstreamer1-1.14.4 = gstreamer1-libav-1.14.4_2 = gstreamer1-plugins-1.14.4_1 = gstreamer1-plugins-gdkpixbuf-1.14.4 = gstreamer1-plugins-good-1.14.4 = gtk-update-icon-cache-2.24.32 = gtk3-3.24.7 > handbrake-1.2.2_1 > harfbuzz-2.4.0_1 > help2man-1.47.10 > hicolor-icon-theme-0.17 > html2text-1.3.2a = iconv-2.0_4 = icu-64.2,1 > indexinfo-0.3.1 = intltool-0.51.0_1 = iso-codes-4.2 > iso8879-1986_3 = jansson-2.12 = jasper-1.900.1_17 = jbig2dec-0.16 > jbigkit-2.1_1 = jpeg-turbo-2.0.2 > lame-3.100_2 = lcms2-2.9 = libICE-1.0.9_3,1 = libSM-1.2.3,1 = libX11-1.6.7,1 = libXScrnSaver-1.2.3_2 = libXau-1.0.9 > libXcomposite-0.4.4_5,1 = libXcursor-1.1.15_2 = libXdamage-1.1.4_5 = libXdmcp-1.1.3 > libXext-1.3.3_3,1 = libXfixes-5.0.3_2 = libXft-2.3.2_3 = libXi-1.7.9_2,1 = libXinerama-1.1.4_2,1 = libXrandr-1.5.1_2 = libXrender-0.9.10_2 = libXt-1.1.5_2,1 = libXtst-1.2.3_2 = libXxf86vm-1.1.4_3 = libarchive-3.3.3,1 = libass-0.14.0 = libcroco-0.6.12 = libdaemon-0.14_1 = libdrm-2.4.96,1 = libedit-3.1.20181209_2,1 = libepoll-shim-0.0.20190311 > libepoxy-1.5.2 = libffi-3.2.1_3 = libfontenc-1.1.4 > libgcrypt-1.8.4_1 = libgpg-error-1.36 > libgsf-1.14.44 = libiconv-1.14_11 = libidn-1.35 > libidn2-2.1.1 = libijs-0.35_5 = libinotify-20180201_1 = liblqr-1-0.4.2 = libltdl-2.4.6 = liblz4-1.9.1,1 > libnghttp2-1.38.0 > libnotify-0.7.7_1 = libogg-1.3.3,4 = libpaper-1.1.24.4 = libpciaccess-0.13.5 = libpthread-stubs-0.4 = libraw-0.19.2 > librsvg2-2.40.20 = libsamplerate-0.1.9 = libsndfile-1.0.28_2 > libsunacl-1.0.1 = libtasn1-4.13_1 = libtheora-1.1.1_7 = libtool-2.4.6_1 = libunicode-0.4_11 = libunistring-0.9.10_1 = libunwind-20170615 = libv4l-1.6.3_4 = libva-2.4.1 > libvdpau-1.1.1_2 = libvorbis-1.3.6,3 = libvpx-1.8.0 = libwmf-0.2.8.4_15 = libx264-0.157.2945 > libxcb-1.13.1 = libxkbcommon-0.8.0_1 = libxml2-2.9.8 = libxshmfence-1.2_4 = libxslt-1.1.32 = libzvbi-0.2.35_3 = lua52-5.2.4 = lzo2-2.10_1 = m4-1.4.18_1,1 = mesa-libs-18.3.2 = minixmlto-0.0.2_1 = mkfontscale-1.2.1 > mono-5.10.1.57_1 = mpc-1.1.0_2 = mpfr-4.0.2 > nano-4.2 > nasm-2.14.02,1 = neon-0.30.2_4 = nettle-3.4.1_1 = nspr-4.21 > opencv-core-3.4.1_17 > openjpeg-2.3.1 > openldap-client-2.4.47 = openssl-1.0.2r,1 > opus-1.3.1 > orc-0.4.28 = p11-kit-0.23.15 = p5-Authen-SASL-2.16_1 = p5-CGI-4.42 > p5-Digest-HMAC-1.03_1 = p5-Error-0.17027 = p5-GSSAPI-0.28_1 = p5-HTML-Parser-3.72 = p5-HTML-Tagset-3.20_1 = p5-IO-Socket-INET6-2.72_1 = p5-IO-Socket-SSL-2.066 > p5-Locale-gettext-1.07 = p5-Locale-libintl-1.31 = p5-Mozilla-CA-20180117 = p5-Net-SSLeay-1.85 = p5-Parse-Yapp-1.05_2 = p5-Socket6-0.29 = p5-Text-Unidecode-1.30 = p5-Unicode-EastAsianWidth-1.40 = p5-XML-Parser-2.44 = pango-1.42.4_1 = pciids-20190418 > pcre-8.43_1 > perl5-5.28.2 > perl5.24-5.24.4_2 = pixman-0.34.0_1 = pkg-1.10.5_5 = pkgconf-1.6.1,1 > png-1.6.37 > polkit-0.114_2 = poppler-data-0.4.9 = popt-1.16_2 = py27-Babel-2.6.0_1 > py27-Jinja2-2.10 = py27-MarkupSafe-1.1.1 > py27-alabaster-0.7.6 = py27-asn1crypto-0.22.0 = py27-certifi-2019.3.9 > py27-cffi-1.12.3 > py27-chardet-3.0.4_1 > py27-cryptography-2.6.1 > py27-dnspython-1.16.0 > py27-docutils-0.14_4 > py27-enum34-1.1.6 = py27-idna-2.8 > py27-imagesize-0.7.1 = py27-ipaddress-1.0.22 = py27-iso8601-0.1.12 > py27-openssl-18.0.0 = py27-pillow-5.3.0 = py27-pycparser-2.18 = py27-pygments-2.3.0_1 > py27-pysocks-1.6.8 = py27-pystemmer-1.3.0_2 = py27-pytz-2019.1,1 > py27-requests-2.21.0 = py27-setuptools-41.0.0 > py27-six-1.12.0 = py27-snowballstemmer-1.2.0_1 = py27-sphinx-1.6.5_2,1 > py27-sphinx_rtd_theme-0.4.3 > py27-sphinxcontrib-websupport-1.1.0 = py27-tkinter-2.7.16_6 > py27-typing-3.6.6 > py27-urllib3-1.22,1 = py36-Babel-2.6.0_1 > py36-Jinja2-2.10 = py36-MarkupSafe-1.1.1 > py36-alabaster-0.7.6 = py36-asn1crypto-0.22.0 = py36-certifi-2019.3.9 > py36-cffi-1.12.3 > py36-chardet-3.0.4_1 > py36-cryptography-2.6.1 > py36-cython-0.29_1 > py36-docutils-0.14_4 > py36-idna-2.8 > py36-imagesize-0.7.1 = py36-openssl-18.0.0 = py36-pycparser-2.18 = py36-pygments-2.3.0_1 > py36-pysocks-1.6.8 = py36-pystemmer-1.3.0_2 = py36-pytest-runner-2.11.1 = py36-pytz-2019.1,1 > py36-requests-2.21.0 = py36-setuptools-41.0.0 > py36-setuptools_scm-3.1.0 = py36-six-1.12.0 = py36-snowballstemmer-1.2.0_1 = py36-sphinx-1.6.5_2,1 > py36-sphinx_rtd_theme-0.4.3 > py36-sphinxcontrib-websupport-1.1.0 = py36-urllib3-1.22,1 = python2-2_3 = python27-2.7.16_1 > python36-3.6.8_2 > readline-8.0.0 > samba47-4.7.12_1 > schroedinger-1.0.11_4 = sdocbook-xml-1.1_2,2 = serf-1.3.9_3 = shared-mime-info-1.10_1 > speex-1.2.0,1 = speexdsp-1.2.r3_1 = spidermonkey170-17.0.0_9 > spidermonkey52-52.9.0_3 > sqlite3-3.27.2 > subversion-1.12.0 > svgalib-1.4.3_7 = swig30-3.0.12 = talloc-2.1.14 = tcl86-8.6.9_1 > tdb-1.3.16,1 = tevent-0.9.37 = texi2html-5.0_2,1 = texinfo-6.6_1,1 > tiff-4.0.10 = tk86-8.6.9_1 > tpm-emulator-0.7.4_2 = trousers-0.3.14_2 = unzip-6.0_7 = utf8proc-2.2.0 > v4l_compat-1.6.3_3 = wavpack-5.1.0_1 = wayland-1.16.0_1 = wayland-protocols-1.17 = webp-1.0.2 = wget-1.20.3 > x265-3.0 > xcb-proto-1.13_1 > xcb-util-0.4.0_2,1 = xcb-util-renderutil-0.3.9_1 = xkeyboard-config-2.24_1 = xmlcatmgr-2.2_2 = xmlcharent-0.3_2 = xorg-fonts-truetype-7.7_1 = xorg-macros-1.19.2 = xorgproto-2018.4 = xtrans-1.4.0 > xvid-1.3.5,1 = Edited April 29, 2019 by Baenwort Link to comment Share on other sites More sharing options...
Luke 37065 Posted April 29, 2019 Share Posted April 29, 2019 Can you provide a log from 4.0.2? thanks. Link to comment Share on other sites More sharing options...
Baenwort 97 Posted April 30, 2019 Share Posted April 30, 2019 (edited) See post: https://emby.media/community/index.php?/topic/68032-update-to-4002-on-freenas/page-2#entry734789 the log that is called embyserver-before is from before the upgrade. I've also posted logs from before (4.0.2.0_1) and after (4.1.0.26 and 4.2 beta) at: https://emby.media/community/index.php?/topic/68032-update-to-4002-on-freenas/page-3#entry735390 If turning on debugging can help I can do it the before upgrade (4.0.2.0_1) and after upgrade (4.1.0.26) and after crash (4.1.0.26 homepage load by webapp) just ask. I can do this all day thanks to ZFS snapshot system. Edited April 30, 2019 by Baenwort Link to comment Share on other sites More sharing options...
Luke 37065 Posted April 30, 2019 Share Posted April 30, 2019 I've posted the 4.1.1 stable release. Please try that. Thanks. Link to comment Share on other sites More sharing options...
makarai 108 Posted May 1, 2019 Author Share Posted May 1, 2019 I've posted the 4.1.1 stable release. Please try that. Thanks. Can you elucidate me on the version naming scheme ? Which one, is the newest one. old to new ? 4.1.0.26 4.1.1 4.2.0.1-beta Link to comment Share on other sites More sharing options...
Luke 37065 Posted May 1, 2019 Share Posted May 1, 2019 yes that's correct. Link to comment Share on other sites More sharing options...
muskokaslowpitcher 0 Posted May 13, 2019 Share Posted May 13, 2019 I have installed 4.1.1.0, and am experiencing similar behaviour to makarai. I can use the manage server page, but as soon as I select the home icon, the server crashes. I tried from Firefox and Chrome on Linux, and both had the same behaviour. I was, however able to use my android phone and the emby app to see the home page and watch a video. Link to comment Share on other sites More sharing options...
makarai 108 Posted May 14, 2019 Author Share Posted May 14, 2019 hmm i dont expect any of this behaivior. Can you install a new emby jail using the method outlined here? https://github.com/ma-karai/iocage-plugin-emby Link to comment Share on other sites More sharing options...
MRobi 159 Posted May 15, 2019 Share Posted May 15, 2019 hmm i dont expect any of this behaivior. Can you install a new emby jail using the method outlined here? https://github.com/ma-karai/iocage-plugin-emby Is 4.2.0.1 the latest stable? I thought that was 4.1.1.0? Link to comment Share on other sites More sharing options...
Luke 37065 Posted May 15, 2019 Share Posted May 15, 2019 4.1.1 is the stable release. 4.2 is beta right now. Link to comment Share on other sites More sharing options...
makarai 108 Posted May 15, 2019 Author Share Posted May 15, 2019 Is 4.2.0.1 the latest stable? I thought that was 4.1.1.0? anyway the install script installs exactly that 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