repomd.xml: [Errno 14] HTTP Error 404 - Not Found

[yokochi]

I executed the following below command, but I get a 404 error.

curl -L https://toolbelt.treasuredata.com/sh/install-redhat-td-agent2.sh | sh

404 error

http://packages.treasuredata.com/2/redhat/2018.03/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Version Elastic Beanstalk
AMI: 2018.03.0 ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux]

detail

# curl -L https://toolbelt.treasuredata.com/sh/install-redhat-td-agent2.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   849  100   849    0     0   4850      0 --:--:-- --:--:-- --:--:--  4879
==============================
 td-agent Installation Script 
==============================
This script requires superuser access to install rpm packages.
You will be prompted for your password by sudo.
読み込んだプラグイン:priorities, update-motd, upgrade-helper
http://packages.treasuredata.com/2/redhat/2018.03/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
他のミラーを試します。
To address this issue please refer to the below knowledge base article 

https://access.redhat.com/articles/1320623

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

 One of the configured repositories failed (TreasureData),
 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 treasuredata

     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=treasuredata.skip_if_unavailable=true

failure: repodata/repomd.xml from treasuredata: [Errno 256] No more mirrors to try.
http://packages.treasuredata.com/2/redhat/2018.03/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
読み込んだプラグイン:priorities, update-motd, upgrade-helper
amzn-main                                                                                                                                                                                                                                                                                                | 2.1 kB  00:00:00     
amzn-updates                                                                                                                                                                                                                                                                                             | 2.5 kB  00:00:00     
http://packages.treasuredata.com/2/redhat/2018.03/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
他のミラーを試します。
To address this issue please refer to the below knowledge base article 

https://access.redhat.com/articles/1320623

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

 One of the configured repositories failed (TreasureData),
 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 treasuredata

     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=treasuredata.skip_if_unavailable=true

failure: repodata/repomd.xml from treasuredata: [Errno 256] No more mirrors to try.
http://packages.treasuredata.com/2/redhat/2018.03/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Installation completed. Happy Logging!

[toru-takahashi]

Thank you for the report. Unfortunately, we don't maintain this repo for a long time. You need to update the script by yourselves. PR is welcome.

Looks you installed td-agent to Amazon Linux 2018.03 But, td-agent2 doesn't support Amazon Linux 2018.03

So, you need to install td-agent3 instead. https://docs.fluentd.org/v1.0/articles/install-by-rpm

[yokochi]

Thanks for reply. I'll try install td-agent3.