Artifactory won't proxy artifacts anymore

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Artifactory won't proxy artifacts anymore

dhoffer
I upgraded to 4.1.3 and I have been having problems proxing new artifacts.

In my Maven builds I get errors like this for new artifacts that have not been proxied before.

[WARNING] Checksum validation failed, expected <!DOCTYPE but is 7bf6c3d50f09078c2a55a79d161e2c833c164259 for http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
[WARNING] Could not validate integrity of download from http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar: Checksum validation failed, expected <!DOCTYPE but is 7bf6c3d50f09078c2a55a79d161e2c833c164259
[WARNING] Checksum validation failed, expected <!DOCTYPE but is 7bf6c3d50f09078c2a55a79d161e2c833c164259 for http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
Downloaded: http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar (473 B at 0.0 KB/sec)

Note it says its a warning but what artifactory really did is create garbage files for all the poms and jar artifacts.

Then when I go back to Artifactory and browse for the artifact and click on it...it says:

{
  "errors" : [ {
    "status" : 404,
    "message" : "Unable to retrieve http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom/: 404: Not Found (remote response: 404: Not Found)"
  } ]
}

But if I go to the repo1 URL, http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom, it is just fine as expected.

What is going on here, why can't Artifactory proxy & cache as expected?  In early versions of Artifactory I never had any issues now I can't get simple things to work.


Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

HughG_TMVSE
Hi dhoffer,

just a guess, but maybe Artifactory has tried to download the checksum files (e.g., ".pom.sha1") from repo1, received an XHTML error page, and incorrectly stored that as the checksum value?

I'm not running 4.x so I can't check.

Hope that helps,

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / mailto:[hidden email]

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.


-----Original Message-----
From: dhoffer [mailto:[hidden email]]
Sent: 12 November 2015 07:17
To: [hidden email]
Subject: [Artifactory-users] Artifactory won't proxy artifacts anymore

I upgraded to 4.1.3 and I have been having problems proxing new artifacts.

In my Maven builds I get errors like this for new artifacts that have not been proxied before.

[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7bf6c3d50f09078c2a55a79d161e2c833c164259 for http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
[WARNING] Could not validate integrity of download from
http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar:
Checksum validation failed, expected <!DOCTYPE but is
7bf6c3d50f09078c2a55a79d161e2c833c164259
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7bf6c3d50f09078c2a55a79d161e2c833c164259 for http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
Downloaded:
http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
(473 B at 0.0 KB/sec)

Note it says its a warning but what artifactory really did is create garbage files for all the poms and jar artifacts.

Then when I go back to Artifactory and browse for the artifact and click on it...it says:

{
  "errors" : [ {
    "status" : 404,
    "message" : "Unable to retrieve
http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom/:
404: Not Found (remote response: 404: Not Found)"
  } ]
}

But if I go to the repo1 URL,
http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom,
it is just fine as expected.

What is going on here, why can't Artifactory proxy & cache as expected?  In early versions of Artifactory I never had any issues now I can't get simple things to work.






--
View this message in context: http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

dhoffer
I continue to have nothing but trouble with the newer Artifactory versions.  

I just need to get access to some Atlassian components so added their remote repo to my Artifactory. 


And it tests out find in Artifactory.  But when I try to download any artifact from the remote repo Artifactory downloads things but its all garbage.  the content of all the poms and jars is the following:


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head><title>Index of libs-releases/com/atlassian/jira/jira-rest-java-client/2.0.0-m2/jira-rest-java-client-2.0.0-m2.jar</title>
</head>
<body>
<h1>Index of libs-releases/com/atlassian/jira/jira-rest-java-client/2.0.0-m2/jira-rest-java-client-2.0.0-m2.jar</h1>
<pre>Name  Last modified      Size</pre><hr/>
<pre><a href="../">../</a>
</pre>
<hr/><address style="font-size:small;">Artifactory/4.1.3 Server at internal.company.com Port 80</address></body></html>


This is completely baffling, it used to be so easy to use Artifactory but now nothing works.

Does anyone have some ideas on how to fix?

-Dave


On Fri, Nov 13, 2015 at 2:26 AM, HughG_TMVSE [via Artifactory] <[hidden email]> wrote:
Hi dhoffer,

just a guess, but maybe Artifactory has tried to download the checksum files (e.g., ".pom.sha1") from repo1, received an XHTML error page, and incorrectly stored that as the checksum value?

I'm not running 4.x so I can't check.

Hope that helps,

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel <a href="tel:%2B%2044%20%280%29131%20472%204792" value="+441314724792" target="_blank">+ 44 (0)131 472 4792 / Fax <a href="tel:%2B%2044%20%280%29%20131%20472%204799" value="+441314724799" target="_blank">+ 44 (0) 131 472 4799
http://www.tmvse.com / mailto:[hidden email]

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.


-----Original Message-----
From: dhoffer [mailto:[hidden email]]
Sent: 12 November 2015 07:17
To: [hidden email]
Subject: [Artifactory-users] Artifactory won't proxy artifacts anymore

I upgraded to 4.1.3 and I have been having problems proxing new artifacts.

In my Maven builds I get errors like this for new artifacts that have not been proxied before.

[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7bf6c3d50f09078c2a55a79d161e2c833c164259 for http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
[WARNING] Could not validate integrity of download from
http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar:
Checksum validation failed, expected <!DOCTYPE but is
7bf6c3d50f09078c2a55a79d161e2c833c164259
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7bf6c3d50f09078c2a55a79d161e2c833c164259 for http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
Downloaded:
http://internal.qsd.com/artifactory/libs-releases/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.jar
(473 B at 0.0 KB/sec)

Note it says its a warning but what artifactory really did is create garbage files for all the poms and jar artifacts.

Then when I go back to Artifactory and browse for the artifact and click on it...it says:

{
  "errors" : [ {
    "status" : 404,
    "message" : "Unable to retrieve
http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom/:
404: Not Found (remote response: 404: Not Found)"
  } ]
}

But if I go to the repo1 URL,
http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom,
it is just fine as expected.

What is going on here, why can't Artifactory proxy & cache as expected?  In early versions of Artifactory I never had any issues now I can't get simple things to work.






--
View this message in context: http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users



If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580601.html
To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

Alex
Hi dhoffer

I think you have stumbled upon this bug that was fixed in version 4.3.1: https://www.jfrog.com/jira/browse/RTFACT-6773

It seems that you are trying to download an artifact from virtual repository and it ends with “/” in the end of the URL. I think that Maven added the “/” to the end of the URL. Artifactory in previous versions returned 200 instead of 404 for non existing folders if you are using a virtual repository. This result created the page you have received. In your first email it seems like this issue since in the error: "Unable to retrieve http://repo1.maven.org/maven2/com/google/api-ads/dfp-axis/2.7.0/dfp-axis-2.7.0.pom/: 
You can see that there is “/” in the end.

Try to upgrade to newest version and I think it will solve your issue.
 
Thanks,
Alex
Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

dave_p
In reply to this post by dhoffer
You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)
Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

dhoffer
Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

Very strange behavior...have no confidence in the tool anymore.




On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <[hidden email]> wrote:
You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html
To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

dhoffer
In reply to this post by dave_p
The bug is back already.  I added a couple more Atlassian dependencies and Artifactory is back to producing garbage again.  I simply can't get Artifactory to work any more.

On Thu, Dec 31, 2015 at 6:31 PM, David Hoffer <[hidden email]> wrote:
Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

Very strange behavior...have no confidence in the tool anymore.




On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <[hidden email]> wrote:
You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html
To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML


Reply | Threaded
Open this post in threaded view
|

Re: [#35145] Artifactory won't proxy artifacts anymore

JFrog Support
In reply to this post by dhoffer
Hi David,

Thank you for raising this issue in our forum. We would like to further investigate this issue with you to bring it to a resolution over an online session with our relevant experts.

Would you be able to join us so we can further examine this behaviour with you? Let us know if so and please provide us with your availability for next week and timezone. 

Sincerely,
Mor
JFrog Support 


On Fri, 1 Jan at 3:34 AM , Dhoffer6 <[hidden email]> wrote:
Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

Very strange behavior...have no confidence in the tool anymore.




On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <[hidden email]> wrote:
You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html
To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML



View this message in context: Re: Artifactory won't proxy artifacts anymore
Sent from the Artifactory - Users mailing list archive at Nabble.com.
35145

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: [#35145] Artifactory won't proxy artifacts anymore

darnone
I think you have the wrong David.

David

On Jan 1, 2016, at 2:39 AM, JFrog Support <[hidden email]> wrote:

Hi David,

Thank you for raising this issue in our forum. We would like to further investigate this issue with you to bring it to a resolution over an online session with our relevant experts.

Would you be able to join us so we can further examine this behaviour with you? Let us know if so and please provide us with your availability for next week and timezone. 

Sincerely,
Mor
JFrog Support 


On Fri, 1 Jan at 3:34 AM , Dhoffer6 <[hidden email]> wrote:
Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

Very strange behavior...have no confidence in the tool anymore.




On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <<a href="x-msg://4/user/SendEmail.jtp?type=node&amp;node=7580687&amp;i=0" target="_top" rel="nofollow" class="">[hidden email]> wrote:
You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html
To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML



View this message in context: Re: Artifactory won't proxy artifacts anymore
Sent from the Artifactory - Users mailing list archive at Nabble.com.
35145
------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

HughG_TMVSE
In reply to this post by dhoffer

Hi Dave,

 

this is a fairly wild guess, but I wonder if you need to “Zap Caches” for the files which were previously (with the “200 when it should be 404” bug) returned as “garbage” (XML error documents) and now (with the bug fix) ought to be correct.  I’m supposing that Artifactory thinks it has a cached result for those files, so doesn’t bother going to the remote site, which would now return a 404, forcing you to fix whatever script/tool is requesting a filename which ends in a “/”.  I just have this nagging feeling that I encountered something similar with Artifactory 3.x in the past, but I can’t remember what.  I believe you can Zap Caches on just a single file or folder, as well as on the whole repo, which might help you test whether that will fix things.

 

Apologies if this is irrelevant – I don’t understand all the details of your problem.

 

Regards,

 

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / [hidden email]

 

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.

 

From: dhoffer [mailto:[hidden email]]
Sent: 01 January 2016 04:12
To: [hidden email]
Subject: Re: [Artifactory-users] Artifactory won't proxy artifacts anymore

 

The bug is back already.  I added a couple more Atlassian dependencies and Artifactory is back to producing garbage again.  I simply can't get Artifactory to work any more.

 

On Thu, Dec 31, 2015 at 6:31 PM, David Hoffer <[hidden email]> wrote:

Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

 

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

 

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

 

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

 

Very strange behavior...have no confidence in the tool anymore.

 

 

 

 

On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <[hidden email]> wrote:

You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html

To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

 

 

 


View this message in context: Re: Artifactory won't proxy artifacts anymore
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

dhoffer
Actually you are quite right but it required more than that.  I did work with Aritifactory support on this and yes due to that previous bug I had to both zap caches on all my remote repos plus delete the content. (Its possible this was a bit overkill but since we had no way to know what caches had bad content its the fastest fix.)

But that still was not enough.  With that fix I was able to proxy properly using the remote repo but my virtual one still had the same problem. What I finally did to fix this was the above steps plus I had to manually remove all the repos from my virtual repo and put them back.  No idea why this last step was needed but it was critical to the fix.  So far with these changes I have not had any problems but I have not added any new remote repos yet either...but I'm fairly confident all my issues were do to the prior Artifactory bug that corrupted so much of my remote/virtual caches.

-Dave 

On Wed, Jan 6, 2016 at 6:27 AM, HughG_TMVSE [via Artifactory] <[hidden email]> wrote:

Hi Dave,

 

this is a fairly wild guess, but I wonder if you need to “Zap Caches” for the files which were previously (with the “200 when it should be 404” bug) returned as “garbage” (XML error documents) and now (with the bug fix) ought to be correct.  I’m supposing that Artifactory thinks it has a cached result for those files, so doesn’t bother going to the remote site, which would now return a 404, forcing you to fix whatever script/tool is requesting a filename which ends in a “/”.  I just have this nagging feeling that I encountered something similar with Artifactory 3.x in the past, but I can’t remember what.  I believe you can Zap Caches on just a single file or folder, as well as on the whole repo, which might help you test whether that will fix things.

 

Apologies if this is irrelevant – I don’t understand all the details of your problem.

 

Regards,

 

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel <a href="tel:%2B%2044%20%280%29131%20472%204792" value="+441314724792" target="_blank">+ 44 (0)131 472 4792 / Fax <a href="tel:%2B%2044%20%280%29%20131%20472%204799" value="+441314724799" target="_blank">+ 44 (0) 131 472 4799
http://www.tmvse.com / [hidden email]

 

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.

 

From: dhoffer [mailto:[hidden email]]
Sent: 01 January 2016 04:12
To: [hidden email]
Subject: Re: [Artifactory-users] Artifactory won't proxy artifacts anymore

 

The bug is back already.  I added a couple more Atlassian dependencies and Artifactory is back to producing garbage again.  I simply can't get Artifactory to work any more.

 

On Thu, Dec 31, 2015 at 6:31 PM, David Hoffer <[hidden email]> wrote:

Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

 

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

 

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

 

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

 

Very strange behavior...have no confidence in the tool anymore.

 

 

 

 

On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <[hidden email]> wrote:

You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html

To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

 

 

 


View this message in context: Re: Artifactory won't proxy artifacts anymore
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users



If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580699.html
To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: Artifactory won't proxy artifacts anymore

HughG_TMVSE

Hi again Dave,

 

well, glad to hear you fixed your problem, and to have the solution recorded here for others.  I’m hoping we’ll upgrade to a later 4.x and skip that problem, though we may hit others …

 

Regards,

 

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / [hidden email]

 

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.

 

From: dhoffer [mailto:[hidden email]]
Sent: 06 January 2016 14:03
To: [hidden email]
Subject: Re: [Artifactory-users] Artifactory won't proxy artifacts anymore

 

Actually you are quite right but it required more than that.  I did work with Aritifactory support on this and yes due to that previous bug I had to both zap caches on all my remote repos plus delete the content. (Its possible this was a bit overkill but since we had no way to know what caches had bad content its the fastest fix.)

 

But that still was not enough.  With that fix I was able to proxy properly using the remote repo but my virtual one still had the same problem. What I finally did to fix this was the above steps plus I had to manually remove all the repos from my virtual repo and put them back.  No idea why this last step was needed but it was critical to the fix.  So far with these changes I have not had any problems but I have not added any new remote repos yet either...but I'm fairly confident all my issues were do to the prior Artifactory bug that corrupted so much of my remote/virtual caches.

 

-Dave 

 

On Wed, Jan 6, 2016 at 6:27 AM, HughG_TMVSE [via Artifactory] <[hidden email]> wrote:

Hi Dave,

 

this is a fairly wild guess, but I wonder if you need to “Zap Caches” for the files which were previously (with the “200 when it should be 404” bug) returned as “garbage” (XML error documents) and now (with the bug fix) ought to be correct.  I’m supposing that Artifactory thinks it has a cached result for those files, so doesn’t bother going to the remote site, which would now return a 404, forcing you to fix whatever script/tool is requesting a filename which ends in a “/”.  I just have this nagging feeling that I encountered something similar with Artifactory 3.x in the past, but I can’t remember what.  I believe you can Zap Caches on just a single file or folder, as well as on the whole repo, which might help you test whether that will fix things.

 

Apologies if this is irrelevant – I don’t understand all the details of your problem.

 

Regards,

 

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel <a href="<a href="tel:%2B%2044%20%280%29131%20472%204792">tel:%2B%2044%20%280%29131%20472%204792" value="+441314724792" target="_blank">+ 44 (0)131 472 4792 / Fax <a href="<a href="tel:%2B%2044%20%280%29%20131%20472%204799">tel:%2B%2044%20%280%29%20131%20472%204799" value="+441314724799" target="_blank">+ 44 (0) 131 472 4799
http://www.tmvse.com / [hidden email]

 

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.

 

From: dhoffer [mailto:[hidden email]]
Sent: 01 January 2016 04:12
To: [hidden email]
Subject: Re: [Artifactory-users] Artifactory won't proxy artifacts anymore

 

The bug is back already.  I added a couple more Atlassian dependencies and Artifactory is back to producing garbage again.  I simply can't get Artifactory to work any more.

 

On Thu, Dec 31, 2015 at 6:31 PM, David Hoffer <[hidden email]> wrote:

Okay this is really weird.  I upgraded to 4.3.3 per the suggestion that I might have hit on a bug that was fixed but 4.3.3 has the same problem, it still creates garbage when it downloads from a perfectly good repo.

 

Now a little about my upgrade, I have a standalone service so I followed the upgrade instructions where I replace the bin, tomcat & artifactory.war in the old install with the new files.  So after this starts up and I see that it does not fix the bug I notice that Artifactory now has a lot of old remote repos (Admin | Repositories | Remote) that I had deleted a long time ago.  (They did not show in the UI with the prior version.)

 

The reason I had previously deleted some old ones was because of this same bug, I was told that newer versions of Artifactory don't support some public maven repositories that it used to support (if I recall they were maven repos hosted in svn or something like that).  Well in any case the old repos are back now in the UI in this new version.  So I suspect that although I had deleted them previously Artifactory was still 'using' them and that's why the bug persisted.

 

So I now have re-deleted the old repos and now I'm not getting garbage anymore from the Atlassian repo.  But just like last time I suspect the bug will come back because apparently Artifactory isn't really deleting anything.  So I have no confidence the bug won't come back when I add another repo (or whatever is triggering this bug).

 

Very strange behavior...have no confidence in the tool anymore.

 

 

 

 

On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <[hidden email]> wrote:

You might also want to take a look at this thread:

http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html

And double check all your remote repository URLs. (Assuming the "libs-releases" repository is a virtual repository that includes one or more cached repositories.)


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html

To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

 

 

 


View this message in context: Re: Artifactory won't proxy artifacts anymore
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580699.html

To unsubscribe from Artifactory won't proxy artifacts anymore, click here.
NAML

 

 


View this message in context: Re: Artifactory won't proxy artifacts anymore
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users