Hi all:
We have an instance of 3.4.2 (subsequently updated to 3.5.1 during the
investigation of this problem) that has started experiencing some odd
problems, apparently independent of any administrative or configuration
changes:
No user, not even the "super user" can deploy any sort of artifact to any
snapshot repo. The error is always that the deploy is denied because it is
against the snapshot/release handling policy of the repo. Deploys to release
repositories work properly.
Anonymous users can browse the repos, but if they try to look at the
contents of any artifact, they are prompted for a username/password, even
though the anonymous user is granted read access to all repos.
The PyPI index no longer works (possibly because of #2 above). pip install
-i fails, but pip install -f seems to work okay.
Is there any way to validate that there is no corruption in the Derby
database and/or associated metadata? Looking at the logs, we see sequences
of errors like this:
Thanks in advance,
--
View this message in context:
http://forums.jfrog.org/PyPI-Repos-broken-tp7580204.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
