The Kodi repository is up to date and so are the Nexus branches of aforementioned repo urls. What is going on?
It seems to be a recurring theme as I search around the support section, even an old topic from [myself] (OSMC addon repository addons.xml hickup? - #2 by sam_nazarko). If the mirrors don’t provide reliability, what would be the best way to circumvent the osmc mirrors and just use Kodi’s mirrors instead?
Thanks for the report. Your previous post is three years old and there have been a number of improvements since then. Even then, your situation seemed to be revolved around the fact you were using a specific mirror.
The mirrors are kept in sync on a twice daily basis. Any further synchronisation does not really yield significant benefit. We used to also increase the repository update frequency for OSMC users on our mirrors vs the Kodi standard settings, but again this yielded no benefit. For users, the repository usually updates while they are asleep. If it’s urgent, it can be manually updated (as explained below).
Without any logs, it’s hard to confirm what your issue is. I have however checked the mirror system and can confirm what we serving is up to date. Please see as follows:
The file /osmc/download/kodi/addons/omega/addons.xml has a size of 8.7 MB (9080352 bytes) and was last modified on Wed, 23 Oct 2024 12:49:14 UTC.
You have checked manual mirrors but the OSMC mirror direction system will always point you to a mirror with up to date resources, so even if an individual mirror is outdated, it will not be used. You can see all mirrors currently serving this file correctly as follows:
However you should also pay attention to this commit:
The next update will revert back to the Kodi mirror system directly. We have chosen to do this as the Kodi mirror system’s reliability has improved significantly over the years and there is now little need to mirror it ourselves.
I suspect there may be a caching issue on your side as we haven’t had other reports of this since 12th October (as you quoted) which was quite a while ago. I have also checked my home system and can see it updated on 23rd October, which was the date of the last repository update.
You could try manually refreshing the repository in Kodi. If you still experience an issue then I would encourage you to post some logs.
Yes my old post was 3 years old, but there was also a thread this year (Kodi addons repository not up to date) and from glancing across the forums I got the impression that addons were more often missing or being out of sync.
The mirror mirrors.dotsrc.org is still behind (but I understand it is out of OSMC’s control):
ftp.fau.de was behind too when I checked, I wish I had made a screenshot (and I did from desktop, not from OSMC, making caching a less likely cause). Thankfully this one seems to be up-to-date now.
I resolved the issue on my end by un-hijacking the repository.xbmc.org package and list the original mirrors.kodi.tv url’s there, hacky and probably temporary but it was enough to trigger a bunch of updates. The mentioned commit is welcomed a lot! Hopefully less hassle for you, me, and everyone.
It does not matter if an individual mirror is out of date. The mirror system will simply not redirect traffic to it and route it to one that is up to date. If you check individual mirrors, you will of course find ones that are out of date
Probably worth keeping in mind that the same mirror system serves updates and downloads, so it is pretty reliable.
The link to the post you provided was caused by Kodi’s mirror system being slow. This is an external factor and won’t be improved by the change we have made. However: we won’t be blamed for it anymore
I’m encountering a similar issue with add-on updates on my Vero4K running Kodi v21.1. I can’t update to the latest version of the OzWeather add-on through the default Vero4K repository - only v2.1.1 is available, while the developer claims the latest is v2.1.3.
After troubleshooting with the add-on developer, he suggested that OSMC may be using its own mirrors instead of the standard Kodi repository, and these mirrors are not showing the latest versions. He found in my logs that Kodi on Vero4K accessing the OSMC mirror at Index of /osmc/osmc/download/kodi/addons/omega/weather.ozweather, where only version 2.1.1 is available, while v2.1.3 is present on the Kodi mirrors.
I wanted to start a new thread but noticed there’s an ongoing discussion. Is there a way to ensure the latest add-on versions sync correctly, or an alternative to update OzWeather without manually installing it from GitHub (to preserve auto-update functionality)?
Thank you for your reply. I checked Kodi on Vero4K again, and it still shows OzWeather at version 2.1.1, with no update available. The link I provided appears to have come from my log, which I shared on the Kodi forum, but I’m not familiar with the specifics of Kodi repository mirrors.
If needed, I can provide another log. As I said, I haven’t seen any updates for this add-on in the past few days.
After running “Check for updates,” I still couldn’t see any add-on updates. However, on the OzWeather add-on screen, selecting “Versions” in the left menu revealed a pop-up showing both v2.1.3 (Kodi Add-on repository) and v2.1.1 (Local package cache). Choosing v2.1.3 installed it successfully, so I’m now on the latest version. This manual approach isn’t ideal, as it’s not practical to check each add-on individually. I’d like to understand what’s going on with my setup.
For full logs, I followed the OSMC Wiki guidance to enable debugging under Settings > System > Logging, but I couldn’t find the “Enable Debugging” option there. The only options visible are:
Enable component-specific logging
Enable event logging
Has this menu changed in the latest Kodi version? If so, what should I select, and should the Wiki page be updated?
Typically, I use the Aeon Nox Silvo skin, but for testing, I switched to the standard OSMC skin. With settings on Expert, I still see only the options for “Enable component-specific logging” and “Enable event logging.”:
Regarding add-on updates, my setting is to “notify, but don’t install updates.” However, since upgrading to Kodi v21.1 a couple of weeks ago, I haven’t received any prompts to update add-ons:
I have not tested the ‘notify, but don’t install updates’ option.
The ‘enable debug logging’ option is usually situated above ‘enable component logging’.
If it is not present, it may be because this setting has been overridden. It’s possible you enabled debug logging in the past via advancedsettings.xml. One reason for doing this would be to stop the visibility of the GUI overlay, which is not configurable via Kodi’s interface.
If you upload a log, we should be able to verify whether this is the case.
I checked my advancedsettings.xml file and found the line <loglevel>1</loglevel>. Could this be why I don’t see the “Enable Debug Logging” option in the menu? If so, should I remove or adjust this line to enable debug logging from the interface? I’m happy to make changes to provide the full logs and hopefully get to the bottom of the add-ons database issue.
I’ve removed the <loglevel>1</loglevel> line from advancedsettings.xml, which brought back the debug logging option in the menu. After enabling debug logging, I restarted the Vero4K twice and then ran “Check for updates” from the add-on screen. Here’s the link to the full debug log:
There doesn’t seem to be any issue with the add-ons database from a cursory glance.
FYI: as of the October update, Kodi mirrors are used directly again for add-on updates.
Thanks for clarifying! I did a manual check for add-on updates and initially found none. However, after reading your message, I checked for an OSMC update and found the October update. Once installed, a dozen add-on updates appeared in the add-ons screen, and I was able to update them all without any issues.
It seems the problem is resolved. Thank you very much for your help!
