Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Acceptable from a Host - empty install template?
New on LowEndTalk? Please Register and read our Community Rules.

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.

Acceptable Host Service?
  1. Is providing an empty OS install template OK for a VPS provider?43 votes
    1. Absolutely, what do you expect for self/unmanaged?
        6.98%
    2. Its OK, not great, but not bad, you shouldn't be surprised.
      18.60%
    3. No, the OS install should work, but after that you are on your own
      72.09%
    4. Other
        2.33%

Comments

  • ATHKATHK Member

    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

    Thanked by 1MTUser2012
  • KuJoeKuJoe Member, Host Rep

    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.

  • @KuJoe said:
    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.

    Thanked by 1MTUser2012
  • b6688b6688 Member

    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

    
    -----BEGIN PGP PUBLIC KEY BLOCK-----
    Version: GnuPG v1.4.5 (GNU/Linux)
    
    mQINBFOn/0sBEADLDyZ+DQHkcTHDQSE0a0B2iYAEXwpPvs67cJ4tmhe/iMOyVMh9
    Yw/vBIF8scm6T/vPN5fopsKiW9UsAhGKg0epC6y5ed+NAUHTEa6pSOdo7CyFDwtn
    4HF61Esyb4gzPT6QiSr0zvdTtgYBRZjAEPFVu3Dio0oZ5UQZ7fzdZfeixMQ8VMTQ
    4y4x5vik9B+cqmGiq9AW71ixlDYVWasgR093fXiD9NLT4DTtK+KLGYNjJ8eMRqfZ
    Ws7g7C+9aEGHfsGZ/SxLOumx/GfiTloal0dnq8TC7XQ/JuNdB9qjoXzRF+faDUsj
    WuvNSQEqUXW1dzJjBvroEvgTdfCJfRpIgOrc256qvDMp1SxchMFltPlo5mbSMKu1
    x1p4UkAzx543meMlRXOgx2/hnBm6H6L0FsSyDS6P224yF+30eeODD4Ju4BCyQ0jO
    IpUxmUnApo/m0eRelI6TRl7jK6aGqSYUNhFBuFxSPKgKYBpFhVzRM63Jsvib82rY
    438q3sIOUdxZY6pvMOWRkdUVoz7WBExTdx5NtGX4kdW5QtcQHM+2kht6sBnJsvcB
    JYcYIwAUeA5vdRfwLKuZn6SgAUKdgeOtuf+cPR3/E68LZr784SlokiHLtQkfk98j
    NXm6fJjXwJvwiM2IiFyg8aUwEEDX5U+QOCA0wYrgUQ/h8iathvBJKSc9jQARAQAB
    tEJDZW50T1MtNyBLZXkgKENlbnRPUyA3IE9mZmljaWFsIFNpZ25pbmcgS2V5KSA8
    c2VjdXJpdHlAY2VudG9zLm9yZz6JAjUEEwECAB8FAlOn/0sCGwMGCwkIBwMCBBUC
    CAMDFgIBAh4BAheAAAoJECTGqKf0qA61TN0P/2730Th8cM+d1pEON7n0F1YiyxqG
    QzwpC2Fhr2UIsXpi/lWTXIG6AlRvrajjFhw9HktYjlF4oMG032SnI0XPdmrN29lL
    F+ee1ANdyvtkw4mMu2yQweVxU7Ku4oATPBvWRv+6pCQPTOMe5xPG0ZPjPGNiJ0xw
    4Ns+f5Q6Gqm927oHXpylUQEmuHKsCp3dK/kZaxJOXsmq6syY1gbrLj2Anq0iWWP4
    Tq8WMktUrTcc+zQ2pFR7ovEihK0Rvhmk6/N4+4JwAGijfhejxwNX8T6PCuYs5Jiv
    hQvsI9FdIIlTP4XhFZ4N9ndnEwA4AH7tNBsmB3HEbLqUSmu2Rr8hGiT2Plc4Y9AO
    aliW1kOMsZFYrX39krfRk2n2NXvieQJ/lw318gSGR67uckkz2ZekbCEpj/0mnHWD
    3R6V7m95R6UYqjcw++Q5CtZ2tzmxomZTf42IGIKBbSVmIS75WY+cBULUx3PcZYHD
    ZqAbB0Dl4MbdEH61kOI8EbN/TLl1i077r+9LXR1mOnlC3GLD03+XfY8eEBQf7137
    YSMiW5r/5xwQk7xEcKlbZdmUJp3ZDTQBXT06vavvp3jlkqqH9QOE8ViZZ6aKQLqv
    pL+4bs52jzuGwTMT7gOR5MzD+vT0fVS7Xm8MjOxvZgbHsAgzyFGlI1ggUQmU7lu3
    uPNL0eRx4S1G4Jn5
    =OGYX
    -----END PGP PUBLIC KEY BLOCK-----
    

    vi /etc/yum.repos.d/CentOS-Base.repo

    # CentOS-Base.repo
    #
    # The mirror system uses the connecting IP address of the client and the
    # update status of each mirror to pick mirrors that are updated to and
    # geographically close to the client.  You should use this for CentOS updates
    # unless you are manually picking other mirrors.
    #
    # If the mirrorlist= does not work for you, as a fall back you can try the 
    # remarked out baseurl= line instead.
    #
    #
    
    [base]
    name=CentOS-$releasever - Base
    mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
    #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    
    #released updates 
    [updates]
    name=CentOS-$releasever - Updates
    mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
    #baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    
    #additional packages that may be useful
    [extras]
    name=CentOS-$releasever - Extras
    mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
    #baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    
    #additional packages that extend functionality of existing packages
    [centosplus]
    name=CentOS-$releasever - Plus
    mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
    #baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
    gpgcheck=1
    enabled=0
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    

    vi /etc/yum.repos.d/CentOS-Vault.repo

    # CentOS Vault contains rpms from older releases in the CentOS-7 
    # tree.
    #c7.0.1406
    [C7.0.1406-base]
    name=CentOS-7.0.1406 - Base
    baseurl=http://vault.centos.org/7.0.1406/os/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.0.1406-updates]
    name=CentOS-7.0.1406 - Updates
    baseurl=http://vault.centos.org/7.0.1406/updates/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.0.1406-extras]
    name=CentOS-7.0.1406 - Extras
    baseurl=http://vault.centos.org/7.0.1406/extras/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.0.1406-centosplus]
    name=CentOS-7.0.1406 - CentOSPlus
    baseurl=http://vault.centos.org/7.0.1406/centosplus/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.0.1406-fasttrack]
    name=CentOS-7.0.1406 - CentOSPlus
    baseurl=http://vault.centos.org/7.0.1406/fasttrack/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    # C7.1.1503
    [C7.1.1503-base]
    name=CentOS-7.1.1503 - Base
    baseurl=http://vault.centos.org/7.1.1503/os/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.1.1503-updates]
    name=CentOS-7.1.1503 - Updates
    baseurl=http://vault.centos.org/7.1.1503/updates/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.1.1503-extras]
    name=CentOS-7.1.1503 - Extras
    baseurl=http://vault.centos.org/7.1.1503/extras/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.1.1503-centosplus]
    name=CentOS-7.1.1503 - CentOSPlus
    baseurl=http://vault.centos.org/7.1.1503/centosplus/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    
    [C7.1.1503-fasttrack]
    name=CentOS-7.1.1503 - CentOSPlus
    baseurl=http://vault.centos.org/7.1.1503/fasttrack/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    enabled=0
    

    vi /etc/yum.repos.d/CentOS-Debuginfo.repo

    # CentOS-Debug.repo
    #
    # The mirror system uses the connecting IP address of the client and the
    # update status of each mirror to pick mirrors that are updated to and
    # geographically close to the client.  You should use this for CentOS updates
    # unless you are manually picking other mirrors.
    #
    
    # All debug packages from all the various CentOS-7 releases
    # are merged into a single repo, split by BaseArch
    #
    # Note: packages in the debuginfo repo are currently not signed
    #
    
    [base-debuginfo]
    name=CentOS-7 - Debuginfo
    baseurl=http://debuginfo.centos.org/7/$basearch/
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-Debug-7
    enabled=0
    #
    

    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.

    Thanked by 1MTUser2012
  • 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.

    @KuJoe said:
    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.

  • 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/

    @b6688 said:
    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.

  • ATHKATHK Member

    @MTUser2012 said:
    Here is how I was shown how to fix it. It looks a little quicker than your way?

    You shouldn't have to fix it IMO they should've either inserted their own caching repositories or just left as is...

    Thanked by 1MTUser2012
  • 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.

    @budi1413 said:
    People make a mistake once in a while. Just notify them.

    Thanked by 1b6688
  • b6688b6688 Member

    @MTUser2012

    if you have more than 1 server running with CentOS7, you can use rsync. Thanks for sharing.

    Thanked by 1MTUser2012
  • MikeAMikeA Member, Patron Provider
    edited May 2016

    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.

    Thanked by 2ATHK MTUser2012
  • @MTUser2012 said:
    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.

    @budi1413 said:
    People make a mistake once in a while. Just notify them.

    Sorry i missed that. :)

    Thanked by 1MTUser2012
  • nepsneps Member

    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.

    Thanked by 2ATHK MTUser2012
  • yghostyghost Member, Host Rep

    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 ;)

    Thanked by 1MTUser2012
  • 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.

    Thanked by 1MTUser2012
  • 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.

    Thanked by 1MTUser2012
Sign In or Register to comment.