Kodi Community Forum

Using the Library Auto Updater add-on (https://kodi.wiki/view/Add-on:XBMC_Library_Auto_Update 2) and it is fine when updating the audio library but when it updates the video library it seems to go into a loop.
I have run it with debug on and pasted the results here https://paste.osmc.tv/kigadokita 1
The loop constantly displays messages on the screen (when the add-on is run manually) Saying Compressing database, and searching for data on the TVDB database.
The log shows these messages when running using the “RUN” option on the Settings>Add-on browser>Library Auto Update screen

Quote:2021-10-27 11:26:58.064 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:26:58.266 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:26:58.714 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:26:59.170 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:26:59.631 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:26:59.823 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:00.253 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:00.483 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:00.880 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:01.074 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:01.547 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:01.741 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:02.197 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:02.389 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:02.820 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:03.063 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:03.447 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:03.649 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:04.097 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:04.293 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:04.714 T:866 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:27:04.905 T:866 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:27:05.330 T:866 INFO : VideoInfoScanner: Starting scan …

When I invoke an update of the library from the context menu the update runs as expected with no issues

Quote:2021-10-27 11:08:27.154 T:729 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:08:27.491 T:729 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:08:40.554 T:729 INFO : VideoInfoScanner: Starting scan …
2021-10-27 11:08:40.740 T:729 INFO : VideoInfoScanner: Finished scan. Scanning for video info took 00:00
2021-10-27 11:08:43.160 T:739 INFO : initializing python engine.
2021-10-27 11:08:45.765 T:739 INFO : CPythonInvoker(15, /home/osmc/.kodi/addons/script.skinshortcuts/default.py): script successfully run
2021-10-27 11:08:46.380 T:739 INFO : Python interpreter stopped
 

Kodi (OSMC) is running on a Raspberry Pi The files for the library are held on another Raspberry Pi acting as a file server.

Two things...

1) You already gave a URL-link of the full OSMC log file. So there is no need to splatter log parts into the forum as wall, especially 10+ identical log entries. We try to keep our forum (server) clean.

2) Specific OSMC technicalities are best handled at the OSMC forum. It's a bit like offering your BMW to a Mercedes garage for repairs.

(2021-10-27, 09:02)Klojum Wrote: [ -> ]Two things...

1) You already gave a URL-link of the full OSMC log file. So there is no need to splatter log parts into the forum as wall, especially 10+ identical log entries. We try to keep our forum (server) clean.

2) Specific OSMC technicalities are best handled at the OSMC forum. It's a bit like offering your BMW to a Mercedes garage for repairs.

Two answers...
1) I am sorry.
2) OSMC claim it is not their fault.

Problem fixed by reverting to 1.2.1.