Identify access in log to file recentlyaddedmovies.xml

Identify access in log to file recentlyaddedmovies.xml - Printable Version

+- 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: Identify access in log to file recentlyaddedmovies.xml (/showthread.php?tid=335890)

Identify access in log to file recentlyaddedmovies.xml - ctawn - 2018-09-26

I'm not sure if there's a problem here, but while debugging other issues in the log I am finding this near the top of the log after Kodi first boots:

:
10:42:35.779 T:4056937216 ERROR: GetDirectory - Error getting library%3a%2f%2fvideo%2frecentlyaddedmovies.xml%2f/

10:42:35.780 T:4056937216 ERROR: Previous line repeats 3 times.

10:42:35.780 T:4056937216 ERROR: GetDirectory - Error getting

10:42:36.066 T:4076892752 ERROR: Previous line repeats 7 times.]

The path is obviously wrong there, but how can I tell what's trying to access it so I can fix it? I'm thinking since it's close to right after boot, it's not a skin-dependent issue, but could be wrong…

RE: Identify access in log to file recentlyaddedmovies.xml - Klojum - 2018-09-26

Provide a full kodi.log file via a pastebin website, errors can start earlier than assumed.

RE: Identify access in log to file recentlyaddedmovies.xml - ctawn - 2018-09-26

(2018-09-26, 17:04)Klojum Wrote: Provide a full kodi.log file via a pastebin website, errors can start earlier than assumed.

Alright, thanks. (noted)

Identify access in log to file recentlyaddedmovies.xml - Klojum - 2018-09-26

The forum moderators have determined that banned addons (wiki) are present on your system. To receive assistance here, these banned items must be removed. If a clean log is not submitted within 3 days, then the relevant post(s) will be removed after this time.

RE: Identify access in log to file recentlyaddedmovies.xml - ctawn - 2018-09-26

Thanks for your understanding. Hopefully uninstalled the right offending plugins (which, not to be too defensive, but I was just checking out and never actually accessed content, but…)

Here's hopefully a clean log. Smile

Same lines as in headpost still appear. TIA.

RE: Identify access in log to file recentlyaddedmovies.xml - DarrenHill - 2018-09-27

You've still got several banned addon (wiki) repos installed:

115.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.podgod
118.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.whitecream
121.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.xbmchub
122.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository incursion.repository
123.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.iceballs

Also debug logging is not enabled, so a lot of information is missing.

RE: Identify access in log to file recentlyaddedmovies.xml - ctawn - 2018-09-27

(2018-09-27, 10:48)DarrenHill Wrote: You've still got several banned addon (wiki) repos installed:

115.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.podgod
118.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.whitecream
121.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.xbmchub
122.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository incursion.repository
123.17:22:22.914 T:4079317584 NOTICE: ADDONS: Using repository repository.iceballs

Also debug logging is not enabled, so a lot of information is missing.

Gah. FYI, podgod doesn't seem to be listed in the wiki at all. Others I didn't turn up cuz of the way I searched the page and the spacing, or being listed in the addon rather than repo section. My fault, too, too careless. Anyway, again apologies and thanks for your understanding. If you'd care to still address the original issue, here's the log again (3rd time's the charm.), this time in debug mode, with those repos removed. If I'm still a criminal, I give up. Smile

In the debug log, I noticed that it comes in a section related to super.favourites addon. I tried to debug this a little myself. Inspected the addon's data folder's .xml files, and could see nothing related in any of them. Deleted the whole addon data folder and restarted Kodi, with same log entries.

:
10:54:28.587 T:3714052864 DEBUG: CPythonInvoker(15, /home/osmc/.kodi/addons/plugin.program.super.favourites/service.py): entering source directory /home/osmc/.kodi/addons/plugin.program.super.favourites 10:54:28.640 T:4081336912 DEBUG: CDirectoryProvider[library%3a%2f%2fvideo%2frecentlyaddedmovies.xml%2f/]: refreshing.. 10:54:28.641 T:4061131520 ERROR: GetDirectory - Error getting library%3a%2f%2fvideo%2frecentlyaddedmovies.xml%2f/]

This whole thing is sort of unimportant, but it's really bugging me. Smile

RE: Identify access in log to file recentlyaddedmovies.xml - DarrenHill - 2018-09-27

You've missed one:

10:54:19.698 T:4081336912 DEBUG: ADDON: cpluff: 'Plug-in plugin.video.1channel has been installed.'

Get rid of that and you're good to go.

The simplest test would be to temporarily disable super favourites and see if it removes the issue. If so ask in its support thread about it.

RE: Identify access in log to file recentlyaddedmovies.xml - Klojum - 2018-09-27

(2018-09-27, 21:17)ctawn Wrote: FYI, podgod doesn't seem to be listed in the wiki at all

FYI, as per that same wiki page: "This list is only an example. Due to the dynamic nature of Piracy streams and the add-ons that access them, it is impossible to list all Builds/Repositories/Add-ons that violate the forum rules".

This is apparently an OSMC setup, so perhaps @Sam.Nazarko can help out a bit.

RE: Identify access in log to file recentlyaddedmovies.xml - ctawn - 2018-09-28

(2018-09-27, 22:51)DarrenHill Wrote: The simplest test would be to temporarily disable super favourites and see if it removes the issue. If so ask in its support thread about it.

I disabled it and line still appears in debug log. So Super Favourites not the culprit. This time it appears after this line:

Code:
22:56:37.631 T:3817861888   DEBUG: CPythonInvoker(3, /home/osmc/.kodi/addons/service.library.data.provider/service.py): instantiating addon using automatically obtained id of "service.library.data.provider" dependent on version 2.25.0 of the xbmc.python api

service.library.data.provider has no corresponding files in userdata/addon_data. however the addon itself is installed in .kodi/addons. don't know what installed it. I'm guessing an xonfluence skin wiget. it's service.py has the following lines:

:
def _fetch_recent(self):

LIBRARY._fetch_recent_movies()]

What would that in turn be calling, and more importantly, what would it be referencing to get that stale/inaccurate URL?

RE: Identify access in log to file recentlyaddedmovies.xml - DarrenHill - 2018-09-28

The add-on is in the official repo - Add-on:Library_Data_Provider (wiki). As you say it's a skin helper so perhaps your Xonfluence thought is on the money.

Simplest way to check is to close Kodi, rename your .kodi folder to something else and restart again. Kodi will build a new one and start factory fresh. You can then see if by default it's there (if Estuary has it as a dep) or if adding Xonfluence again installs it as a dependency.

Once you're done, close Kodi, delete the new .kodi folder and rename the old one back should restore things to how they were before.