RE: sentora install error
11-13-2018, 03:24 AM
(This post was last modified: 11-13-2018, 03:27 AM by laci.)
(11-12-2018, 09:24 AM)republicus Wrote: I've installed on Centos 7 without those problems.
If you have further issues I'll setup a 6.8 server to test.
It looks like its failing on epel and uzip. Try installing those first.
Code:# yum -y update
Install dependancies
Code:install wget unzip
Install Epel repo for CentOS 6.x 32-bit:
Code:# wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
# rpm -ivh epel-release-6-8.noarch.rpm
or; 64-bit:
Code:# wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
# rpm -ivh epel-release-6-8.noarch.rpm
Try running the Sentora install again.
Let me know if you have further problems. If so ill setup a test environment.
Hy!
I tried :
wget http://dl.fedoraproject.org/pub/epel/6/x...noarch.rpm
--2000-01-02 10:34:17-- http://dl.fedoraproject.org/pub/epel/6/x...noarch.rpm
Resolving dl.fedoraproject.org... 209.132.181.24, 209.132.181.25, 209.132.181.23
Connecting to dl.fedoraproject.org|209.132.181.24|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14540 (14K) [application/x-rpm]
Saving to: âepel-release-6-8.noarch.rpmâ
rpm -ivh epel-release-6-8.noarch.rpm
warning: epel-release-6-8.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
Preparing... ########################################### [100%]
1:epel-release ########################################### [100%]
end i followed : http://docs.sentora.org/?node=22
wget --no-check-certificate sentora.org/install
Checking that minimal requirements are ok
Detected : CentOs 6 x86_64
Ok.
DB server will be mySQL
-- Installing wget and dns utils required to manage inputs
Loaded plugins: fastestmirror
Setting up Update Process
Loading mirror speeds from cached hostfile
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Preparing to select timezone, please wait a few seconds...
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
-- Downloading and installing required tools...
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
-- Downloading Sentora, Please wait, this may take several minutes, the installer will continue after this is complete!
ERROR: cannot verify github.comâs certificate, issued by â/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 Extended Validation Server CAâ
Issued certificate not yet valid.
To connect to github.com insecurely, use â--no-check-certificateâ.
[sentora_core.zip]
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of sen sentora_core.zip.zip, and cannot find sentora_core.zip.ZIP, period.
mv: cannot stat `/etc/sentora/sentora-core-1.0.0': No such file or directory
rm: cannot remove `/etc/sentora/panel/LICENSE.md': No such file or directory
rm: cannot remove `/etc/sentora/panel/README.md': No such file or directory
rm: cannot remove `/etc/sentora/panel/.gitignore': No such file or directory
--2000-01-02 10:47:00-- https://raw.githubusercontent.com/sentor...er.ext.php
Resolving raw.githubusercontent.com... 151.101.84.133
Connecting to raw.githubusercontent.com|151.101.84.133|:443... connected.
ERROR: cannot verify raw.githubusercontent.comâs certificate, issued by â/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CAâ
Issued certificate not yet valid.
To connect to raw.githubusercontent.com insecurely, use â--no-check-certificateâ.
mv: cannot stat `/etc/sentora/panel/modules/ftp_management/code/controller.ext.php': No such file or directory
mv: cannot move `hotfix_controller.ext.php' to `/etc/sentora/panel/modules/ftp_management/code/controller.ext.php': No such file or directory
chown: cannot access `/etc/sentora/panel/modules/ftp_management/code/controller.ext.php': No such file or directory
chmod: cannot access `/etc/sentora/panel/modules/ftp_management/code/controller.ext.php': No such file or directory
chmod: cannot access `/etc/sentora/panel/bin/zppy': No such file or directory
chmod: cannot access `/etc/sentora/panel/bin/setso': No such file or directory
chmod: cannot access `/etc/sentora/panel/bin/setzadmin': No such file or directory
ERROR: cannot verify github.comâs certificate, issued by â/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 Extended Validation Server CAâ
Issued certificate not yet valid.
To connect to github.com insecurely, use â--no-check-certificateâ.
[sentora_preconfig.zip]
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of sentora_preconfig.zip or
sentora_preconfig.zip.zip, and cannot find sentora_preconfig.zip.ZIP, period.
cp: cannot stat `sentora-installers-1.0.3/preconf/*': No such file or directory
./install: line 541: cc: command not found
(11-12-2018, 01:48 PM)fearworks Wrote: Rather than setting up test environments etc., this is probably related to an installation script issue I pointed out a few months ago.
OP, you need to say which installation script you are using - there is the "official" one linked from the Sentora documentation, and there is also the current "master" one in the Github repository which has a few differences (there are probably more floating around in Github too...)
So, can you link to the EXACT installation script you used and we can take it from there.
Keith.
Hy
I do not think the "official" or github installation script issue ... with both is the same error ...