[Solved] 1.6.1 - Media scanning doesn't seem to work

[Shred]

While upgrading on Linux from 1.5.2 to 1.6.1 today I had a bit of a brain-fade and accidentally deleted my library. Not a big deal really, other than losing my watched history, but it does take time to do the rescan.

Using the new web-based consoled, I re-added my shared folders which are samba shares. So far so good. Then I clicked on Force refresh, waited a while and checked - nothing seemed to be added. I've tried it again and again, doing a full reboot as well but I can't get Serviio to add any media.

Looking at the log, this is the last message I get:

INFO [LocalLibraryManager] Starting manual library scan

There are no errors or further messages after that. The Serviio console can see the shares and the media files when adding the shared folders

I waited about 30 minutes to see if anything changed but nothing was scanned - no files were added to the library.

I then deleted everything except the library, log and plugins directories and reinstalled 1.5.2. After starting it, immediately began scanning and adding media to the library. All working normally.

Once it finished, I went back to 1.6.1, added another folder to scan and again, nothing happened. So I have reverted to 1.5.2 again and it scanned the additional folder as expected.

I don't know why, but the media scanning just doesn't seem to work in 1.6.1 on my Linux system. Any thoughts?

[zip]

Does it work if you click Force refresh?

YOu could also try to turn of the Poller mechnism. http://wiki.serviio.org/doku.php?id=lib ... _mechanism

[Shred]

Force refresh doesn't work either - it just says Start manual library scan in the log but nothing happens after that.

Yes, I've also tried turning on the Poller mechanism to no effect.

[zip]

Can you post detailed log pls?

[Shred]

I turned on detailed debugging in the log and now I can see that it actually does do a scan, but nothing is picked up. I just added a new file to one of the folders and saw that it searched the folder in the log but didn't report that it found anything. I can still post the log if you like but from what I can see, it doesn't really tell you anything. Plus now that I've turned on DEBUG level of logging there are now 6 log files from when I turned it on.

[zip]

Can't really check anything without the log...

[Shred]

I've attached 2 logs in a zip file. The one with the .5 extension is where I started the manual scan and the .4 is where the location of my added media file appears. I added a file to the Banshee Season 4 folder but it doesn't seem to get picked up. I can see lots of other "Found file" log entries so I'm not sure what's going on. The file permissions are the same on the locations where files are found and those where they aren't.

I just switched back to 1.5.2 and the file in question was found and added to the library as expected.

[zip]

I saw this in the logs:

  Code:

2016-04-04 09:30:17,720 DEBUG [LibraryOneTimeScanner] Looking for files to share in folder: /media/3b96487d-e145-4abc-8211-3e242e684cc6/Seagate/Files/TV/Banshee
2016-04-04 09:30:17,762 DEBUG [LibraryOneTimeScanner] Looking for files to share in folder: /media/3b96487d-e145-4abc-8211-3e242e684cc6/Seagate/Files/TV/Banshee/Banshee Season 2
2016-04-04 09:30:17,811 DEBUG [LibraryOneTimeScanner] Looking for files to share in folder: /media/3b96487d-e145-4abc-8211-3e242e684cc6/Seagate/Files/TV/Banshee/Banshee Season 1
2016-04-04 09:30:17,960 DEBUG [LibraryOneTimeScanner] Looking for files to share in folder: /media/3b96487d-e145-4abc-8211-3e242e684cc6/Seagate/Files/TV/Banshee/Banshee Season 3
2016-04-04 09:30:18,040 DEBUG [LibraryOneTimeScanner] Looking for files to share in folder: /media/3b96487d-e145-4abc-8211-3e242e684cc6/Seagate/Files/TV/Banshee/Banshee Season 4

Normally there would be files found among these lines. This looks like access rights to me.

When you run 1.5.2, do you use the same installation or do you run them side-by-side? Just thinking if maybe you're running 1.6.1 with another user?? try

  Code:

ps aux | grep java

and confirm the user that runs the Serviio task has read access to the folders and files in the folders.

[Shred]

My first thought was also a permissions thing but 1.5.2 and 1.6.1 are run from the same installation folder as the same user. I use this as a guide to switch between installations. The output from ps aux | grep java is the same for both versions too.

[zip]

Make sure you remove all files in the lib folder when you move installations. Also going from 1.6.x to 1.5.x will not work if you keep the library folder - the database schema is no backwards compatible.

[Shred]

I deleted everything except for the library and plugins folders. I'm aware that the db isn't backwards compatible - I can't add new folders to it, but it does read what's already there. If I want to add a folder, I switch to 1.6.1, add it, then go back to 1.5.2 which then reads in the content.

Additionally, once 1.5.2 has added the media and I then switch to 1.6.1 it can serve up the media just fine, which suggests that it does have read access to the files (which it should, as it's run as the same user)

[zip]

Sorry, I can't give you support if your installation might be broken.

Please try a clean install and confirm you still see the problem.

[Shred]

That's how this started - I accidentally deleted everything so I had to start from scratch. I only went back to 1.5.2 to see if it would scan in the media.

Going through the logs I did notice that serviio home directory was wrong (I recently changed serviio locations from /usr/local/serviio to /usr/bin/serviio) so I fixed that in case that was causing issues. So I've now deleted everything and started with a fresh installation of 1.6.1. Same problem though, it goes through all the folders just fine but doesn't pick up any files.

Apart from the actual contents of the installation folders, nothing else has changed between 1.5.2 and 1.6.1. Same user, same media folders and same permissions. I might just go back to 1.5.2 until the next version comes out and see if that fixes my issue.

Update: Although the console indicated that it found no files on the Welcome to Serviio page, going through the detail log it did report that it added 1 file (out of 3000+) and extracted the metadata. It's not in the library though. This is from a clean installation of 1.6.1.

[zip]

I might just go back to 1.5.2 until the next version comes out and see if that fixes my issue.

It won't automagically fix itself You're a beta tester so hopefully you'll be able to test the new version before if goes live.

What is the single file that it added? What if you remove this file, does it try to add others? Can you send me the bit of the log where it adds this single file?

[Shred]

My mistake, I didn't keep a copy of the log file before I deleted the 1.6.1 installation prior to re-installing the 1.5.2 version. 1.5.2 again added all the files as expected.

I'll wipe everything again tomorrow morning (my time) and send you the log. It basically reports the things that it usually does when adding a file including obtaining the metadata and adding it to the database - but it doesn't actually get added.

[Shred]

Attached is the copy of the log where it finds and "adds" one file to the library (it doesn't actually add it, it just says it does). I deleted the file it found, and re-ran the manual scan and it then picked up the next file in the folder (this is in the log too).

[zip]

Ok, I think it's something to do with ffmpeg . There was a change how Serviio detects ffmpeg version and compiled features.

Can you post output when you execute:

  Code:

ffmpeg

[Shred]

Bingo!

Up until just now, I was using libav instead of ffmpeg for Serviio as ffmpeg was deprecated in Debian/Ubuntu when I first started using Serviio. It was supposed to be feature compatible and worked fine for Serviio versions up to and including 1.5.2.

I just did a quick bit of research and have learnt that ffmpeg was reintroduced to Debian/Ubuntu mid-way last year. So I've now installed ffmpeg and serviio 1.6.1 is now adding my media!

Thanks for all your help with this. I now feel a bit embarrassed that the problem was due to my installation.

[zip]

ANy chance to still post what you were getting as an output to ffmpeg? I should catch these cases and print a proper error message

[Shred]

root@omv:~# ffmpeg
avconv version 0.8.17-6:0.8.17-2, Copyright (c) 2000-2014 the Libav developers
built on Mar 2 2016 22:53:14 with gcc 4.7.2
Hyper fast Audio and Video encoder
usage: avconv [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man avconv'