Kodi Community Forum

Full Version: Leia beta 5 - scan for new content (update library) crashes Kodi on Xbox One (SMB)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
So this is exactly the same issue as I've previously reported with Beta 3 here - https://forum.kodi.tv/showthread.php?tid=336402

As I have now got Beta 5 installed and the exact same issue, I'm creating a new thread and have captured fresh Debug logs with the SMB Component specific logging also enabled.

Debug Log: http://paste.kodi.tv/jusodupica

Environment: Xbox One (original) running 10.0.17763 (Insider Omega ring I think it is.. the ring you get updates just before they release to public), LAN connected, content sitting on a Windows server 2012 R2 box accessed via SMB.

The last time that this worked for me was Leia Beta 2. Both Beta 3 and Beta 5 (I never got Beta 4) crash when I try and run any (i.e. Music, TV Shows, Movie) library update.
As before, I can play the existing content that was previously scanned in under beta 2. So accessing the SMB share to play content is fine, but initiating a content scan causes it to crash.

The same as last time, the following lines in the Debug Log appear to highlight the error:
Quote:12:12:12.382 T:488   DEBUG: ------ Window Init (DialogExtendedProgressBar.xml) ------
12:12:12.391 T:1904  NOTICE: VideoInfoScanner: Starting scan ..
12:12:12.391 T:4756   DEBUG: CAnnouncementManager - Announcement: OnScanStarted from xbmc
12:12:12.391 T:4756   DEBUG: GOT ANNOUNCEMENT, type: 16, from xbmc, message OnScanStarted
12:12:12.410 T:1904   ERROR: AddOnLog: SMB support (libsmb2): SMB2: connect to share 'tvshows' at server '192.168.0.140' failed. Session setup failed with (0xc00000cc) STATUS_BAD_NETWORK_NAME.
12:12:12.410 T:1904 WARNING: VIDEO::CVideoInfoScanner::Process directory 'smb://192.168.0.140/tvshows/' does not exist - skipping scan.
Do you have ambilights installed?
(2018-11-03, 03:52)Karellen Wrote: [ -> ]Do you have ambilights installed?
 I do have LIFX smart lights and an add-on (script.kodi.lifx.ambilight) installed to automate them.
The errors generated by the addon are my local DNS filter (AdGuard Home) blocking the Google analytics DNS lookups.

The issue predates installing this add-on but I'm happy to uninstall it and collect fresh logs to validate and declutter the log.
Here we go, fresh Debug Log with the LIFX Ambilight addon disabled: https://paste.kodi.tv/makeqikate
I also have a few LIFX bulbs in my house, but I have never had any Kodi Add-Ons that controlled them. I use Siri to control them.

Besides, wtf would my smartlights have to do with Kodi not updating my library properly?
(2018-11-05, 19:55)UraFarquad Wrote: [ -> ]I also have a few LIFX bulbs in my house, but I have never had any Kodi Add-Ons that controlled them. I use Siri to control them.

Besides, wtf would my smartlights have to do with Kodi not updating my library properly?
 I agree, but given the nature of this problem it's no problem for me to remove components on my Kodi config to help rule things out and clean up the debug log a little.
STATUS_BAD_NETWORK_NAME means that a share doesn't exist. Make sure that the share tvshows exists and works.
Thanks @afedchin and great to see you back!

I now suspect there is more than 1 problem based on your response and further testing I've been conducting (fresh debug log link below).

In response to your feedback:
Quote:STATUS_BAD_NETWORK_NAME means that a share doesn't exist. Make sure that the share tvshows exists and works.

I can confirm that that share is NOT the share name as configured in my sources.

The TV Shows shource is configured as smb://192.168.0.140/Videos/TV Shows (note: the space between TV and Shows, i.e. /TV[space]Shows)

I can play video content either from the TV Shows node using library (populated with content through to Beta 3 after which it broke), and also by browsing to it via the Videos node so I know that connection to the /TV Shows share is working fine.
The only place it fails is on scanning for new content (i.e. Update Library) and it appears that the space in the share name is being incorrectly handled, and ultimately removed, thus resulting in the attempt to connect to a share name that does not exist (i.e. /TVShows). 


In addition to this, if I only go into the Music node and attempt to perform an 'Update Library' from here, Kodi will also crash after about 20 seconds.

This looks to possibly be a different problem based on the Debug Log here - https://paste.kodi.tv/bibeyuperu
Quote:13:39:18.795 T:9064   DEBUG: CAnnouncementManager - Announcement: OnUpdate from xbmc
13:39:18.795 T:9064   DEBUG: GOT ANNOUNCEMENT, type: 32, from xbmc, message OnUpdate
13:39:19.230 T:756   DEBUG: MUSIC_INFO::CMusicInfoScanner:Big GrinoScan Scanning dir 'smb://192.168.0.140/music/'Til Tuesday - Voices Carry (2012 Reissue) (1985)/././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././' as not in the database
13:39:19.318 T:756   DEBUG: AddOnLog: SMB support (libsmb2): SMB2: opened 'Til Tuesday - Voices Carry (2012 Reissue) (1985)\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\01 - 'Til Tuesday - Voices Carry - Love in a Vacuum.mp3
13:39:19.358 T:756   DEBUG: unrecognized ID3 frame detected: TDAT
13:39:19.359 T:756   DEBUG: unrecognized ID3 frame detected: TDOR
13:39:19.359 T:756   DEBUG: unrecognized ID3 frame detected: TMED
13:39:19.359 T:756   DEBUG: unrecognized ID3 frame detected: TSRC
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:SCRIPT
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:ASIN
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:originalyear
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:BARCODE
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:CATALOGNUMBER
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:MusicBrainz Album Status
13:39:19.359 T:756   DEBUG: unrecognized user text tag detected: TXXX:MusicBrainz Album Release Country
13:39:19.360 T:756   DEBUG: unrecognized user text tag detected: TXXX:MusicBrainz Release Track Id

The MP3 files were tagged using MusicBrainz Picard 2.0.4 and Mp3tag v2.90a
Thanks again for all your help. Let me know if there is any other data I can provide.
I think I've possibly found where the 'bad path' is coming from causing the crash, however, I'm not sure how to solve it.
The music scanning issue I've also raised in my previous post I think I'll create a new thread for as it may be a completely different issue.

First up, a fresh Debug log based on the recently pushed RC5 build for Xbox - https://paste.kodi.tv/ivuvabofin

The key lines right at the end appear to be:
Quote:21:25:58.905 T:8088   ERROR: AddOnLog: SMB support (libsmb2): SMB2: connect to share 'tvshows' at server '192.168.0.140' failed. Session setup failed with (0xc00000cc) STATUS_BAD_NETWORK_NAME.
21:25:58.906 T:8088 WARNING: VIDEO::CVideoInfoScanner:Tonguerocess directory 'smb://192.168.0.140/tvshows/' does not exist - skipping scan.
However, I have no such path defined in my sources.xml (link here - https://pastebin.com/sHUNaMjU)
My TV shows path is clearly defined as smb://192.168.0.140/videos/tv shows/
Quote:        <source>
            <name>TV Shows</name>
            <path pathversion="1">smb://192.168.0.140/videos/tv shows/</path>
            <allowsharing>true</allowsharing>
        </source>
When I went and checked inside the MyVideos113.db, I did find it in the Path table:

Image

So my questions are now:
  1.  Is this path str in my MyVideos113.db what is being referenced just before the crash?
  2.  If this is the cause of my problem, how do I rectify it? I know I can use File Manager in Kodi on Xbox One to copy the MyVideos113.db file out to a location to review it (as I've done), but will Kodi let me copy it back using File Manager? Or is it file locked and it won't work? If it won't work, what are my options beyond nuking it and rescanning my entire library from scratch?