Page 1 of 1

upgrade issue

PostPosted: Tue Apr 17, 2018 4:45 pm
by dutchguy69
My serviio server runs on a linux openSUSE system.

With version 1.6 all is fine.

Upgrading to 1.8 or 1.9 makes all mp3 and flac files show an exclamation mark (This file is invalid) on the client side. I'm using LG 32LS5600 and Sony KDL32EX713 tv and Sony DN850 AV receiver as clients.

With the upgrade I copy library and plugins directory from 1.6 to the higher version and once done restarting the serviio server. This is the process described as part of the serviio upgrade.

I tried the debug level for logging but have not found anything obviously wrong.

I tried the forum and google but have not found any direct pointers into the direction of what is wrong here.

Re: upgrade issue

PostPosted: Tue Apr 17, 2018 5:40 pm
by atc98092
Did the assigned profiles for your players change for some reason? If not, have you tried any other LG or Sony profiles? Seems strange that playable files now don't. I don't use any LG profile, and only use one Sony BD profile, and not really familiar with either of them so not certain what might have changed.

Re: upgrade issue

PostPosted: Wed Apr 18, 2018 2:48 pm
by dutchguy69
No, all three have their own standard profile assigned. LG/TV player, Sony Bravia TV (2009) and Sony AVReceiver STR.

This morning I extracted 1.8 again and copied the library and plugins directory from the working 1.6 install into it. Checked permissions and the mp3 and flac are still having the same issue.

I'm not sure what to do or how to investigate this right now.

Re: upgrade issue

PostPosted: Wed Apr 18, 2018 3:07 pm
by atc98092
Next step would be to upload a copy of your log here. You may need to enable the detailed logging (instructions in my sig line) to show what might be going on. With that, please provide a few of the file names that aren't appearing correctly. This could speed analyzing your log.

Re: upgrade issue

PostPosted: Thu Apr 19, 2018 11:19 am
by dutchguy69
I have done the debug logging and have done a session on the client, ip 162.61.5.55. I opened a jpg first. Visible at 11:52:14. That one is shown on the screen as expected.

Then I opened an audio file which shows exclamation mark in the icon and gives me message "File is invalid". I can see in the log at 11:52:40 the browsing. The file is called 01 - Love.mp3 but I can not find that at all in the logfile.

I then did another jpg before the log stops. The serviio server runs on 162.61.5.21

Re: upgrade issue

PostPosted: Thu Apr 19, 2018 10:43 pm
by atc98092
This log is incomplete. It doesn't contain any of the startup or shutdown information. I can't say what you're looking for is in the removed section, but it could be. The problem is probably occuring much sooner, when Serviio first loads and scans your directories. Perhaps it doesn't appear here because Serviio already determined (incorrectly) it was unusable. Need the full log to look for that.

Re: upgrade issue

PostPosted: Fri Apr 20, 2018 9:18 am
by dutchguy69
Sorry, here is a complete file from start to close of server including me trying to open 2 mp3 files.

They are called

01 - Theme From Harry's Game.mp3
05 - Something To Believe In.mp3

Re: upgrade issue

PostPosted: Fri Apr 20, 2018 2:18 pm
by atc98092
Neither one of those names appear in the log. I have no idea why. My last request is to move the files to a different location, so that Serviio has to re-identify them. Then we can see what the log says when it sees them in the new location. Beyond that, I'm at a loss, and Zip would have to weigh in with any other ideas.

Re: upgrade issue

PostPosted: Mon Apr 23, 2018 10:18 am
by dutchguy69
Hi first I renamed one directory and they became usable again and then I removed the 2 entries I had that contained mp3's within the shared resources. Now they are all back.

This was not what I was expecting since I had done the upgrade many times using this method.

Thanks for your information and input.

Re: upgrade issue

PostPosted: Mon Apr 23, 2018 12:09 pm
by atc98092
I believe Zip has identified an anomaly in the file refresh procedure, and has it fixed for the next version. I don't know if it might have had something to do with your issue, but I'm glad it's been resolved for you. :D