[king107s]

Hello,

I'm new to the forums but haven't seen this specific issue posted (after a lot of searching). After I upgraded to Krypton 17.6 none of my movies would play. I logged into the base ubuntu OS and executed the following again...

sudo apt-get dist-upgrade
sudo apt-get update
sudo apt-get install

and of course it did not install, change or remove any files because it was fully updated already. But... after i reboot and log back into kodi all the movies play just fine. If I reboot again they won't play. Excute those commands and it works again... not sure what the deal is or how to fix it because I'm a total noob when it comes to this stuff. I chose the new Mummy movie as an example in the log files below...

Here is the log file for when it doesnt work: https://paste.ubuntu.com/26254804/
Here is the log file for after the temporary 'fix': https://paste.ubuntu.com/26254851/  

Thank you for your time and help!

[kimkl]

This is just a guess, since i do not have great experience with kodi on Linux
But my best guess is... database problem but someone else can prob give a better solution so wait a couple hours and someone who knows the in's and out's will post
i base my guess on what i have read in the past year

[DaVu]

First...

Don't execute commands if you don't know what they are doing .

- You don't need to do a dist-upgrade all the time.
- it's useless to do a dist-upgrade if you do the apt-get update after it. Repositories are need to be updated first before you should upgrade something
- "sudo apt-get install" won't do anything as that command requires at least a package-name which it should install.

I'll show you an example from my system. It's a bit different as I'm using Ubuntu 16.04 and you are using Ubuntu 14.04.5. The difference is, that I don't use "sudo apt-get update". I'm using "sudo apt update" which does generally the same:

Code:


davu@Ubuntu-Desktop:~$ sudo apt update
..
here are the lines of the repos I update
--
--
Es wurden 102 kB in 2 s geholt (43,3 kB/s).
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 58 Pakete verfügbar. Führen Sie »apt list --upgradable« aus,


The above in german means that there are 58 packages availabel for updating. So you see, there are packages which need to be updated!! If I now run "sudo apt install" which is the same as you did, the following will happen.

Code:


davu@Ubuntu-Desktop:~$ sudo apt install
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 58 nicht aktualisiert.
davu@Ubuntu-Desktop:~$


You see....there was no package updated, nothing was installed and nothing was removed and!!!! 58 packages aren't updated. So the commands you are using are useless in your case. If you want to update (and upgrade) your system you need to do something else. First...sudo apt-get update doesn't mean your system is being updated. It's only the repositories you get your packages from which are being updated to give you the option to 'upgrade' to newer versions of your installed software. So in order to complete update your system you need to do the following:

- sudo apt-get update
- sudo apt-get upgrade -y

The "-y" is for answering an upcoming question if you really want to upgrade the available packages. It's a "yes/no"-question hence the "-y". You can remove that if you want to decide different. After that command (that might take some time to finish) your system is up-to-date.

Your Problem:

Your problem is not related to those commands. That's why I said, don't execute commands if you don't know what you are doing. If I look at your log I see:

non-working:
21:29:37.080 T:139705276688128 ERROR: GetDirectory - Error getting /media/alan/Pro RAID/Movies/The Mummy (2017)/

So, if I look at the path it seems you have some NAS where you save your movies and do a system mount of the shares, correct? Either the NAS is not ready up for the time you try to start the movie or the mount is not being done. It could also be, that you don't have a network connection after boot (do you have a SSD as the system drive?), because it might boot too fast and after a reboot you are lucky that the network service comes up faster.

Generally you know more than we about your system at home and how devices are connected. Unfortunately you missed to give us more informations about that. But the commands you executed are not related to your problem.

[spike3312]

Hi,

I have the same problem on 2 of my 3 media centres. This has appeared 2 days ago on one machine and yesterday on the second, the third is still working OK at the moment.

They are all the same machine, Acer net-top's which contain cloned drives so they all run the same sofrware and settings other than their hostnames and IP's.

They have been working fine for several years through the same upgrades until 2 days ago when these errors started appearing:

11:04:04.329 T:139823294736128   ERROR: GetDirectory - Error getting
11:04:09.817 T:139824681961536   ERROR: Previous line repeats 6 times.
11:04:09.817 T:139824681961536   ERROR: Error creating player for item smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E08 - The Beach (Buggy) Boys (Part 2).mkv (File doesn't exist?)
11:04:09.817 T:139824681961536   ERROR: Playlist Player: skipping unplayable item: 0, path [smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E08 - The Beach (Buggy) Boys (Part 2).mkv]
11:05:10.813 T:139822190556928  NOTICE: ES: Client  from ::ffff:10.7.86.107 timed out
11:05:45.698 T:139824681961536  NOTICE: Samba is idle. Closing the remaining connections
11:07:04.894 T:139824681961536   ERROR: Error creating player for item smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E08 - The Beach (Buggy) Boys (Part 2).mkv (File doesn't exist?)
11:07:04.894 T:139824681961536   ERROR: Playlist Player: skipping unplayable item: 0, path [smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E08 - The Beach (Buggy) Boys (Part 2).mkv]
11:08:35.648 T:139824681961536  NOTICE: Samba is idle. Closing the remaining connections
11:09:28.735 T:139822190556928  NOTICE: ES: Client  from ::ffff:10.7.86.107 timed out
11:09:35.560 T:139824681961536   ERROR: Error creating player for item smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E01 - The Holy Trinity.mkv (File doesn't exist?)
11:09:35.560 T:139824681961536   ERROR: Playlist Player: skipping unplayable item: 0, path [smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E01 - The Holy Trinity.mkv]
11:09:37.596 T:139824681961536   ERROR: Error creating player for item smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E01 - The Holy Trinity.mkv (File doesn't exist?)
11:09:37.596 T:139824681961536   ERROR: Playlist Player: skipping unplayable item: 0, path [smb://10.7.86.67/Videos/The Grand Tour/Season 01/S01.E01 - The Holy Trinity.mkv]
11:10:38.597 T:139822190556928  NOTICE: ES: Client  from ::ffff:10.7.86.107 timed out
11:11:08.640 T:139824681961536  NOTICE: Samba is idle. Closing the remaining connections

The season 1 episode 1 file was played on the machine in question only the day before and now it wont play a single file, including movies, tv shows or even MP3 files, yet 2 days before was all working fine.

I've not updated anything since installing 17.6 a few weeks ago.

I have removed the source loaction and added it again completing a library refresh in the process which went fine and shows all the files, if i go to the file list it shows ones i added today and adds them to the library.

I've tried downgrading to 17.5 and reupgrading to 17.6 with no success on either versions.

Any help would be apreciated.

Matt

[king107s]

non-working:
21:29:37.080 T:139705276688128 ERROR: GetDirectory - Error getting /media/alan/Pro RAID/Movies/The Mummy (2017)/

So, if I look at the path it seems you have some NAS where you save your movies and do a system mount of the shares, correct? Either the NAS is not ready up for the time you try to start the movie or the mount is not being done. It could also be, that you don't have a network connection after boot (do you have a SSD as the system drive?), because it might boot too fast and after a reboot you are lucky that the network service comes up faster.

I have a RAID array attached through USB3 directly to the Intel NUC which is using an SSD... There does not seem to be a mounting issue because during the same time that it will not play movies, it WILL play other media such as music.

Here is the configuration of the HTPC:
Intel NUC BOXD34010WYK1
4th Generation Intel Core i3-4010U processor
Intel HD Graphics 4400
Crucial 8GB Kit (4GBx2) DDR3 1600 MT/s (PC3 - 12800) CL11 SODIMM Notebook Memory Modules CT2KIT51264BF160B / CT2CP51264BF160B
Intel 530 SSDMCEAW080A401 mSATA 80GB SATA III MLC Internal Solid State Drive

[DaVu]

I have a RAID array attached through USB3 directly to the Intel NUC which is using an SSD... There does not seem to be a mounting issue because during the same time that it will not play movies, it WILL play other media such as music.

Maybe the music is located on another Disc in the RAID system which spins up faster. If you are talking about a RAID system I assume it's at least 2 discs in either a RAID1 or RAID0 (if more discs are in use it should be RAID5 or whatever)

Anyway, the commands you entered won't solve anything as you are executing them wrong and they won't affect Kodi at all.

For whatever reason Kodi can't connect to the mount directory or cannot read the folder. I'm not 100% sure why it behaves like that. You should debug your connections if that issue comes up and if you are able to reach the specific folder if you have the problem, that Kodi can't play the file.

Generally I would say that's not a Kodi issue. But we are willing to help. So please check if you are able to reach the movie folder if the error comes up again.

[DaVu]

@spike3312 

please don't hijack others threads. Open your own one and please don't post log snippets at the forums. Use a paste-service such as http;//pastebin.com

And always post full logs

[king107s]

I have a RAID array attached through USB3 directly to the Intel NUC which is using an SSD... There does not seem to be a mounting issue because during the same time that it will not play movies, it WILL play other media such as music.

Maybe the music is located on another Disc in the RAID system which spins up faster. If you are talking about a RAID system I assume it's at least 2 discs in either a RAID1 or RAID0 (if more discs are in use it should be RAID5 or whatever)

Anyway, the commands you entered won't solve anything as you are executing them wrong and they won't affect Kodi at all.

For whatever reason Kodi can't connect to the mount directory or cannot read the folder. I'm not 100% sure why it behaves like that. You should debug your connections if that issue comes up and if you are able to reach the specific folder if you have the problem, that Kodi can't play the file.

Generally I would say that's not a Kodi issue. But we are willing to help. So please check if you are able to reach the movie folder if the error comes up again.

It's a RAID0 array so it's distributed and not a situation of one drive versus another. I can see the array is mounted and all the files are accessible in the file browser. The hardware and cables are all the same as when it worked on previous versions. I think it's also worth mentioning that after the 'work around' that's not supposed to have caused any changes but temporarily makes the system work, I can play any movie for as long as the system is up. After a restart it goes back to not working. Doesn't that mean that the ports, cables and hardware work? I did post both log files... Can you deduce the difference between the two files that would make the movie files not play or be accessible? Do you have any suggestions for me to try to fix the problem? Seeing as the hardware is all the same I have a hard time believing it's not software related...

[spike3312]

Appologies for the code.

I don't see it as hijacking as i have a similar issue with the same error codes logged.

One machine did it after playing one file, i then pressed on the next file and got this error. Then returning to the previous file it had just finished playing gave the same error again which shouldnt be a mouting issue as it would have already been mounted at the time.

The other machine did it after a reboot the following day.

Full log: https://paste.ubuntu.com/26259044/

[DaVu]

@spike3312 

You are using a SMB connection to your files. The OP does something different. So it can't be the same.

Again, please stop hijacking threads and I also answered in your new thread and mentioned the banned repos you are using. So please let's continue over there after you removed the banned repos.

[king107s]

So, any ideas? What do I do now?

[DaVu]

That's the part, where it fails in the log above....

Code:

21:29:37.079 T:139706994071552 NOTICE: VideoPlayer: Opening: /media/alan/Pro RAID/Movies/The Mummy (2017)/The Mummy (2017).mkv
21:29:37.079 T:139706994071552 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:29:37.079 T:139706994071552   DEBUG: LinuxRendererGL: Cleaning up GL resources
21:29:37.079 T:139706994071552   DEBUG: CLinuxRendererGL::PreInit - precision of luminance 16 is 16
21:29:37.080 T:139705276688128   DEBUG: Thread VideoPlayer start, auto delete: false
21:29:37.080 T:139705276688128  NOTICE: Creating InputStream
21:29:37.080 T:139705276688128   ERROR: GetDirectory - Error getting /media/alan/Pro RAID/Movies/The Mummy (2017)/
21:29:37.080 T:139705276688128   ERROR: Previous line repeats 1 times.
21:29:37.080 T:139705276688128   ERROR: CVideoPlayer::OpenInputStream - error opening [/media/alan/Pro RAID/Movies/The Mummy (2017)/The Mummy (2017).mkv]
21:29:37.080 T:139705276688128  NOTICE: CVideoPlayer::OnExit()

That's the part where it works....

Code:

21:39:14.722 T:140693225715712  NOTICE: VideoPlayer: Opening: /media/alan/Pro RAID/Movies/The Mummy (2017)/The Mummy (2017).mkv
21:39:14.722 T:140693225715712 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:39:14.722 T:140693225715712   DEBUG: LinuxRendererGL: Cleaning up GL resources
21:39:14.724 T:140693225715712   DEBUG: CLinuxRendererGL::PreInit - precision of luminance 16 is 16
21:39:14.724 T:140690613085952   DEBUG: Thread VideoPlayer start, auto delete: false
21:39:14.724 T:140690613085952  NOTICE: Creating InputStream
21:39:14.808 T:140690613085952   DEBUG: ScanForExternalSubtitles: Searching for subtitles...
21:39:14.808 T:140690613085952   DEBUG: ScanForExternalSubtitles: END (total time: 0 ms)
21:39:14.808 T:140690613085952  NOTICE: Creating Demuxer
21:39:14.836 T:140690613085952   DEBUG: Open - probing detected format [matroska,webm]
21:39:14.858 T:140690613085952   DEBUG: Open - avformat_find_stream_info starting
21:39:14.981 T:140690613085952   DEBUG: ffmpeg[7FF516042700]: [matroska,webm] Could not find codec parameters for stream 3 (Subtitle: hdmv_pgs_subtitle): unspecified size
21:39:14.981 T:140690613085952   DEBUG: ffmpeg[7FF516042700]: [matroska,webm] Consider increasing the value for the 'analyzeduration' and 'probesize' options
...
...

After that, the movie starts. So you see, the log isn't very helpful in that regard. For what I can see, it tells for the non-working part, that it can't reach the folder/directory (for whatever reason). For the working part, it can reach it. The first commands you mentioned won't affect this situation. That's why I said they are useless.

What I would do now is to check if you can reach the folder at that point Kodi can't reach it (when the movie doesn't play). If you can't reach the folder as well, then probably a dmesg | pastebinit would give more helpful information. If you can reach the folder while Kodi can't, I'm a bit clueless, tbh.

[king107s]

That's the part, where it fails in the log above....

Code:

21:29:37.079 T:139706994071552 NOTICE: VideoPlayer: Opening: /media/alan/Pro RAID/Movies/The Mummy (2017)/The Mummy (2017).mkv
21:29:37.079 T:139706994071552 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:29:37.079 T:139706994071552 DEBUG: LinuxRendererGL: Cleaning up GL resources
21:29:37.079 T:139706994071552 DEBUG: CLinuxRendererGL::PreInit - precision of luminance 16 is 16
21:29:37.080 T:139705276688128 DEBUG: Thread VideoPlayer start, auto delete: false
21:29:37.080 T:139705276688128 NOTICE: Creating InputStream
21:29:37.080 T:139705276688128 ERROR: GetDirectory - Error getting /media/alan/Pro RAID/Movies/The Mummy (2017)/
21:29:37.080 T:139705276688128 ERROR: Previous line repeats 1 times.
21:29:37.080 T:139705276688128 ERROR: CVideoPlayer::OpenInputStream - error opening [/media/alan/Pro RAID/Movies/The Mummy (2017)/The Mummy (2017).mkv]
21:29:37.080 T:139705276688128 NOTICE: CVideoPlayer::OnExit()

That's the part where it works....

Code:

21:39:14.722 T:140693225715712 NOTICE: VideoPlayer: Opening: /media/alan/Pro RAID/Movies/The Mummy (2017)/The Mummy (2017).mkv
21:39:14.722 T:140693225715712 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:39:14.722 T:140693225715712 DEBUG: LinuxRendererGL: Cleaning up GL resources
21:39:14.724 T:140693225715712 DEBUG: CLinuxRendererGL::PreInit - precision of luminance 16 is 16
21:39:14.724 T:140690613085952 DEBUG: Thread VideoPlayer start, auto delete: false
21:39:14.724 T:140690613085952 NOTICE: Creating InputStream
21:39:14.808 T:140690613085952 DEBUG: ScanForExternalSubtitles: Searching for subtitles...
21:39:14.808 T:140690613085952 DEBUG: ScanForExternalSubtitles: END (total time: 0 ms)
21:39:14.808 T:140690613085952 NOTICE: Creating Demuxer
21:39:14.836 T:140690613085952 DEBUG: Open - probing detected format [matroska,webm]
21:39:14.858 T:140690613085952 DEBUG: Open - avformat_find_stream_info starting
21:39:14.981 T:140690613085952 DEBUG: ffmpeg[7FF516042700]: [matroska,webm] Could not find codec parameters for stream 3 (Subtitle: hdmv_pgs_subtitle): unspecified size
21:39:14.981 T:140690613085952 DEBUG: ffmpeg[7FF516042700]: [matroska,webm] Consider increasing the value for the 'analyzeduration' and 'probesize' options
...
...

After that, the movie starts. So you see, the log isn't very helpful in that regard. For what I can see, it tells for the non-working part, that it can't reach the folder/directory (for whatever reason). For the working part, it can reach it. The first commands you mentioned won't affect this situation. That's why I said they are useless.

What I would do now is to check if you can reach the folder at that point Kodi can't reach it (when the movie doesn't play). If you can't reach the folder as well, then probably a dmesg | pastebinit would give more helpful information. If you can reach the folder while Kodi can't, I'm a bit clueless, tbh. 

 So after you mentioned about the commands being irrelevant and that if/when I were using them it should have been update and then upgrade, I experimented a bit to see what commands and order would reproduce the 'fix' and what would not. I found that the dist-upgrade was not necessary at all and that i had to restart after the commands in ubuntu because logging off and back into kodi without the restart did not work. 

Exit Kodi and enter Ubuntu
Open command terminal
sudo  apt-get update
sudo apt-get upgrade
Restart the system
Log off Ubuntu and back into Kodi
Movies play with no problem.

So I first started with a restarted system where the movies would not play. I confirmed that the volume was mounted and went through the file manager and was able to access all kinds of content within the movie folders. I exited and used the dmesg command and then got the system working as described above and used the dmesg command again for comparison. But to your point I can access the data when kodi cannot so I'm not sure if these two logs will help you or not....

Maybe a fresh install is required.

Movies Won't play: https://paste.ubuntu.com/26285649/

Movies play, system works normally: https://paste.ubuntu.com/26285669/

Again, thanks for your continued help on this issue, it is much appreciated!

[DaVu]

I guess it's a problem with the USB NAS (whatever that is) you are using.

I can't help anymore as you didn't show us the dmesg for comparsions.

[king107s]

I guess it's a problem with the USB NAS (whatever that is) you are using.

I can't help anymore as you didn't show us the dmesg for comparsions.

The dmesg links are at the bottom of the previous post... Is that not the right thing?