Twonky, Windows 7 and a tablet - problems

[Jocko]

Hi anpulli
:scratch

There is an issue with your cloudbox.
When you enable 'Notify' option, new content must be added in the twonky cache almost at once :whistle

Need to check some points:
-what kernel version do you use. In Putty, do

Code: Select all

uname -a

or read it on the 'view system information' menu
-see the Twonky command line used by your NAS. So start twonky and in Putty, give this command

Code: Select all

ps -ef|grep twonkymedia > /share/1000/fvdw/twonkycmd.txt

(I assume that you have already created a share fvdw) So in twonkycmd.txt you will find the command used to start twonky

Please, post these outputs.
So if the command set rightly the option scantime, then maybe there is an issue with the kernel. This option relies on an
existing “inotify” support in the Linux kernel.

I will check if there is no issue with my nwsp2

[anpulli]

Hi again and thanks for your time. :)

uname -a:

Code: Select all

Linux LASSIE.local 3.9.5 #164 PREEMPT Fri Aug 9 14:52:22 GMT+1 2013 armv5tel unknown unknown GNU/Linux

the txt-file:

Code: Select all

root      1465     1  0 17:47 ?        00:00:00 /share/1000/twonkymedia/twonkymedia -contentbase /share/1000 -friendlyname Twonky-server -httpport 9000 -enableweb 2 -streambuffer 128000 -uploadenabled 1 -scantime -1
root      1466  1465  0 17:47 ?        00:00:23 /share/1000/twonkymedia/twonkyserver -contentbase /share/1000 -friendlyname Twonky-server -httpport 9000 -enableweb 2 -streambuffer 128000 -uploadenabled 1 -scantime -1
root      2236  2223  0 20:49 ttyp0    00:00:00 grep twonkymedia


I'll also attach the file because when viewing it with notepad it seems that there is no space after the "-scantime -1" and "root".

As far as I know I've used the correct kernel files and such. I chose the "install fvdw-sl firmware" in fvdw-sl console. Should I use the "write firmware image to disk" -option instead?

[Jocko]

Thank anpulli

That means that twonky have an issue with inotify support.

I did some tests with my nwsp2 and 5big2 and I can reproduce your problem. I tested with twonky version 7.0.9 with kernel version 164 but also with the next version 199 and same behavior: twonky doesn't update this media database :pissed
I also tested the next version 7.2.5-1 but also without successful.

inotify support seems work well because minidlna updates automatically its database at each event..

With some google searches, I found that at least with version 7.0.9 there are issues with several NAS QNAP, DNS-320,... because twonky uses wrong syscall numbers for inotify functions.

So temporarily, you can use minidlna and fvdw and me need some time to see if we can make a fix

[anpulli]

Oh, you're welcome. Glad to be at least some kind of assistance.

Would Twonky 6 work ok? I see it's available in fvdw-sl's media server options. I tried minidlna too, but on some occasions it somehow makes the client software list the files twice but not all of them. It's not a big deal compared to the issues with Twonky 7 but just a bit annoying. :)

[Jocko]

Twonkyserver version 6 is not a free license but you can try to use it for testing.

see also your pm ;)

[anpulli]

Yes I know it's not free but was just wondering if it would do things as it should.

I also have a Zyxel NSA-325 with Twonky 7.2.6-1 and it updates files and folders correctly. I haven't messed around it at all so I don't even know if I can access it with PuTTY or anything like that. I was just thinking if I could dig up something useful from it.

[Jocko]

Thank anpulli but currently we need yet to find how to fix this bug.

The issue is that twonky binary doesn't run well with the kernel

[anpulli]

Umm.. dunno if I did something wrong when I installed Twonky6 to try it and found out that it has the same problem. Notify is on and I tried to put -1 as scantime value but it doesn't stay. After restart the value is empty and new files are shared to media receivers only if I click the "rescan content directories" -button. What missing or messing up here? :scratch

[Jocko]

Hi anpulli,

I checked the command line used to start twonky and this option is present here (-scantime). So you can not handle this option in the twonky interface.

Be careful anpulli, this option is directly handled by the command line. So what you describe it's the normal behavior :

I tried to put -1 as scantime value but it doesn't stay. After restart the value is empty

Otherwise,that twonky version 6 has the same behavior than twonky version 7 (need to do manual scan to add new file), confirms that there is an issue between twonky and the kirkwood kernel version 3.9.5 about the inotify support.

To fix it we need the twonky files source :mrgreen:

[rimoth]

Hi Jocko,

I experienced the same problem a while back and fvdw mentioned that...

Another thing is if the rescan really works. I disabled it because the rescan can be annoying and take long time and system resource. I update it my self when having add media files.

Not sure if this helps. Obviously it would be good to have the automatic rescan, but if it hogs resources, then a cron job might be more practical.