Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service unavailable #672

Closed
marcospassos opened this issue Feb 29, 2024 · 16 comments
Closed

Service unavailable #672

marcospassos opened this issue Feb 29, 2024 · 16 comments

Comments

@marcospassos
Copy link

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

@jacerider
Copy link

Having the same issue. Also cannot log in.

@ProxiBlue
Copy link

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)

@naseefpv
Copy link

naseefpv commented Mar 1, 2024

Yes, Cannot login or publish the app

@adaluppa
Copy link

adaluppa commented Mar 1, 2024

The service is back to normal now.

@Jelle-S
Copy link

Jelle-S commented Mar 1, 2024

@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.

@ProxiBlue
Copy link

ProxiBlue commented Mar 1, 2024

@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

@akondas
Copy link
Member

akondas commented Mar 1, 2024

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

@akondas akondas closed this as completed Mar 1, 2024
@ProxiBlue
Copy link

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.

@astersnake
Copy link

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.

@treestonemedia
Copy link

@akondas this is still happening :(

@ProxiBlue
Copy link

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

@treestonemedia
Copy link

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

@ProxiBlue
Copy link

ProxiBlue commented Mar 12, 2024

@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

@treestonemedia
Copy link

@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

@ProxiBlue
Copy link

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

@treestonemedia
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants