temurin-11-jre and temurin-17-jdk Debian package aren't served properly on JFrog #1006
Comments
|
adoptium/installer#810 to resolve this |
|
I also believe these packages should now be being served properly. |
|
@hdurand-artic Can you try again and let us know? |
|
This is odd. I just performed a quick new test on Debian 12 (bookworm) on x64 and 11-jre installed ok but 17-jdk didn't. I tried the install several times with the same results, then paused for a minute or so before trying the EDIT: Tried in a new docker container after the above and it worked ok straight away with |
|
@karianna Some errors are still here, including on new packages: Some of them are indeed broken in JFrog - for example:
but, weirdly enough, not all of them: - for example:
|
|
I've checked all of these artifacts ( and re-uploaded them, and checked again! ), and it appears all are present and correct, there may be an issue with the jfrog web UI, when clicking on the location page. but for me at least, it then redirects to the correct artifact when browsing, e.g... https://packages.adoptium.net/ui/repos/tree/General/deb/pool/main/t/temurin-21/temurin-21-jdk_21.0.1.0.0+12_amd64.deb .. Im going to log the issue with the webui with jfrog.. but I've also tested that apt install works for JDKs & JREs for all version and installs the current/latest versions.. |
|
I am not sure it's working... it doesn't seem to error out on download, but it does say that there were timeouts... which is weird: |
|
@hdurand-artic Are you using a mirror repo/proxy or anything of that nature?, also would you mind sharing your repository configurations, and specifically what/how you are downloading the jdks ? .. the read errors appear to be related to debmirror.. |
|
@steelhead31 So, we're using debmirror to mirror every adoptium debian packages (amd64 / bullseyes-buster) - and serve them back ourselves internally. I don't think there's a proxy between our server and your server. (I'm personally not super familiar with debmirror) Everything worked before the original issue happened so I really don't think it's on our end. |
|
@hdurand-artic I think the cache on the debmirror may need updating, as we had to re-upload some packages following an initial error... is it possible for you to try with the debmirror disabled?, so you are downloading directly. |
It really isn't no, our machines don't have external access if they don't have to |
|
I've reached out to jfrog to check everything on their end, especially the fact that the web-ui doesn't display any packages, though it does list 13 available. |
|
@steelhead31 So, after digging into the debmirror documentation, I found out about "precleanup" after running it once I got those errors: but those errors don't appear again if I run it again with or without cleanup... I guess something is still wrong on your end? |
|
Yes, it appears there may be an issue on our hosted jfrog server, I've raised an issue with them to investigate, but it looks related to metadata/indexes on the artifactory server itself. The packages are visible ( and installable via other methods ) . But I think I've exhausted everything I can do.. I'll update this issue when I get an update |
|
@steelhead31 Alright, thank you! |
|
Adding more details on this. case1: if i add repo details on the CentOS/fedora on the server then there is no error and system will able to download the package. Cas2: if i add these in some kind of script(in my case i was doing on json for packer) and add the repo detail then first it will start throwing error around escape character After this fix packer json also valid and system was able to download the package. |
|
@pandeyv-del thanks for that information, thats useful to know... @hdurand-artic Apologies Im still waiting on an update from Jfrog for this issue, I've chased them again this morning. Can you have a look at the comment above and see if something similar is appropriate for your mirror scripting / environment? |
|
@steelhead31 Hello, do you have any news ? By the way, here's the debmirror output with debug/verbose enabled (I had to dug a bit recently to understand how debmirror works - after an unrelated issue - so I was able to enable that) |
|
So it seems to work now. I also just noticed that URLs had double "/" "https://packages.adoptium.net/artifactory/deb//pool/main/t/temurin-8/temurin-8-jdk_8.0.402.0.0+6_amd64.deb" , after solving this. It seems to be working consistently... so problem solved? Maybe? https://packages.adoptium.net/ui/packages/deb:%2F%2Ftemurin-11-jdk?name=temurin-11&type=packages still broken on JFrog though. |
|
Thanks for the update, Im still awaiting a response from jfrog... ,so Im guessing the caching issue with broken URLs is now working properly... as far as the packages, Im pretty much stuck until jfrog take a look.. as they manage the repository, and the only option left to me, is to rebuild the repository from scratch.. which I'd like to avoid unless its absolutely necessary. |
|
We are marking this issue as stale because it has not been updated for a while. This is just a way to keep the support issues queue manageable. |
|
I think these issues have now been resolved. Certainly the most recent release packages work correctly. |
Hello,
Same as #1002 (but it was closed)
Since yesterday packages.adoptium.net stopped serving some of the temurin's Debian package.
debmirror's log:
Our firewall doesn't seem to see any problem:
After digging into it, we discovered that the packages aren't visible on JFrog's web UI even though it seems to "know" that they exist
Alpine in comparison:
Debian 11 JRE in comparison:
The text was updated successfully, but these errors were encountered: