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] <
[email protected]> 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 + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
> http://www.tmvse.com / [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7580699&i=0>
>
>
>
> 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]
> <http:///user/SendEmail.jtp?type=node&node=7580699&i=1>]
> *Sent:* 01 January 2016 04:12
> *To:* [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7580699&i=2>
> *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]
> <http:///user/SendEmail.jtp?type=node&node=7580688&i=0>> 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]
> <http:///user/SendEmail.jtp?type=node&node=7580688&i=1>> 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
> <http://forums.jfrog.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
>
>
> ------------------------------
>
> View this message in context: Re: Artifactory won't proxy artifacts
> anymore
> <http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580688.html>
> Sent from the Artifactory - Users mailing list archive
> <http://forums.jfrog.org/Artifactory-Users-f2377369.html> 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] <http:///user/SendEmail.jtp?type=node&node=7580699&i=3>
> 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
> <http://forums.jfrog.org/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7580586&code=ZGhvZmZlcjZAZ21haWwuY29tfDc1ODA1ODZ8LTc0ODU5MzA3NQ==>
> .
> NAML
> <http://forums.jfrog.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580700.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
