Taking backup
# mysqldump -u -p mydatabase table1 > table1.sql
restoring from backup file need not include table name
# mysql -u -p mydatabase < table1.sql [/bash]
Author: The Geek Decoder
chown influx etc/influxentrepreneur.info/quota chown influx etc/influxentrepreneur.info/shadow chown influx etc/influxentrepreneur.info
# nano /etc/pure-ftpd.conf # Port range for passive connections replies. - for firewalling. PassivePortRange 50000 51000
Restart xinetd
Source: https://documentation.cpanel.net/display/CKB/How+to+Enable+FTP+Passive+Mode#HowtoEnableFTPPassiveMode-Passive
The installation of micro-updates started from the Plesk home screen fails:
Failed to update Panel. You can send the update log to Parallels support to try fixing the issue. View the update log.
Attempting to access the update log fails:
Error Internal error: File specified by 766460e6-7587-54f1-e1be-794e5655c4a4 was not found Message File specified by 766460e6-7587-54f1-e1be-794e5655c4a4 was not found File LogFile.php Line 36 Type Smb_Exception_NotFound
Cause
The Plesk Installer has failed or was terminated.
Workaround
1) (Linux only) Remove the /tmp/psa-installer.lock file
2) Remove stale records from the ‘psa.longtasks’ and ‘psa.longtaskparams’ tables:
mysql -uadmin -p`cat /etc/psa/.psa.shadow` mysql> use psa; mysql> begin; mysql> DELETE longtasks, longtaskparams FROM longtasks INNER JOIN longtaskparams WHERE longtasks.type='panel-update' AND longtaskparams.task_id=longtasks.id; mysql> commit;
Install updates through Tools & Settings > Updates and Upgrades or from the command-line
# /usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base
If the update fails again, Check you logs:
/tmp/autoinstaller3.log
c:\ParallelsInstaller\autoinstaller3.log
New server created with 20GB Drive.
# fdisk -l
Disk /dev/xvda: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00028fed
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2 66 2611 20446208 8e Linux LVM
Disk /dev/mapper/centos-swap: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/centos-root: 19.9 GB, 19860029440 bytes
255 heads, 63 sectors/track, 2414 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root centos -wi-ao---- 18.50g swap centos -wi-ao---- 1.00g
Check Physical Volumes
# pvs PV VG Fmt Attr PSize PFree /dev/xvda2 centos lvm2 a-- 19.50g 0
Now I upgrade the cloud server
to
1024 MB RAM, 1 Core, 40 GB Disk
After upgrade…
# fdisk -l
Disk /dev/xvda: 40.8 GB, 40802189312 bytes
255 heads, 63 sectors/track, 4960 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00028fed
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2 66 2611 20446208 8e Linux LVM
Disk /dev/mapper/centos-swap: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/centos-root: 19.9 GB, 19860029440 bytes
255 heads, 63 sectors/track, 2414 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root centos -wi-ao---- 18.50g swap centos -wi-ao---- 1.00g
# pvs PV VG Fmt Attr PSize PFree /dev/xvda2 centos lvm2 a-- 19.50g 0
Create a new partition (n). Make it primary (p). The start and end should be the defaults provided by fdisk.
# fdisk /dev/xvda
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): p
Disk /dev/xvda: 40.8 GB, 40802189312 bytes
255 heads, 63 sectors/track, 4960 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00028fed
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2 66 2611 20446208 8e Linux LVM
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 3
First cylinder (2611-4960, default 2611):
Using default value 2611
Last cylinder, +cylinders or +size{K,M,G} (2611-4960, default 4960):
Using default value 4960
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Reboot the VM so the kernel picks up the partition changes.
# shutdown -r now
Check for the new partition
# fdisk -l
Disk /dev/xvda: 40.8 GB, 40802189312 bytes
255 heads, 63 sectors/track, 4960 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00028fed
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2 66 2611 20446208 8e Linux LVM
/dev/xvda3 2611 4960 18869680 83 Linux
Disk /dev/mapper/centos-swap: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/centos-root: 19.9 GB, 19860029440 bytes
255 heads, 63 sectors/track, 2414 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Run “pvcreate /dev/xvda3” to make /dev/xvda3 a LVM partition.
# pvcreate /dev/xvda3 Physical volume "/dev/xvda3" successfully created
Check for the name
# vgs VG #PV #LV #SN Attr VSize VFree centos 1 2 0 wz--n- 19.50g 0
Run “vgextend centos /dev/xvda3” to add /dev/xvda3 to the centos volume group.
# vgextend centos /dev/xvda3 Volume group "centos" successfully extended
Check again…
# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root centos -wi-ao---- 18.50g swap centos -wi-ao---- 1.00g
Root “lvresize -r -l +100%FREE centos/root” to resize the / partition.
# lvresize -r -l +100%FREE centos/root Size of logical volume centos/root changed from 18.50 GiB (4735 extents) to 36.49 GiB (9341 extents). Logical volume root successfully resized resize2fs 1.41.12 (17-May-2010) Filesystem at /dev/mapper/centos-root is mounted on /; on-line resizing required old desc_blocks = 2, new_desc_blocks = 3 Performing an on-line resize of /dev/mapper/centos-root to 9565184 (4k) blocks. The filesystem on /dev/mapper/centos-root is now 9565184 blocks long.
Run “df -H”. You should now see 30+ GB size on the / partition.
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root
36G 928M 34G 3% /
tmpfs 496M 0 496M 0% /dev/shm
/dev/xvda1 504M 62M 417M 13% /boot
And fdisk again
# fdisk -l
Disk /dev/xvda: 40.8 GB, 40802189312 bytes
255 heads, 63 sectors/track, 4960 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00028fed
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2 66 2611 20446208 8e Linux LVM
/dev/xvda3 2611 4960 18869680 83 Linux
Disk /dev/mapper/centos-swap: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/centos-root: 39.2 GB, 39178993664 bytes
255 heads, 63 sectors/track, 4763 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
http://www.howtogeek.com/howto/40702/how-to-manage-and-use-lvm-logical-volume-management-in-ubuntu/
The fdisk shows a 256GB Drive. 50GB on root and the question is how to resize up to the 256GB drive for more space.
]# fdsik -l
-bash: fdsik: command not found
root@cpanel [~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
50G 27G 21G 56% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
/dev/sda1 485M 96M 364M 21% /boot
/dev/mapper/VolGroup-lv_home
1.1T 43G 996G 5% /home
/dev/sdc1 917G 200M 871G 1% /backup
root@cpanel [~]# fdisk -l
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004bb0e
Device Boot Start End Blocks Id System
/dev/sdb1 1 121602 976760832 8e Linux LVM
Disk /dev/sda: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00062f67
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 31131 249545728 8e Linux LVM
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders
Units = cylinders of 5103 * 512 = 2612736 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa9b15e21
Device Boot Start End Blocks Id System
/dev/sdc1 1 382818 976760095+ 83 Linux
Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap: 8355 MB, 8355053568 bytes
255 heads, 63 sectors/track, 1015 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_home: 1193.7 GB, 1193690529792 bytes
255 heads, 63 sectors/track, 145124 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
50G 27G 21G 56% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
/dev/sda1 485M 96M 364M 21% /boot
/dev/mapper/VolGroup-lv_home
1.1T 43G 996G 5% /home
/dev/sdc1 917G 200M 871G 1% /backup
You can learn information about the volume group itself with ‘lvdisplay’, ‘vgscan’, ‘lvs’ and ‘vgdisplay’.
root@cpanel [~]# lvdisplay --maps
--- Logical volume ---
LV Path /dev/VolGroup/lv_root
LV Name lv_root
VG Name VolGroup
LV UUID TYNmVB-vtiC-Gce6-FAsk-VXxi-CJDA-K4Pg8g
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2014-08-29 13:01:37 -0400
LV Status available
# open 1
LV Size 50.00 GiB
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Segments ---
Logical extents 0 to 12799:
Type linear
Physical volume /dev/sda2
Physical extents 0 to 12799
--- Logical volume ---
LV Path /dev/VolGroup/lv_home
LV Name lv_home
VG Name VolGroup
LV UUID PojYKo-WnwD-ywxH-6C0V-Ta7U-3sfE-x4szaI
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2014-08-29 13:01:39 -0400
LV Status available
# open 1
LV Size 1.09 TiB
Current LE 284598
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
--- Segments ---
Logical extents 0 to 238465:
Type linear
Physical volume /dev/sdb1
Physical extents 0 to 238465
Logical extents 238466 to 284597:
Type linear
Physical volume /dev/sda2
Physical extents 12800 to 58931
--- Logical volume ---
LV Path /dev/VolGroup/lv_swap
LV Name lv_swap
VG Name VolGroup
LV UUID g2sdlK-rUv3-visr-NlMW-G3As-SOE2-07RDB1
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2014-08-29 13:04:05 -0400
LV Status available
# open 1
LV Size 7.78 GiB
Current LE 1992
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Segments ---
Logical extents 0 to 1991:
Type linear
Physical volume /dev/sda2
Physical extents 58932 to 60923
LVS
lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_home VolGroup -wi-ao---- 931.71g lv_root VolGroup -wi-ao---- 230.00g lv_swap VolGroup -wi-ao---- 7.78g
Both drives are in an LVM configuration. This allows you to create logical partitions that include either or both drives.
/dev/mapper/VolGroup-lv_root exists on the SDA drive (Physical volume /dev/sda2) and
/dev/mapper/VolGroup-lv_home exists on both the SDA and SDB drive. To remove the LVM configuration, re-installation would be necessary, but we can re-configure the LVM configuration so that /dev/mapper/VolGroup-lv_root is larger.
Amazonon DMARC (http://sesblog.amazon.com/post/Tx22ZELXSSZRYZR/What-is-DMARC-and-should-you-use-it).
This Google article is also helpful: https://support.google.com/a/answer/2466563?hl=en
If you scroll down to the ‘Example records’ section, you’ll see a number of examples on how to write the TXT record. Here’s an example of that record:
_dmarc.advancedmediawebs.com. 3600 IN TXT “v=DMARC1; p=quarantine; pct=5; rua=mailto:mark@domain.com”
# mount -t nfs 10.0.0.43:/mnt/vol1 /mnt/nfs mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified
Start the rpcbind service and/or the nfs services to mount the NFS share.
# service rpcbind start #service nfs start
How to install Apache, MySQL and PHP on Ubuntu 14.04
Update
# sudo apt-get update
Apache
# sudo apt-get install apache2
Install MySQL
# sudo apt-get install mysql-server php5-mysql
# sudo mysql_install_db
# mysql_secure_installation
Install PHP
# sudo apt-get install php5 libapache2-mod-php5 php5-mcrypt
Restart Server
# sudo /etc/init.d/apache2 restart
Check Apache
Open a web browser and navigate to http://IPADDRESS. You should see a message saying It works!
Check PHP
# php -r 'echo "\n\nYour PHP installation is working fine.\n\n\n";'
# mysql –version
mysql Ver 15.1 Distrib 5.5.37-MariaDB, for Linux (x86_64) using readline 5.1
I ran the mysql command on the system – I received the error message shown below:
# mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
I checked to see if the mysqld service was running and found it was not.
# systemctl status mysqld.service mysqld.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
When I tried to start the service, it wouldn’t start.
# service mysqld start Redirecting to /bin/systemctl start mysqld.service Failed to issue method call: Unit mysqld.service failed to load: No such file or directory. # systemctl start mysqld.service Failed to issue method call: Unit mysqld.service failed to load: No such file or directory.
I checked the contents of the /etc/my.cnf file and saw the following:
[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 # Settings user and group are ignored when systemd is used. # If you need to run mysqld under a different user or group, # customize your systemd unit file for mariadb according to the # instructions in http://fedoraproject.org/wiki/Systemd [mysqld_safe] log-error=/var/log/mariadb/mariadb.log pid-file=/var/run/mariadb/mariadb.pid # # include all files from the config directory # !includedir /etc/my.cnf.d
I checked for the existence of files and directories
# ls -ld /var/lib/mysql drwxr-xr-x. 19 mysql mysql 4096 Oct 14 23:46 /var/lib/mysql
[root@localhost install]# ls -l /var/lib/mysql/mysql.sock srwxrwxrwx. 1 mysql mysql 0 Sep 29 15:05 /var/lib/mysql/mysql.sock
# ls -l /var/log/mariadb/mariadb.log -rw-r-----. 1 mysql mysql 0 Oct 5 20:49 /var/log/mariadb/mariadb.log
# ls -l /var/run/mariadb/mariadb.pid ls: cannot access /var/run/mariadb/mariadb.pid: No such file or directory
I didn’t see any mariadb.pid file
When I checked the files in the includedir directory, I saw the following:
# ls -l /etc/my.cnf.d total 12 -rw-r--r--. 1 root root 295 Apr 15 2014 client.cnf -rw-r--r--. 1 root root 232 Apr 15 2014 mysql-clients.cnf -rw-r--r--. 1 root root 744 Apr 15 2014 server.cnf
So..how to start the service
# systemctl start mariadb.service # systemctl status mysqld service mysqld.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) service.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
# mysql ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
When I was using CentOS 6, I had MySQL rather than MariaDB – didn’t know I needed to start the MariaDB RDBMS service on the CentOS 7 system using a command referencing mariadb rather mysqld. I assumed I could reference mysqld to start the service.
To have the MariaDB service start automatically each time the system boots, issue the command
“systemctl enable mariadb.service”. After you have started the service, also issue the command
“mysql_secure_installation”.
# mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: command not found
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
You already have a root password set, so you can safely answer 'n'.
Change the root password? [Y/n] n
... skipping.
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n] y
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] Y
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] Y
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n] Y
ERROR 1146 (42S02) at line 1: Table 'mysql.servers' doesn't exist
... Failed!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
Note on copying files to the maria DB!
If you copy DB files to /var/lib/mysql directory from the hard drive of the prior CentOS 6 system to the new CentOS 7 system to have all of the databases from the old system available on the new system, so that appeared to be the reason that the mysql_secure_installation, which can be found in /usr/bin, did not accept my just hitting Enter for the password initially. When I entered the root password for MySQL on the old system, it was accepted. And I was able finally get a prompt where I could enter SQL commands using that password with mysql -u root -p .
# mysql -u root -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 11 Server version: 5.5.37-MariaDB MariaDB Server Copyright (c) 2000, 2014, Oracle, Monty Program Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>
So the 3 steps to enable and run MariaDB are as follows, assuming it was previously installed during the initial setup for the system or with yum install mariadb mariadb-server:
# systemctl start mariadb.service # systemctl enable mariadb.service # mysql_secure_installation