All good so far - the repo file is in my /etc/yum.repos.d directory
[root@ip-10-100-0-4 tftpboot]# yum clean all
Loaded plugins: priorities, update-motd, upgrade-helper
Cleaning repos: MongoDB amzn-main amzn-updates schmooze-commercial
Cleaning up everything
Still looking good… however:
[root@ip-10-100-0-4 tftpboot]# yum -y install php-5.3-zend-guard-loader sysadmin fail2ban incron ImageMagick
Loaded plugins: priorities, update-motd, upgrade-helper
MongoDB | 951 B 00:00
MongoDB/primary | 44 kB 00:00
MongoDB 274/274
amzn-main/latest | 2.1 kB 00:00
amzn-main/latest/group | 35 kB 00:00
amzn-main/latest/primary_db | 3.4 MB 00:00
amzn-updates/latest | 2.3 kB 00:00
amzn-updates/latest/group | 35 kB 00:00
amzn-updates/latest/updateinfo | 266 kB 00:00
amzn-updates/latest/primary_db | 174 kB 00:00
One of the configured repositories failed (Unknown),
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 <repoid>
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=<repoid>.skip_if_unavailable=true
Cannot find a valid baseurl for repo: schmooze-commercial/latest/x86_64