You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like they are hosting the repository as an S3 bucket on Amazon, not sure if a setup like that is supported.
My conf file:
[sensu]
name = Sensu $release ($arch)
release = 6
arch = x86_64
metadata = yum repomd # I also tried with only yum
baseurl = http://repos.sensuapp.org
The command used and the response just waits without timeout or stopping. The repository is responding with my clients connecting to it directly and not using mrepo and the http url is responding in my browser.
[root@ip-10-0-1-201 mrepo.conf.d]# mrepo -g -u -vvv sensu
Verbosity set to level 3
Using configfile /etc/mrepo.conf
Reading config file /etc/mrepo.conf
Setting option confdir in section [main] to: /etc/mrepo.conf.d
Setting option srcdir in section [main] to: /var/mrepo
Setting option wwwdir in section [main] to: /var/www/mrepo
Setting option mailto in section [main] to: root@localhost
Setting option smtp-server in section [main] to: localhost
Setting option arch in section [main] to: i386
Reading config file /etc/mrepo.conf.d/centos6.conf
Setting option arch in section [centos6] to: x86_64
Reading config file /etc/mrepo.conf.d/sensu.conf
Setting option arch in section [sensu] to: x86_64
sensu-x86_64: Updating Sensu 6 (x86_64)
sensu-x86_64: Mirror packages from http://repos.sensuapp.org to /var/mrepo/sensu-x86_64/baseurl
Getting files information (100%) [Waiting for response...]
The text was updated successfully, but these errors were encountered:
It looks like they are hosting the repository as an S3 bucket on Amazon, not sure if a setup like that is supported.
My conf file:
The command used and the response just waits without timeout or stopping. The repository is responding with my clients connecting to it directly and not using mrepo and the http url is responding in my browser.
The text was updated successfully, but these errors were encountered: