All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Acceptable from a Host - empty install template?
Maybe I'm lucky, but in all my experience buying VPSs and Dedis, I have never had an experience like this with a host. Install of Centos 7 goes fine. Here are my first few commands:
[root@host ~]# yum update
There are no enabled repos.
Run "yum repolist all" to see the repos you have.
You can enable repos with yum-config-manager --enable
[root@host ~]# yum repolist all
repolist: 0
[root@host ~]# cat /etc/yum.repos.d/*
placeholder for now
placeholder for now
placeholder for now
I asked the host about this, and got nothing helpful. Yes, I know you can get around this now with rsync after I was educated. But, I am interested in others' opinion - nothing to see here move along or substandard service. To me, it feels like taking "unmanaged" to a whole new level.
- Is providing an empty OS install template OK for a VPS provider?43 votes
- Absolutely, what do you expect for self/unmanaged?  6.98%
- Its OK, not great, but not bad, you shouldn't be surprised.18.60%
- No, the OS install should work, but after that you are on your own72.09%
- Other  2.33%
Comments
Looks like they left it out, a lot of bigger companies like OVH will cache the repositories so you can download them faster.
It's probably just a mistake which they should be made aware of (which you've done yay you!) And fix.. if they have no desire in fixing it then they have a serious attitude problem. And I would suggest you look at leaving them for a company that actually cares for their customers...
I've have had a similar issue where they would use their own DNS in resolv.conf and those IPS were old, they fixed it up pretty quickly thougb
Could be an honest mistake, we've pushed out broken templates before on accident but we've fixed them as soon as somebody pointed them out to us.
yes I just rolled out solusvm from virtualizor and all kinds of errors like this has happened and I am waiting to see if solusvm support could help as there mostly not being transferred fully from the master to the slave causing the issue.
I was having the same problem when installing the VPS with CentOS 7 with one of the recent bought VPS Host. Not to mention the company name here. Anyway, you need to manually edit the setting to include the repository information yourself. This is how I fixed it.
vi /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
vi /etc/yum.repos.d/CentOS-Base.repo
vi /etc/yum.repos.d/CentOS-Vault.repo
vi /etc/yum.repos.d/CentOS-Debuginfo.repo
yum install -y deltarpm
yum -y update
Then, you can use the yum command now. I guess the main reason was some host was more "Encourage" the user to use Debian instead of CentOS.
Thanks for the response. So a ticket about this that got no answer for a week - we will get back to you, and a follow up a week later, what are you trying to install, would be sub-standard. I gave up after two weeks and learned how to fix it myself.
Here is how I was shown how to fix it. It looks a little quicker than your way?
Go to another functional VPS with Centos 7 installed:
yum install rsync
rsync -avP /etc/yum.repos.d/CentOS-* [email protected]:/etc/yum.repos.d/
rsync -avP /etc/pki/rpm-gpg/RPM-GPG-KEY-Cent* [email protected]:/etc/pki/rpm-gpg/
You shouldn't have to fix it IMO they should've either inserted their own caching repositories or just left as is...
People make a mistake once in a while. Just notify them.
Yes, I agree. I've made more than my fair share of mistakes. Did you see in the post that I did notify them? They didn't fix it after two weeks. So I learned how to fix it myself.
@MTUser2012
if you have more than 1 server running with CentOS7, you can use rsync. Thanks for sharing.
Doesn't matter if it's a mistake or not, unmanaged servers should still work out of the box. A week with no reply? That's a joke as is.
Sorry i missed that.
A mistake like that, embarassing maybe, but not fixing it after two weeks? Sounds like a bad host; good thing you learned to fix it yourself, but I'd think about moving. Doesn't sound like a host I'd want to be with if something else goes wrong.
some times is good when the provider don't care and by this you learn a lot of things, and of course you learn that you should not renew your service with him
Can imagine it be headache if you dont supply your own OS templates surely its easier for the host as well to have a selection of templates to supply saving people misconfiguring etc.
I have learned the empty install templates issue is what I found out it is was the master not copying the full template to the slave and me wgetted it manually to the slave node fixed that template error which reminds me I need to follow up with solusvm support to see if they can tell what went wrong.
as I surely wouldn't leave a customer like this at my company but when you are dealing with everything else at once you kinda gotta admit you cannot be superman and do all of that at once replying to the customer, fixing the issues etc.