Are you sure about that? I don't think Plex uses any FFP libs at all, as it cannot find them. It can find it's own libs by LD_LIBRARY_PATH, and /lib/* because that's the default, but /ffp/lib?

Yep. You right. I was a little bit confused with such coincidence on sqlite error. Plex is not using any external libraries except one-Avahi. And this should be strange:

Code:

root@NSA310:~# export LD_LIBRARY_PATH=/ffp/lib/plexmediaserverroot@NSA310:~# ldd /ffp/lib/plexmediaserver/Plex\ Media\ Server libboost_system.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_system.so.1.47.0 (0x40005000) libboost_filesystem.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_filesystem.so.1.47.0 (0x40010000) libboost_thread.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_thread.so.1.47.0 (0x40031000) libboost_iostreams.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_iostreams.so.1.47.0 (0x40050000) libboost_regex.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_regex.so.1.47.0 (0x40081000) libboost_signals.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_signals.so.1.47.0 (0x4017a000) libboost_program_options.so.1.47.0 => /ffp/lib/plexmediaserver/libboost_program_options.so.1.47.0 (0x40197000) libxml2.so.2 => /ffp/lib/plexmediaserver/libxml2.so.2 (0x401f4000) libavutil.so.50 => /ffp/lib/plexmediaserver/libavutil.so.50 (0x403da000) libavcodec.so.52 => /ffp/lib/plexmediaserver/libavcodec.so.52 (0x40404000) libavformat.so.52 => /ffp/lib/plexmediaserver/libavformat.so.52 (0x40f21000) libswscale.so.0 => /ffp/lib/plexmediaserver/libswscale.so.0 (0x41025000) libz.so.1 => /ffp/lib/plexmediaserver/libz.so.1 (0x4105a000) libcrypto.so.1.0.0 => /ffp/lib/plexmediaserver/libcrypto.so.1.0.0 (0x41083000) libssl.so.1.0.0 => /ffp/lib/plexmediaserver/libssl.so.1.0.0 (0x411e7000) libnatpmp.so.1 => /ffp/lib/plexmediaserver/libnatpmp.so.1 (0x41239000) libminiupnpc.so.8 => /ffp/lib/plexmediaserver/libminiupnpc.so.8 (0x41243000) libiconv.so.2 => /ffp/lib/plexmediaserver/libiconv.so.2 (0x41254000) libdbus-1.so.3 => /ffp/lib/plexmediaserver/libdbus-1.so.3 (0x41352000) libsqlite3.so.0 => /ffp/lib/plexmediaserver/libsqlite3.so.0 (0x413b6000) libcurl.so.4 => /ffp/lib/plexmediaserver/libcurl.so.4 (0x4148c000) libsoci_core-gcc-3_0-3.0.0.so => /ffp/lib/plexmediaserver/libsoci_core-gcc-3_0-3.0.0.so (0x414e0000) libsoci_sqlite3-gcc-3_0-3.0.0.so => /ffp/lib/plexmediaserver/libsoci_sqlite3-gcc-3_0-3.0.0.so (0x4152e000) libpython2.7.so.1.0 => /ffp/lib/plexmediaserver/libpython2.7.so.1.0 (0x4154c000) libavahi-client.so.3 => /ffp/lib/plexmediaserver/libavahi-client.so.3 (0x416ed000) libavahi-common.so.3 => /ffp/lib/plexmediaserver/libavahi-common.so.3 (0x41709000) libfreeimage.so.3 => /ffp/lib/plexmediaserver/libfreeimage.so.3 (0x41721000) libgcc_s.so.1 => /ffp/lib/libgcc_s.so.1 (0x41c3b000) libc.so.6 => not found libstdc++.so.6 => /ffp/lib/libstdc++.so.6 (0x41c4e000) libm.so.6 => not found libpthread.so.0 => /ffp/lib/libpthread.so.0 (0x41d14000) libdl.so.2 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libm.so.6 => not found libc.so.6 => not found libdl.so.2 => not found libm.so.6 => not found libc.so.6 => not found libm.so.6 => not found libc.so.6 => not found libm.so.6 => not found libc.so.6 => not found libm.so.6 => not found libc.so.6 => not found libm.so.6 => not found libc.so.6 => not found libc.so.6 => not found libdl.so.2 => not found libc.so.6 => not found libdl.so.2 => not found libc.so.6 => not found libc.so.6 => not found libc.so.6 => not found libc.so.6 => not found librt.so.1 => not found libc.so.6 => not found libdl.so.2 => not found libc.so.6 => not found libidn.so.11 => /ffp/lib/plexmediaserver/libidn.so.11 (0x41d30000) librt.so.1 => not found libdl.so.2 => not found libc.so.6 => not found libdl.so.2 => not found libm.so.6 => not found libc.so.6 => not found libdl.so.2 => not found libm.so.6 => not found libc.so.6 => not found libdl.so.2 => not found libutil.so.1 => not found libm.so.6 => not found libc.so.6 => not found librt.so.1 => not found libdl.so.2 => not found libc.so.6 => not found libc.so.6 => not found libc.so.6 => not found libc.so.0 => /ffp/lib/libc.so.0 (0x41d6d000) libm.so.0 => /ffp/lib/libm.so.0 (0x41dd2000) ld-uClibc.so.0 => /ffp/lib/ld-uClibc.so.0 (0x2a000000) libdl.so.0 => /ffp/lib/libdl.so.0 (0x41ded000) libc.so.6 => not found

The problem above is gone and somehow this better handles with stop command. What I mean?If execute stop command after start almost immediately, it will only kill PLEX Media Server process and leaves plugins processes running. After editing as my suggestion, all processes are killed. It just takes a little bit more time to kill them, comparing with stop time if you let PMS fully load.Is these changes are right? >M

But of course there are dependencies and dependencies. The blogger is talking about dependencies to install before you can compile Plex. But libc and friends doesn't need to be installed, it's a part of the build tree. Yet the have to be available on the target system.

Thanks for clarifying things. Last dumb question. Plex searches for needed libraries in /ffp/lib/plexmediaserver/*, when we specify export LD_LIBRARY_PATH=/ffp/lib/plexmediaserver. Do the searching for libs in firmware dirs /lib/* and /usr/lib/* is default behaviour of others FFP programs too?

EDIT2: I accidently had to reinstall the whole ffp-package and now discovery plex and browsing the contents is MUCH faster on my TV... I guess something was interferring. Hopefully this solves my connection problems as well

Are you sure it's due to a fresh FFP install, and not due to the ReadyNAS package? On my NAS the ReadyNAS package webinterface feels faster, but I have no way to test it's actual performance. And, despite of the way of installing, PMS is not really an FFP package. FFP is used as launch platform, but doesn't participate in the actual running. As far as I can see the only way FFP could slowdown PMS is by using too much resources (cpu cycles, memory, disk access) itself. (Well, itself... Some FFP daemon)

on ffp I was permanently running nzbget, although idle most of the time.However I had a chrooted debian running, too. But as far as I understood only a ssh daemon was started on boot-up. So I thought it won't eat much performance.

On the other hand I did some heavy testing when I was new to ffp / Linux on that install, I guess there could have been some leftovers of that.

Mijzelf wrote:

ReadyNAS package webinterface feels faster

Actually I am still on synology-package. Is there a way to change the programm files without touching /mnt/HD_a2/plextmpdir ?

By the way: I was wondering, if there is any difference between those to packages at all. Of course the package handlers differ, but the core files seems to be the same, isn't it?

Is there a way to change the programm files without touching /mnt/HD_a2/plextmpdir ?

Don't know. The actual executables are in /ffp/lib/plexmediaserver. You can easily delete these, and reinstall.But the daemon has 2 different 'data directories': /mnt/HD_as/plextmpdir/lib and /mnt/HD_as/plextmpdir/. While they share the same root, (as configured in the startscript), they actually have a different function. The /mnt/HD_as/plextmpdir/lib contains also executables, so I don't know if those shouldn't be deleted either. On the other hand, the Plex webinterface offers an option to update the package, so I suppose a newer version can cope with an older/not compatible /mnt/HD_as/plextmpdir/lib/*.

Quote:

By the way: I was wondering, if there is any difference between those to packages at all. Of course the package handlers differ, but the core files seems to be the same, isn't it?

I certainly think they are built from the same source. But the executable is dependent on some libs in /lib and /usr/lib, which are firmware files. So I think the packages are built using the SDK provided by Synology and ReadNAS, providing different headers and objects, and so are not binary equal.The reason both run on the ZyXEL is because the libc folks try to keep the different versions of libc and friends binary compatible. Yet there can be obscure differences, making one package more compatible than the other.

My observations and suggestions after using last plex package:1. TMPDIR is owned by root instead of plex and PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR is inside it. I think, it would be better to do vice versa (I mean dirs hierarchy) or better of all to make some generic-general directory in the root of HDD, where all big programs can reside, which uses a large databases and lot of space. For example:

Code:

# Homedir of plex settings and data. About 60MB of data will be placed here after first install and will grow, # depending on your media library sizePLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=/mnt/HD_a2/programs/plex

Who is online

Users browsing this forum: No registered users and 5 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum