YUM.v7

Installing

New Server

Mrepo

smartd

RAID

Hardening

YUM

Crontabs

LogWatch

systemctl

firewalld

CentOS 7

Packages

Apache

Bind

Cacti

DHCP

mariadb

Samba

Sarg

Sendmail

Smokeping

Rsync

Work Apps

Problems

VPN

VPN Win

Extras

Bash

MailScanner

Horde

Google CE

Wake Up

KVM

Other

Computer Lab

ISO2USB

aiContact

Google CE

Android

USB Live

SRS XML

YUM

yum install emacs wget lynx

SELinux

Turn of right now:

setenforce 0

Still seems to ne more owrk than it appears worth.

emacs /etc/selinux/config
SELINUX=disabled

YUM

YUM is the way we now upgrade or install new modules.

Currently we are not running an mrepo server, internet is fast enough.

So leave /etc/yum.repos.d/ as is, but depending on the use of the server we may want to add:

Groups

Show groups

yum grouplist hidden
yum grouplist

EPEL

We need the epel repository in yum for installing various things. You may choose to uninstall this repo later.

wget https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-11.noarch.rpm
rpm -ihv epel-release-7-11.noarch.rpm

Upgrade

yum upgrade

Check where the updates are coming from. Even though we have installed epel, becuase we have not done anything extra with the server there should be no updates from epel. All the updates should be from updates.

i.e.

tzdata                      noarch   2014i-1.el7                                   updates   434 k

GUI

yum groupinstall "GNOME Desktop"

Setup for GUI boot is done via commands now, not /etc/inittab. Use:

systemctl get-default 

To find the current configurations. A multi-user terminal interface is set with:

systemctl set-default multi-user.target

A multi-user graphical interface is set with:

systemctl set-default graphical.target

Current Issues

Post Kernel Update

After a kernel update, on the reboot the start up seems to hang. This is actually graphics drivers not starting, and is due to an incompatibility between the compiled NVIDIA drives and the new kernel. We have to reinstall the NVIDIA drivers.

• Press Ctrl-Alt-F2 to get to a termianl screen.
• Login

sudo bash

• Change default startup

systemctl set-default multi-user.target

• This puts your machine in to terminal mode.

reboot

• Login

sudo bash

• In my case I had the drivers in Downloads

sh ./Downloads/NVIDIA-Linux-x86_64-340.98.run

• I accepted all the defaults and over wrote the existing drivers and configuration.
• The NVIDIA driver file was set to chmod 777
• Once done:

systemctl set-default graphical.target

Rebooted and I could get in to the server

Bad Kernel Update

23/03/2016

Had a bad kenerl upgrade and have reverted back to 3.10.0 229.20.1, so on a reboot rather than use the latest that was loaded I arrowed down to this older one and everything started okay.

I had to start in CLI mode, but my screen was blank and I could not get to a prompt. Easy way around this was to ssh in from another computer and change the settings from graphical to multi-user.

To find current run level

systemctl get-default

graphical.target

To change

systemctl set-default multi-user.target

This will give you a multiuser system that is command line only. Later to change back:

systemctl set-default graphical.target

Rebooted and could get in to the server

Made sure all updates where installed.

Reinstalled the custom NVIDIA drivers (as root), I seem to have to do this often. Dropped to my normal user and

startx

Odd the system started up on gnome and I wanted kde, had to crash back to the command line and run this:

echo "exec startkde" >> ~/.xinitr

Now

startx

and I got kde and had to do a few tweeks to get the two screens right.

Live DVD Rescue

For access from another PC running putty.

Had to do this quite often when no where near the server that has had a stroke.

• Drop down to Terminal
• Become

su

• Create a password for root, passwd, and use letmein
• Stop the firewall.

systemctl stop firewalld.service

• Start sshd

systemctl start sshd.service

• Got a raid?

cat /proc/mdstat

• My raid was a partition ONLY used by the Windows Server VM

• Did you find this page useful?
• Do you have an issue that you have not yet fixed?

We can do this for you.

I am available for technical support. Please follow this link. Tech Support Request.
+64-6-880-0000 : ++1-808-498-7146 : help@ai.net.nz
Getting us to help you