Marc, you're right, false alarm. Turned out to be a new (and misconfigured) firewall rule on our end blocking *some* https traffic.
On Thursday, August 4, 2016 at 2:56:27 PM UTC-5, Marc O'Brien wrote: > > Hi Patrick, > > I just tested this on a fresh CentOS7 instance on AWS and had no issues: > > [centos@ip-172-31-39-122 ~]$ sudo su - > [root@ip-172-31-39-122 ~]# curl -L > https://packagecloud.io/install/repositories/scalr/scalr-server-oss/script.rpm > > | sudo bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 147 0 147 0 0 21 0 --:--:-- 0:00:06 > --:--:-- 40 > 0 0 0 5826 0 0 299 0 --:--:-- 0:00:19 --:--:-- > 1286 > Detected operating system as centos/7. > Checking for curl... > Detected curl... > Downloading repository file: > https://packagecloud.io/install/repositories/scalr/scalr-server-oss/config_file.repo?os=centos&dist=7&source=script > done. > Installing pygpgme to verify GPG signatures... > Loaded plugins: fastestmirror > base > > | 3.6 kB 00:00:00 > extras > > | 3.4 kB 00:00:00 > scalr_scalr-server-oss-source/signature > > | 836 B 00:00:00 > Retrieving key from https://packagecloud.io/scalr/scalr-server-oss/gpgkey > Importing GPG key 0xD59097AB: > Userid : "packagecloud ops (production key) <[email protected] > <javascript:>>" > Fingerprint: 418a 7f2f b0e1 e6e7 eabf 6fe8 c2e7 3424 d590 97ab > From : https://packagecloud.io/scalr/scalr-server-oss/gpgkey > scalr_scalr-server-oss-source/signature > > | 951 B 00:00:00 !!! > updates > > | 3.4 kB 00:00:00 > (1/4): > extras/7/x86_64/primary_db > > | 149 kB 00:00:00 > (2/4): > updates/7/x86_64/primary_db > > | 6.4 MB 00:00:00 > (3/4): > base/7/x86_64/group_gz > > | 155 kB 00:00:00 > (4/4): > base/7/x86_64/primary_db > > | 5.3 MB 00:00:05 > scalr_scalr-server-oss-source/primary > > | 175 B 00:00:00 > Determining fastest mirrors > * base: centos.chicago.waneq.com > * extras: centos.eecs.wsu.edu > * updates: mirrors.kernel.org > Package pygpgme-0.3-9.el7.x86_64 already installed and latest version > Nothing to do > Installing yum-utils... > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > * base: centos.chicago.waneq.com > * extras: centos.eecs.wsu.edu > * updates: mirrors.kernel.org > Package yum-utils-1.1.31-34.el7.noarch already installed and latest version > Nothing to do > Generating yum cache for scalr_scalr-server-oss... > Importing GPG key 0xD59097AB: > Userid : "packagecloud ops (production key) <[email protected] > <javascript:>>" > Fingerprint: 418a 7f2f b0e1 e6e7 eabf 6fe8 c2e7 3424 d590 97ab > From : https://packagecloud.io/scalr/scalr-server-oss/gpgkey > > The repository is setup! You can now install packages. > [root@ip-172-31-39-122 ~]# sudo yum install -y scalr-server > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > * base: centos.chicago.waneq.com > * extras: centos.eecs.wsu.edu > * updates: mirrors.kernel.org > Resolving Dependencies > --> Running transaction check > ---> Package scalr-server.x86_64 > 0:5.11.22.oss~nightly.20160629003350.21.3fb5fbe.014cd7c-1.el7 will be > installed > --> Finished Dependency Resolution > > Dependencies Resolved > > > ======================================================================================================================================================= > Package Arch > Version > Repository Size > > ======================================================================================================================================================= > Installing: > scalr-server x86_64 > 5.11.22.oss~nightly.20160629003350.21.3fb5fbe.014cd7c-1.el7 > scalr_scalr-server-oss 288 M > > Transaction Summary > > ======================================================================================================================================================= > Install 1 Package > > Total download size: 288 M > Installed size: 965 M > Downloading packages: > scalr-server-5.11.22.oss~nightly.20160629003350.21.3fb5fbe.014cd7c-1.el7.x86_64.rpm > > | 288 MB 00:00:17 > Running transaction check > Running transaction test > Transaction test succeeded > Running transaction > Installing : > scalr-server-5.11.22.oss~nightly.20160629003350.21.3fb5fbe.014cd7c-1.el7.x86_64 > > 1/1 > Thank you for installing Scalr! > > The next step in the install process is to run: > > sudo scalr-server-wizard > Verifying : > scalr-server-5.11.22.oss~nightly.20160629003350.21.3fb5fbe.014cd7c-1.el7.x86_64 > > 1/1 > > Installed: > scalr-server.x86_64 > 0:5.11.22.oss~nightly.20160629003350.21.3fb5fbe.014cd7c-1.el7 > > Complete! > [root@ip-172-31-39-122 ~]# > > Can you test this again, perhaps on a fresh instance that is at least an > m3.medium with 4gb ram? > > Many thanks, > Wm. Marc O'Brien > Scalr Technical Support > > > On Thursday, August 4, 2016 at 1:29:40 PM UTC-6, Patrick Vinas wrote: >> >> Following the install guide on the wiki, looks like there's an issue with >> the RPM repo: >> >> curl -s >> https://packagecloud.io/install/repositories/scalr/scalr-server-oss/script.rpm.sh >> | >> sudo bash >> Detected operating system as centos/7. >> Checking for curl... >> Detected curl... >> Downloading repository file: >> https://packagecloud.io/install/repositories/scalr/scalr-server-oss/config_file.repo?os=centos&dist=7&source=script >> done. >> Installing pygpgme to verify GPG signatures... >> Loaded plugins: fastestmirror >> >> https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: >> >> [Errno 14] HTTPS Error 302 - Found >> Trying other mirror. >> >> >> One of the configured repositories failed >> (scalr_scalr-server-oss-source), >> 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. Disable the repository, 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 scalr_scalr-server-oss-source >> >> 4. 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=scalr_scalr-server-oss-source.skip_if_unavailable=true >> >> failure: repodata/repomd.xml from scalr_scalr-server-oss-source: [Errno >> 256] No more mirrors to try. >> >> https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: >> >> [Errno 14] HTTPS Error 302 - Found >> Installing yum-utils... >> Loaded plugins: fastestmirror >> base | 3.6 kB >> 00:00 >> extras | 3.4 kB >> 00:00 >> >> https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: >> >> [Errno 14] HTTPS Error 302 - Found >> Trying other mirror. >> >> >> One of the configured repositories failed >> (scalr_scalr-server-oss-source), >> 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. Disable the repository, 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 scalr_scalr-server-oss-source >> >> 4. 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=scalr_scalr-server-oss-source.skip_if_unavailable=true >> >> failure: repodata/repomd.xml from scalr_scalr-server-oss-source: [Errno >> 256] No more mirrors to try. >> >> https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: >> >> [Errno 14] HTTPS Error 302 - Found >> Generating yum cache for scalr_scalr-server-oss... >> >> https://packagecloud.io/scalr/scalr-server-oss/el/7/x86_64/repodata/repomd.xml: >> >> [Errno 14] HTTPS Error 302 - Found >> Trying other mirror. >> >> >> One of the configured repositories failed (scalr_scalr-server-oss), >> 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. Disable the repository, 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 scalr_scalr-server-oss >> >> 4. 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=scalr_scalr-server-oss.skip_if_unavailable=true >> >> failure: repodata/repomd.xml from scalr_scalr-server-oss: [Errno 256] No >> more mirrors to try. >> >> https://packagecloud.io/scalr/scalr-server-oss/el/7/x86_64/repodata/repomd.xml: >> >> [Errno 14] HTTPS Error 302 - Found >> >> The repository is setup! You can now install packages. >> >> >> Error 302 is a redirect, so I follow the redirect: >> >> <repomd xmlns="http://linux.duke.edu/metadata/repo";> >> <data type="other"> >> >> <location >> href="repodata/69a5c1ee346d2df3f5c11e6374e87ceaea7267c2-other.xml.gz"/> >> <checksum type="sha">69a5c1ee346d2df3f5c11e6374e87ceaea7267c2</checksum> >> <timestamp>1467164091</timestamp> >> >> <open-checksum >> type="sha">8bfc1933bb195d3aad9baf17813b2bd76cd8e4ae</open-checksum> >> </data> >> <data type="filelists"> >> >> <location >> href="repodata/9865cd3515a90e813f50ca2b538bb99687b21140-filelists.xml.gz"/> >> <checksum type="sha">9865cd3515a90e813f50ca2b538bb99687b21140</checksum> >> <timestamp>1467164091</timestamp> >> >> <open-checksum >> type="sha">3e01e5f12431462527bcd0e51880522b3f03114e</open-checksum> >> </data> >> <data type="primary"> >> >> <location >> href="repodata/576d29ab183dbcd0516e114ca782830da64a76f2-primary.xml.gz"/> >> <checksum type="sha">576d29ab183dbcd0516e114ca782830da64a76f2</checksum> >> <timestamp>1467164091</timestamp> >> >> <open-checksum >> type="sha">53999881933a47ef11b3908a8b6634b9c249f74e</open-checksum> >> </data> >> </repomd> >> >> >> Try to access linux.duke.edu, it redirects to sites.duke.edu/linux - and >> there aren't any scalr packages to be found. >> > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
