Skip to main content

[Case 90661] Restarting the cPanel install with the --force option

keithl
I'm trying to build a new cPanel install using an old CentOS 5.4 + cPanel installer, and it seems I'm falling foul of the recent change in the installer discussed here : [url=http://blog.cpanel.net/blockers-for-new-installations-of-cpanel-whm/]Blockers for New Installations of cPanel & WHM | cPanel Blog where it's failing due to the CentOS version not being 6.x. It simply tells me that "You can force the install on a CentOS version 5 using the --force option.", but doesn't tell me where or how I go about doing that. I'm sure it's simple, but I've always used the cPanel provided installers so haven't had to manually initiate the install, and have no idea where or how I need to go about it (and searching online gives me loads of preparation info for if I was doing it manually, but a lack of "to start the install run x" instructions). If someone could point out what I need to run I'd appreciate it. Note, yes I know I'd be better off with a CentOS 6.4 install. I'm building the old box to be the same OS version as our existing install so I can test a few things I can't risk doing on a production instance. Once that's done I'll be binning the installation and re-creating it with 6.4 install.

Comments

2 comments

Date Votes
  • cPanelMichael
    Hello :) The only difference when forcing the installation of cPanel is that "sh latest" becomes: sh latest --force
    There is an internal case open (#90661) to update the blog post to reflect this. Thank you.
    0
  • keithl
    Aha, perfect, just what I needed! Using the normal installer I've never needed to run or know about "sh latest" before now, so that's what I was missing. Also that it's found in /home/cpinst! (not obvious when that isn't where you're left after it's failed the install) Once I'd located the file I got it to run, and it's currently going through the install. Updating the blog (and ideally the error it spits out after failing the install) would be useful. Just one or two lines telling people to go to /home/cpinst and then run sh latest --force and there'd be none of these issues. Thanks a lot for your help.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post