ReadyDLNA is not updating with new iTunes music

[BrainzUK]

I have the ReadyNAS 104 which on the whole works well. I have an issue though where it won't update the ReadyDLNA database with any new music that I add to iTunes.

This has been an ongoing issue for a while and the only way I can add my new music is to to do a manual rescan. I have tried all the obvious like turning it off/on etc.

Checking the upnp-av.log shows lots of errors in the form of:

Jan 12 15:06:22 NAS-104 minidlnad[2574]: inotify.c:93: error: inotify_add_watch(/Red-2TB-3/Red-2TB-3/iTunes/Album Artwork/Cache/A198EF51E2A2F8F5/13/14/01) [No space left on device]

Which indicates no space, but there is definitely a fair amount of space left on the drive. (over 500gb)

Does anyone have any ideas on what's going wrong please?

[JennC]

Hello BrainzUK,

Perhaps try updating to firmware version 6.6.1 and see if there's any difference.

Welcome to the community!

Regards,

[BrainzUK]

Thanks for the welcome 🙂

I have kept up to date with all the firmware updates, including the 6.6.1 version, but still fails to update the music library 😞

Would any of the logs show why it's failing to update?

[JennC]

Hello BrainzUK,

Are you adding the music files using mobile phone or iPad or Mac computer? Please see if you get the same problem when you are using a computer that is wired to the network where the NAS is.

Regards,

[BrainzUK]

I am adding the music via iTunes on my PC.

I am sure that the ReadyDLNA system should be auto scanning for new music every so often and adding anything it finds, which it doesn't.

[JennC]

Hello BrainzUK,

Did you remove then reinstall it after the update? Can you try that please and see if you get the same?

Do you not see the music files that has been added when getting to the share that has the iTunes enabled?

Regards,

[BrainzUK]

I'm not sure how to completely "remove" the DLNA option, but I definitely have tried disabling it, rebooting, then re-enabling and it makes no difference.

The only way to get the new music added is to force the NAS to rescan.

The music is there in the newly added folders, but just doesn't show up when browsing via DLNA folders.

[StephenB]

I think you are saying that:

• you run iTunes on a PC (or Mac), but the music itself is stored on the readynas
• when you add music to the music share(s), then ReadyDLNA isn't updating automatically  But it does find the music if you rescan manually.

Is that correct?

If so, iTunes probably isn't relevant.  ReadyDLNA doesn't depend on iTunes. You can try copying some music into the music share (with no use of iTunes at all) and check that.

Is ReadyDLNA only enabled for the music share?  Or is it enabled for other shares?

[BrainzUK]

"I think you are saying that:

• you run iTunes on a PC (or Mac), but the music itself is stored on the readynas
• when you add music to the music share(s), then ReadyDLNA isn't updating automatically  But it does find the music if you rescan manually."

Both are correct.

New files are definitely in the correct place on the NAS drive, and yet are not picked up the NAS drive using ReadyDLNA.

I have disabled ReadyDLNA from all other shares, so only sharing the Music (iTunes) folder.

New music fails to show on either my Yamaha AV Amp (using DLNA) or my Samsung TV (again using DLNA) unless I force a rescan of the ReadDLNA server.

Any more ideas on how to fix it?

[StephenB]

I suspect that ReadyDLNA is simply not detecting that files were added.

If you are using a Mac (and AFP) then perhaps shift to SMB.  If you are already using SMB I don't have any ideas.

[BrainzUK]

Surely ReadyDLNA should be "looking" for new files and pick them up however they get onto the drive?

I am using Windows with itunes, but even if I just copy the files onto the ReadyNas device, it still doesn't show the new music files unless I manually do a complete new rescan.

It's really frustrating, and I would have hoped that someone could have provided a solution?

[BrainzUK]

Also, I still keep seeing this error on multiple lines in my upnp-av.log :

Mar 03 07:09:20 BrainzNAS-104 minidlnad[2462]: inotify.c:93: error: inotify_add_watch(/Red-2TB-3/Red-2TB-3/iTunes/iTunes Media/Music/Simply Red/Life) [No space left on device]

Someone must know what is causing that [No space left on device] error?

[StephenB]

It might the OS partition is filling.

See if you can download the log zip file.  Then look in volume.log  At the bottom there will be a section that looks like this:

=== df -h ===
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 3.7G 498M 3.0G 15% /
tmpfs 1009M 0 1009M 0% /dev/shm
tmpfs 1009M 556K 1009M 1% /run
tmpfs 505M 656K 504M 1% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup

...

Please post the corresponding lines in your volume.log (no need to go further than the last tmpfs line).

[BrainzUK]

Thanks for the reply.

The log file shows this.. Any more ideas?

=== df -h ===
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 809M 3.0G 22% /
tmpfs 249M 4.0K 249M 1% /dev/shm
tmpfs 249M 624K 248M 1% /run
tmpfs 125M 5.7M 119M 5% /run/lock
tmpfs 249M 0 249M 0% /sys/fs/cgroup
/dev/md127 3.7T 1.1T 2.6T 30% /Red-4TB-1
/dev/md126 1.9T 860G 999G 47% /Red-2TB-3
/dev/md125 2.8T 2.1T 705G 75% /Red-3TB-2
/dev/md124 2.8T 2.1T 683G 76% /Red-3TB-1
/dev/md124 2.8T 2.1T 683G 76% /apps
/dev/md126 1.9T 860G 999G 47% /run/nfs4/Red-2TB-3/Red-2TB-3
/dev/md124 2.8T 2.1T 683G 76% /run/nfs4/Red-3TB-1/Red-3TB-1
/dev/md125 2.8T 2.1T 705G 75% /run/nfs4/Red-3TB-2/Red-3TB-2
/dev/md127 3.7T 1.1T 2.6T 30% /run/nfs4/Red-4TB-1/Red-4TB-1
=== df -i ===
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 63154 462 62692 1% /dev
/dev/md0 65536 14244 51292 22% /
tmpfs 63590 2 63588 1% /dev/shm
tmpfs 63590 637 62953 2% /run
tmpfs 63590 24 63566 1% /run/lock
tmpfs 63590 9 63581 1% /sys/fs/cgroup
/dev/md127 0 0 0 - /Red-4TB-1
/dev/md126 0 0 0 - /Red-2TB-3
/dev/md125 0 0 0 - /Red-3TB-2
/dev/md124 0 0 0 - /Red-3TB-1
/dev/md124 0 0 0 - /apps
/dev/md126 0 0 0 - /run/nfs4/Red-2TB-3/Red-2TB-3
/dev/md124 0 0 0 - /run/nfs4/Red-3TB-1/Red-3TB-1
/dev/md125 0 0 0 - /run/nfs4/Red-3TB-2/Red-3TB-2
/dev/md127 0 0 0 - /run/nfs4/Red-4TB-1/Red-4TB-1

[StephenB]

---

@BrainzUK wrote:

Thanks for the reply.

The log file shows this.. Any more ideas?

=== df -h ===
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 809M 3.0G 22% /
tmpfs 249M 4.0K 249M 1% /dev/shm
tmpfs 249M 624K 248M 1% /run
tmpfs 125M 5.7M 119M 5% /run/lock
tmpfs 249M 0 249M 0% /sys/fs/cgroup

---

The OS partition looks fine.

Is the AntiVirus service enabled on the NAS?  If it is, then try disabling it.  Though that seems like a long shot, since the problem happened in 6.6.0.  However, it might account for the "no space left on device", which is possibly masking the real problem.

[BrainzUK]

Nope.. Antivirus is not enabled.

I guess the fact that I'm getting an error message saying no space left is a good sign that something is wrong, but it doesn't seem to make any sense as it LOOKS like there is ample space on all drives?

[StephenB]

---

@BrainzUK wrote:

I guess the fact that I'm getting an error message saying no space left is a good sign that something is wrong, but it doesn't seem to make any sense as it LOOKS like there is ample space on all drives?

---

Correct. 

The antivirus service (system->settings->services) has generated some similar errors in 6.6.1, but since it's off, that's not the cause.

Maybe PM skywalker, and see if he is interested in looking at your logs.

[BrainzUK]

Thanks for your suggestion of asking Skywalker (and his help), and my own research.. I've fixed it!!!! 🙂

The problem appeared to be caused by the lack of inotify watches.

For anyone else having the same issue my fix was as follows:

Temp Enabling SSH and checking..

cat /proc/sys/fs/inotify/max_user_watches
showed it was currently set on around 65,000

Editing the /etc/sysctl.conf file and adding the line:

fs.inotify.max_user_watches=100000

then running the command "sysctl -p" to make the changes (apparently)

Plus I did a reboot just to make sure!

AND IT WORKS!!

Checking the log file now shows no errors, and the system auto picks up new music added into the folders.

Apparently the new updated Beta firmware update should include a similar fix anyway, so in future you wouldn't need the manual fix.

Thanks for all the help everyone!