+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: No nfo-files can be written when exporting database to "separate" (/showthread.php?tid=342421)
No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
This problem accurs on my Win10-PC and on my Android Media-Players (Zidoo) as well.
My media-files are located on a NAS server (Thecus) which is connected by LAN.
I set up a NFS share and made it public. It's working very well as my source.
There is absolutely no problem with writing on and copying to the NAS, e.g. in Android I can copy files via file-manager (TotalCommander) from Kodi-folder to any of the media folders on the NAS.
BUT... when I want to export the database using the "separate" method, it comes a little bit to Voodoo... After starting it, there comes an error message immediately popping up that Kodi cannot write into the folder, followed by the complete NFS-share / media-folder in which Kodi wants to write to. As if the folder is write protected. But actually it's NOT ... as you will see...
The result: Absolutely no NFO files were written, BUT tons of poster and fanart JPGs.... (
?) !!!Repeating the export without art and poster results in the same error message and absolutely no files to be copied. At the end there is a message that XYZ files could not be exported.
So it seems, that the problem is with NFO files only, as long as Kodi wants to write them onto the NAS into the NFS share.
Copying a nfo.file "by hand" using a file manager is no problem at all.
So what's the problem...?? My fault ? A bug...??
Got no ideas left...
RE: No nfo-files can be written when exporting database to "separate" - Karellen - 2019-03-25
A debug log which captures the following...
1. Update Library, then
2. Export to Separate files
Guide... https://forum.kodi.tv/showthread.php?tid=323719&pid=2665079#pid2665079
RE: No nfo-files can be written when exporting database to "separate" - Klojum - 2019-03-25
(2019-03-25, 21:23)tom.58 Wrote: So what's the problem...?? My fault ? A bug...??Are you using Kodi's internal NFS sourcing, or an OS-based NFS share?
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
Well, I thing I am using Kodi's internal NFS sourcing....
RE: No nfo-files can be written when exporting database to "separate" - Klojum - 2019-03-25
It might use a different Linux user than when you connect with your File Manager TotalCommander.
Can you test if you can you store subtitles via Kodi? If so, then all should be working.
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
(2019-03-25, 21:52)Klojum Wrote: Can you test if you can you store subtitles via Kodi? If so, then all should be working.
Well ...I never did before.... how can I do this ?
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
(2019-03-25, 21:31)Karellen Wrote: A debug log which captures the following...The guide says that you only need complete logs....
1. Update Library, then
2. Export to Separate files
There are more than 1000 entries in my database... so there are about 1000 identical messages in the log about no access to the media folder. You may want me to cut 980 of these messages out of the logfile....(??) Is that ok for you ?
RE: No nfo-files can be written when exporting database to "separate" - Karellen - 2019-03-25
I would prefer that you did not. When people do that in the past, they always end up cutting out one or two lines mixed in with the identical messages and, as luck would have it, they are the lines we are looking for.
Upload to https://paste.ubuntu.com/ if it is too big for https://paste.kodi.tv/
But if you can already see the errors, then there is a problem with the shares and klojum's advice will need to be followed
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
(2019-03-25, 21:52)Klojum Wrote: Can you test if you can you store subtitles via Kodi? If so, then all should be working.Well, in playmode I found the option to download subtitle. Is that what you mean ?
And yes, I could download subtitles to /mnt/somewhere (?) and it was successful.
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
(2019-03-25, 22:32)Karellen Wrote: I would prefer that you did not. When people do that in the past, they always end up cutting out one or two lines mixed in with the identical messages and, as luck would have it, they are the lines we are looking for.This time exporting to separate files showing the same results as before. All of the JPGs (poster & fanart) were exported and written to each of the media folders on my NAS. BUT absolutely no NFO file was written / exported !! Strange behaviour.... AND the error message came up telling for each folder that it's not possible to write into it.
Upload to https://paste.ubuntu.com/ if it is too big for https://paste.kodi.tv/
But if you can already see the errors, then there is a problem with the shares and klojum's advice will need to be followed
The logfile seems to be too big for ubuntu as well.... I tried 4 times now always getting an error and a Bad Gateway ...
What to do...?
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-25
Oh, what I forgot to tell you.... In every media-/ film folder there is a hidden folder called ".actors" which seems to be write protected (not by me !!). It's not possible to delete these folders permanently. After you deleted them, they are back after some seconds automatically. Voodoo...
RE: No nfo-files can be written when exporting database to "separate" - Karellen - 2019-03-25
(2019-03-25, 23:49)tom.58 Wrote: Oh, what I forgot to tell you.... In every media-/ film folder there is a hidden folder called ".actors" which seems to be write protected (not by me !!). It's not possible to delete these folders permanently. After you deleted them, they are back after some seconds automatically. Voodoo...Yes, that is part of the Export function. It is where the Actors images are stored. If you do not want them, then do not select "Export Actors Images" in Export.
(2019-03-25, 23:21)tom.58 Wrote: The logfile seems to be too big for ubuntu as wellOk, then cut it down and lets see if it provides enough information.
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-26
(2019-03-25, 23:53)Karellen Wrote: Ok, then cut it down and lets see if it provides enough information.This is part #1 log ->"Scraper / updating"
Part #2 log -> Export seperate
Part # 3 log -> Export seperate
I add a first log of exporting to seperate without JPGs, taken some hours before the one above. It was cut to short.
LOG of Export to separate (cut version) without JPGs
RE: No nfo-files can be written when exporting database to "separate" - Karellen - 2019-03-26
Thanks.
It definitely looks like a permission issue. The end of the above line states the current permission is --- but the required permission is rw-xml:ERROR: CNFSFile::Open: Unable to open file : '//media/Filme - 0 - F/72 Stunden/BDMV/index.nfo' error : 'open call failed with "NFS: ACCESS denied. Required access rw-. Allowed access ---"'
There is nothing we can do to fix that as it is Network related. You will need to check your permissions. Hopefully someone will come along and guide you with NFS if you can't figure it out.
RE: No nfo-files can be written when exporting database to "separate" - tom.58 - 2019-03-26
(2019-03-26, 00:42)Karellen Wrote: It definitely looks like a permission issue. The end of the above line states the current permission is --- but the required permission is rw-Well, I wonder if the line above just concerns the .actor folder, which seems to be write-protected. (?)
And I can't understand then why all of the JPGs CAN be written to all these folders (!) , but just no NFO files.... I think permission can not be --- in this case. (?)
Thanks for help so far !