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

Not able to use the module. #172

Open
pedrocesarti opened this issue Aug 2, 2018 · 1 comment
Open

Not able to use the module. #172

pedrocesarti opened this issue Aug 2, 2018 · 1 comment

Comments

@pedrocesarti
Copy link

pedrocesarti commented Aug 2, 2018

Still someone supporting this module?

I'm trying to use right now, but apparently the yum repo has been moved: http://repo.varnish-cache.org/redhat/

Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install varnish' returned 1: One of the configured repositories failed (varnish),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=varnish ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable varnish
        or
            subscription-manager repos --disable=varnish

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=varnish.skip_if_unavailable=true

failure: repodata/d18cd2dd5b099eea6d64a2528060d177a589f846-primary.xml.gz from varnish: [Errno 256] No more mirrors to try.
http://repo.varnish-cache.org/redhat/varnish-3.0/el7/x86_64/repodata/d18cd2dd5b099eea6d64a2528060d177a589f846-primary.xml.gz: [Errno 14] HTTP Error 410 - Gone
Error: /Stage[main]/Varnish::Install/Package[varnish]/ensure: change from 'purged' to 'present' failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install varnish' returned 1: One of the configured repositories failed (varnish),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=varnish ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable varnish
        or
            subscription-manager repos --disable=varnish

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
  1 include varnish
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:
  1 forge 'https://forge.puppet.com'

            yum-config-manager --save --setopt=varnish.skip_if_unavailable=true

failure: repodata/d18cd2dd5b099eea6d64a2528060d177a589f846-primary.xml.gz from varnish: [Errno 256] No more mirrors to try.
http://repo.varnish-cache.org/redhat/varnish-3.0/el7/x86_64/repodata/d18cd2dd5b099eea6d64a2528060d177a589f846-primary.xml.gz: [Errno 14] HTTP Error 410 - Gone

Should I start looking in develop a new module? Anyone knows how to keep going?

@maxchk
Copy link
Owner

maxchk commented Sep 26, 2018

I'm not actively marinating this module but will merge a pull request if you submit one ;)

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

2 participants