Systemctl command faliling in CentOS 7


#1

Hi I am following step by step installation of Mapd in CentOS. I am trying to install it in a CentOS instance in Amazon AWS. After setting the environment variables, when I run the sudo ./install_mapd_systemd.sh. I get “systemctl command not found”. Below is more detailed output. Can you suggest where am I getting it wrong.

MAPD_PATH: /home/ec2-user/mapd_core
MAPD_STORAGE: /var/lib/mapd
MAPD_USER: mapd
MAPD_GROUP: mapdstrong text
MAPD_LIBJVM_DIR: /usr/lib/jvm/jre/lib/amd64/server
cp: cannot create regular file ‘/lib/systemd/system/’: No such file or directory
cp: cannot create regular file ‘/lib/systemd/system/’: No such file or directory
cp: cannot create regular file ‘/lib/systemd/system/’: No such file or directory
cp: cannot create regular file ‘/lib/systemd/system/’: No such file or directory
sudo: systemctl: command not found


#2

Hi

please show output of cat /etc/redhat-release

regards


#3

I am actually running on an Amazon quick start machine image “Amazon Linux AMI 2017.03.1 (HVM), SSD Volume Type - ami-643b1972”. It does not come with /etc/redhat-release file (more info https://forums.aws.amazon.com/thread.jspa?threadID=51647). There is a /etc/system-release file and it shows only “Amazon Linux AMI release 2017.03”. Below is some of the directory structure of the system. I can provide more info in case you need to know the content of any other folder.

vi /etc/yum.repos.d/
amzn-main.repo amzn-preview.repo cuda-8-0-local-ga2.repo epel-testing.repo
amzn-nosrc.repo amzn-updates.repo epel.repo

cat /etc/yum.conf
[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
distroverpkg=system-release
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=3
deltarpm=0

by default the yum configuration will point to the latest release

of Amazon Linux AMI. If you prefer not to automatically move to

new releases, comment out this line.

releasever=latest

This is the default, if you make this bigger yum won’t see if the metadata

is newer on the remote and so you’ll “gain” the bandwidth of not having to

download the new metadata and “pay” for it by yum not having correct

information.

It is esp. important, to have correct metadata, for distributions like

Fedora which don’t keep old packages around. If you don’t like this checking

interupting your command line usage, it’s much better to have something

manually check the metadata once an hour (yum-updatesd will do this).

metadata_expire=90m

PUT YOUR REPOS HERE OR IN separate files named file.repo

in /etc/yum.repos.d


#4

Hi,

You are not running Centos 7, I think I recall this is based on Centos 6 ish. I fear you may run into other issues due to older libraries etc.

At the very least you will have to use startmapd or create your own script to mapd_server and mapd_web_server to automate your mapd instance.

regards