NeverSimple
Dabbler
- Joined
- Jul 27, 2011
- Messages
- 16
Hello,
I've tried the 'standard' plugin MiniDLNA, to find that my Sony TV couldn't play a lot of my video content. I needed a transcoding DLNA server. I've used Serviio on a separate FreeBSD9 box, so decided to install that. It turned out to be rather straightforward, but did took a bit of work.
I removed the jail and started over with a 'fresh' one.
- added the ports: 'portsnap fetch extract',
- installed 'portmaster' from ports,
- ran 'portmaster -L' and updated all of the out-of-date installed packages, referencing the /usr/ports/UPDATING file. this step took a while.
- installed serviio from /usr/ports/net/serviio. Also took a while...
- after that completed I found that it would start, but almost immidiately crash. It turned out that the hostname for the jail had to be entered in the '/etc/hosts' file for the localhost entry.
- after that it was only adding the correct media path with the remote console (on W7) and it started adding content.
I'm now looking at the video files on my Sony TV that wouldn't play on MiniDLNA. It seems to work fine. But...
I'm getting random errors on the console like this:
According to the Serviio forum (http://forum.serviio.org/viewtopic....g&sid=60cd95c603743a1e8bf04671eff24bc6#p38075), this has something to do with the port, not with serviio itself. It's just that when I ran Serviio on my FreeBSD9 server I can't remember ever seeing this.
So, is anyone running Serviio in a FreeNAS 8.2 jail and also experiencing this? Or does anyone know how to solve it?
Richard
I've tried the 'standard' plugin MiniDLNA, to find that my Sony TV couldn't play a lot of my video content. I needed a transcoding DLNA server. I've used Serviio on a separate FreeBSD9 box, so decided to install that. It turned out to be rather straightforward, but did took a bit of work.
I removed the jail and started over with a 'fresh' one.
- added the ports: 'portsnap fetch extract',
- installed 'portmaster' from ports,
- ran 'portmaster -L' and updated all of the out-of-date installed packages, referencing the /usr/ports/UPDATING file. this step took a while.
- installed serviio from /usr/ports/net/serviio. Also took a while...
- after that completed I found that it would start, but almost immidiately crash. It turned out that the hostname for the jail had to be entered in the '/etc/hosts' file for the localhost entry.
- after that it was only adding the correct media path with the remote console (on W7) and it started adding content.
I'm now looking at the video files on my Sony TV that wouldn't play on MiniDLNA. It seems to work fine. But...
I'm getting random errors on the console like this:
Code:
[root@jail1 /media]# [Fatal Error] a8d50445-3dd1-46bf-8c82-8a80d7b00c97:1:1: Content is not allowed in prolog. [Fatal Error] 0d976ad8-dbd2-4b0b-8ea1-132392f841c2:1:1: Content is not allowed in prolog. [Fatal Error] af7b49df-a4ff-4caf-9685-48937f391281:1:1: Content is not allowed in prolog. [Fatal Error] 175d95bd-9c59-4c0f-be14-db2a3af1596f:1:1: Content is not allowed in prolog. [Fatal Error] 05eaf0dc-fbce-4aa6-a8f5-702df6a95d84:1:1: Content is not allowed in prolog. [Fatal Error] fd6d6d0c-b5a1-45b8-912c-ee14c3948bb1:1:1: Content is not allowed in prolog.
According to the Serviio forum (http://forum.serviio.org/viewtopic....g&sid=60cd95c603743a1e8bf04671eff24bc6#p38075), this has something to do with the port, not with serviio itself. It's just that when I ran Serviio on my FreeBSD9 server I can't remember ever seeing this.
So, is anyone running Serviio in a FreeNAS 8.2 jail and also experiencing this? Or does anyone know how to solve it?
Richard
