The almost inevitable thread about Plugins on BETA 3...=)

[William Grzybowski]

You just need to chown -R dlna:dlna /var/db/minidlna so dlna can start (within the jail)

 

[duckman]

@William Grzybowski

Did that, no dice as far as I can see. I have re-installed the plugin a few times to see if that helps too.


I did this: jexec into the jail as root
# chown -R dlna:dlna /var/db/minidlna
# /mnt/plugins/pbi/minidlna-i386/sbin/minidlna
/libexec/ld-elf.so.1: Shared object "libjpeg.so.11" not found, required by "minidlna"

weird...

Toggling the start/stop in the gui just says "some error occurred" and it stays off.

However, I may just be thick, so I'll delete it & reinstall it again this evening & try again.

 

[William Grzybowski]

Hmm weird, might be an issue with the i386 build...

 

[mrmojo]

@William Grzybowski

Did that, no dice as far as I can see. I have re-installed the plugin a few times to see if that helps too.


I did this: jexec into the jail as root
# chown -R dlna:dlna /var/db/minidlna
# /mnt/plugins/pbi/minidlna-i386/sbin/minidlna
/libexec/ld-elf.so.1: Shared object "libjpeg.so.11" not found, required by "minidlna"

weird...

Toggling the start/stop in the gui just says "some error occurred" and it stays off.

However, I may just be thick, so I'll delete it & reinstall it again this evening & try again.

I'm also experiencing exactly the same problem with the i386 version. When I click to turn on the minidlna plugin I get "some error occurred" in the GUI. I have tried everything already mentioned in the forum without luck.

I have tried deleting and reinstalling, as well rebooting the machine numerous times without luck. Any help much appreciated.

 

[ProtoSD]

Is there anything wrong with this kind of setup?
In the video you mounted the outside datasets into the plugin's pbi directory, not into the jail itself - any special reason why?

Nothing wrong with it at all.

You could create a mount point into the jailed app's folder in /usr/pbi/your-app-amd64/mount-point, BUT... I think the problem would be if you want to remove the plugin or update it and the update wants to use a new folder and delete the old folder. I think the GUI might have trouble removing the plugin because the folder inside it is mounted, so you would need to delete the mount point in the GUI before deleting the plugin.

 

[William Grzybowski]

Nothing wrong with it at all.

You could create a mount point into the jailed app's folder in /usr/pbi/your-app-amd64/mount-point, BUT... I think the problem would be if you want to remove the plugin or update it and the update wants to use a new folder and delete the old folder. I think the GUI might have trouble removing the plugin because the folder inside it is mounted, so you would need to delete the mount point in the GUI before deleting the plugin.

The GUI already umounts anything inside the pbi dir before proceeding ;)
It won't delete the mount point though.

 

[William Grzybowski]

@William Grzybowski

Did that, no dice as far as I can see. I have re-installed the plugin a few times to see if that helps too.


I did this: jexec into the jail as root
# chown -R dlna:dlna /var/db/minidlna
# /mnt/plugins/pbi/minidlna-i386/sbin/minidlna
/libexec/ld-elf.so.1: Shared object "libjpeg.so.11" not found, required by "minidlna"

weird...

Toggling the start/stop in the gui just says "some error occurred" and it stays off.

However, I may just be thick, so I'll delete it & reinstall it again this evening & try again.

Thats not how you start minidlna:

Use /usr/local/sbin/minidlna

 

[SilverJS]

Here's a quick question : how does all this work when upgrading FreeNAS? I mean I've installed Transmission, configured it, and also installed MySQL inside the jail and configured that to work with XBMC. What happens when I upgrade the OS?

 

[William Grzybowski]

Nothing, everything should remains the same, the jail will continue to use the libraries within its own root, the jail is based on freebsd 8.0 or 8.2 (i dont really recall), as long as the host kernel continues to support those versions it will work

EDIT: It doesn't mean if the Host OS changes to a version 8.3 or 9, those kernels can maintain binary backwards compatibility to older verions...

 

[Sneakernet]

Same problem with minidlna. Firefly dropping from itunes share.

I can't get minidlna working. The other two (firefly, transmission) are working.

I did the chown dlna:dlna mentioned earlier in this thread, but I'm getting this error:

PJail# /mnt/plugins/pbi/minidlna-i386/sbin/minidlna
/libexec/ld-elf.so.1: Shared object "libjpeg.so.11" not found, required by "minidlna"

Is that the right way to start it? Doing it from the gui just says "some error occurred".

Also, in the gui console I'm getting the following as well:

Apr 21 08:21:47 localhost Couldn't retrieve http://nas/plugins/minidlna/_s/treemenu: HTTP Error 502: Bad Gateway
Apr 21 08:21:48 localhost Couldn't retrieve http://nas/plugins/minidlna/_s/status: HTTP Error 502: Bad Gateway
Apr 21 08:22:28 localhost Couldn't retrieve http://nas/plugins/minidlna/_s/status: HTTP Error 502: Bad Gateway
Apr 21 08:22:29 localhost Couldn't retrieve http://nas/plugins/minidlna/_s/treemenu: HTTP Error 502: Bad Gateway

and no entry for minidlna in the treemenu - there are entries for firefly & transmission (which I used to configure them).
Being a beta, I'm not expecting it all to work straight off, but I dunno if this is a bug or something I've done...

On other thing as well, files downloaded by transmission are owned by uid 1003, and I don't have permission to move/delete them. The uid of the only user on here is 1002. There is no user with uid 1003 in /etc/passwd on base system. The transmission user inside the jail does have uid 1003.

Same problem with minidlna. Appears to be an issue with the i386 version.

Firefly and transmission starting okay. But seeing an issue with the Firefly share dropping from itunes after short period of time even while streaming music.

 

[duckman]

Same problem with minidlna. Appears to be an issue with the i386 version.

Firefly and transmission starting okay. But seeing an issue with the Firefly share dropping from itunes after short period of time even while streaming music.

Does your firefly have bonjour running? Is it "discoverable" or do you have to point whatever client you have at the server IP?
My firefly also stops playing, it does seem still connected though as I can still browse the music list & start it playing again. Could be the client I'm using (Daap from the Android market)

 

[Sneakernet]

Does your firefly have bonjour running? Is it "discoverable" or do you have to point whatever client you have at the server IP?
My firefly also stops playing, it does seem still connected though as I can still browse the music list & start it playing again. Could be the client I'm using (Daap from the Android market)

It is discoverable. I see it on all clients throughout the house. I can browse music and play until it drops off the share. Drops across all clients and requires stopping and restarting the service. I did notice that in the Firefly GUI that Bonjour is indicated as "Stopped" under server status but I have mDNSRespnder.exe service running on all clients.

 

[duckman]

It is discoverable. I see it on all clients throughout the house. I can browse music and play until it drops off the share. Drops across all clients and requires stopping and restarting the service. I did notice that in the Firefly GUI that Bonjour is indicated as "Stopped" under server status but I have mDNSRespnder.exe service running on all clients.

Interesting. I don't have any windows boxes, but all my linux laptop clients are running avahi (which is what I believe mdnsResponder is named). None of them can "find" the firefly share. Along with that, my phone does not see it either.
I had always assumed that the server needed to be running some sort of bonjour/dnsresponder/avahi in order to "broadcast" the share so clients could "listen" for it.

Out of interest, what are the client software you've got? iTunes? something else?

 

[Sneakernet]

Client software is iTunes

 

[SilverJS]

Uh-Oh - Mount Point Debacle

OK, so mount points don't work for me at ALL. =) I created a folder from Windows, on my FreeNAS root directory, called "Downloads (Finished)" without the quotes. I then SSH'd into my box to create a folder, with the exact same name, inside the jail, in /usr/pbi. I then tried to mount the two folders - got a Middleware error.

Either way, I then deleted the two folders, and I guess I must have forgotten to delete the mount point, because everything started going haywire. I resorted to deleting the datasets, re-installing the jail and re-installing the plug-in - except that now, the jail won't fully start.

Interestingly, my mount point is still visible in the GUI tree menu on the left, but if I click on it, I get a dialog box that says "Sorry, An Error Occurred" that I can't get out of (No "X" button, and I have to close the window/tab). I also can't view my mount points or add to them. I suspect that's what's holding up the jail and everything else.

So is there some way to do the same thing for the plugins (sqlite3 /data/freenas-v1.db "delete from plugins_plugins") to the mount points?

Cheers!

EDIT : Tried "re-upgrading", or re-installing the original beta 3 firmware via GUI update - get a Middleware error as well. Now I'm kinda stuck. =)

 

[ProtoSD]

OK, so mount points don't work for me at ALL. =) I created a folder from Windows, on my FreeNAS root directory, called "Downloads (Finished)" without the quotes. I then SSH'd into my box to create a folder, with the exact same name, inside the jail, in /usr/pbi.

You didn't follow the video tutorial....:( If you did and created both directories from the shell I don't think that would have happened.

You could try recreating the folders and deleting the mountpoint from the GUI. Let me look at the database and see what needs resetting to clear out the mountpoint, but at this point things sound pretty frelled and I'm not sure doing that will make any difference.

 

[ProtoSD]

So is there some way to do the same thing for the plugins (sqlite3 /data/freenas-v1.db "delete from plugins_plugins") to the mount points?

You can try this for cleaning the stale mount points, but if you've done a factory reset, don't do this, it won't help.

sqlite3 /data/freenas-v1.db "delete from plugins_nullmountpoint"

 

[SilverJS]

You're right, you're right...(slaps hand) I didn't follow the tutorial. =) Anyhow - I'll try inputting that line of code now. Rebooting as we speak - but, I don't even know how to do a factory reset! I'll research that so that I'm ready if it comes to that.

 

[SilverJS]

OK, everything's back to normal, thanks to that line of code. I'll follow tutorials VERY strictly from now on, thanks ProtoSD. =)

BTW - You a Starcraft player or something? I keep wanting to call you Protoss...=))))

 

[ProtoSD]

OK, everything's back to normal, thanks to that line of code. I'll follow tutorials VERY strictly from now on, thanks ProtoSD. =)

BTW - You a Starcraft player or something? I keep wanting to call you Protoss...=))))

Glad to hear you got things twirling properly again! ;)

I'm not much of a game player, maybe a little larn/rogue from the old Unix days, but not much beyond that.

I used to have SDproto, but there was some problem during registration and I flipped the SD to the other side, Proto is fine. I don't use any of my name in the open forums, had some freaky experience happen to me once in another forum.