repman-io/repman

Service unavailable

marcospassos opened this issue · 16 comments

We are currently experiencing issues fetching package metadata. Is the service experiencing an outage?

Having the same issue. Also cannot log in.

Yes, there seems to be an issue with http2 protocol on the servers

curl error 92 while downloading https://xxxxxxxx.repo.repman.io/packages.json: HTTP/2 stream 65 was not closed cleanly: INTERNAL_ERROR (err 2)

Yes, Cannot login or publish the app

The service is back to normal now.

@adaluppa composer install still gives us "package not found" errors for our repman package. For example: when running composer install -vvv we see [404] https://digipolis.repo.repman.io/p2/district09/kuanza.json among the messages.

@adaluppa composer install still gives us "package not found" errors for our repman package. For example: when running composer install -vvv we see [404] https://digipolis.repo.repman.io/p2/district09/kuanza.json among the messages.

This may be related to another issue I have also experienced (randomly) with pacakges on repman.
You have to update each package.

If you have plenty (like i do) it is a tedious task.

this bash script will do teh job. just setup your org name and key to use. I did not write this, it was found on a ticket in this repo related to the fact that randomly pckages can go 404.

#!/bin/env bash
# Requires HTTPie and JQ

ORG_NAME='xxxxxx'
API_KEY='xxxxxx'
SLEEP_S=0.5

# End of variables that need to change

package_url="[https://app.repman.io/api/organization/${ORG_NAME}/package](https://app.repman.io/api/organization/$%7BORG_NAME%7D/package)"
echo "http -j '${package_url}' 'X-Api-Token:${API_KEY}'"
result=`http -j "${package_url}" "X-Api-Token:${API_KEY}"`

echo $result

while [[ true ]]
do
    for uuid in `echo "${result}" | jq -r '.data[].id'`
    do
        sync_url="${package_url}/${uuid}"
        echo "Syncing package ${sync_url}"
        http -j PUT "${sync_url}" "X-Api-Token:${API_KEY}"
        sleep "${SLEEP_S}"
    done

    next_link=`echo "${result}" | jq -re '.links.next'`
    if [ $? -ne 0 ]; then
        break
    fi

    echo "---- Fetching ${next_link}"
    result=`http -j "${next_link}" "X-Api-Token:${API_KEY}"`
done

echo "done"
exit 0

https://gist.github.com/ProxiBlue/f00ecb42c1eade71c8c0f991da6d13f0

Small worker issue, task queue is staring to catch up. Sorry for problems.

Just as a note, a day later, I still found all my packages come back 404.

 Problem 1
    - Root composer.json requires elgentos/magento2-link-guest-orders-to-customer ^1.0, found elgentos/magento2-link-guest-orders-to-customer[1.0.0] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.
    -
40 more like this.

using the script I supplied above fixed it all up.

Small worker issue, task queue is staring to catch up. Sorry for problems.

You should close the issue when it no longer occurs, as we are still receiving the 404 error.

@akondas this is still happening :(

If you are getting 404's, use the script I supplied above, it fixes the 404 issues, and you can go on.

@ProxiBlue i ran the PHP script mentioned here #673 (comment) it fixed a couple of packages but all the rest are still 404

@ProxiBlue i ran the PHP script mentioned here #673 (comment) it fixed a couple of packages but all the rest are still 404

Odd, it usually works for all packages for me. you sure they are all on the same ORG_Name?

Ahh, that is not the same one I supplied above. Use the one above, it workd 100% for me. multiple times. repman has had this 404 issue a few times, unrelated to this tickets main issue

@ProxiBlue Yes, they're all on the same ORG_Name
I looked at the code and both scripts do the same thing, I couldn't run yours because I don't have http installed, i get a command not found

Try the support team via buddy.works - as repman is made by buddy.

@ProxiBlue I installed http and ran your script - same results