Linux Blimp

Time is a very important part of our everyday computing. We, humans, may even tolerate hours of time mismatch but in the case of the computer, even a millisecond mismatch can cause some real trouble. For ensuring that your system’s time is on the correct path, it’s necessary to set the right time zone. When you first install Ubuntu, you can choose the right time zone. In case you need to change the time zone, this guide will help you out.

There are 2 different approaches to changing the time zone – using system tools and using commands.

Change time zone from system settings

Open the GNOME menu.

Search for “time zone”. Select the “Date and Time” from “Settings” section.

Uncheck the option “Automatic Time Zone”. Click on “Time Zone”.

Change to the time zone you want, then close the window.

It’s recommended to restart your system to make sure that all your software are working the updated time zone.

Changing the time zone using the commands

Open up a terminal and run the following commands –

sudo -s
dpkg-reconfigure tzdata

Follow the on-screen steps for selecting your target time zone. Once the time zone change is complete, you’ll see the following confirmation message –

Enjoy!

Source

Bitnami Drupal Stack is a free and multi-platform software project, an all-in-one installer that greatly simplifies the deployment of the Drupal web-based application and its runtime dependencies (MySQL, PHP and Apache) on desktop computers or laptops. It can be deployed using native installers, a virtual machines, cloud images, a Docker container or *AMP modules.

What is Drupal?

Drupal is an open source, free and cross-platform content management system that allows an individual or a group of users to easily publish, manage, and organize a wide variety of content on a website.

Installing Bitnami Drupal Stack

Bitnami Drupal Stack is mainly distributed as native installers for the GNU/Linux, Microsoft Windows and Mac OS X operating systems, supporting 64-bit (recommended) and 32-bit hardware platforms.

To install the Drupal application on your personal computer, just download the package that corresponds to your PC’s hardware architecture, run it and follow the instructions displayed on the screen.

Run Drupal in the cloud

Thanks to Bitnami, users are now able to run their own Drupal stack server in the cloud with their hosting platform or by using a pre-built cloud image for the Windows Azure or Amazon EC2 cloud hosting providers.

Virtualize Drupal or use the Docker container

In addition to install Drupal on your PC or run it in the cloud, you can also use a virtual appliance, designed by Bitnami for the VMware ESX, ESXi and Oracle VirtualBox virtualization software, and based on the latest stable release of the Ubuntu Linux distribution. A Drupal Docker container will also be available on the project’s homepage.

The Bitnami Drupal Module

Besides the Bitnami Drupal Stack product reviewed here, Bitnami also offers a module for its LAMP, WAMP and MAMP stacks, which allows users to deploy the Drupal application on personal computers, without having to install its runtime dependencies.

Source

New releases focus on boot time, new hardware, and modular design.

October is the time of the year when users get to play with new versions of Ubuntu and Fedora.

Canonical announced Ubuntu 18:10, and the Fedora community announced Fedora 29. Both are Gnome-based distributions. Ubuntu focused on faster boot times and improved support for new hardware; Fedora focused on improving its modular design.

“Modularity helps make it easier to include alternative versions of software and updates than those shipped with the default release, designed to enable some users to use tried-and-true versions of software while enabling others to work with just-released innovation without impacting the overall stability of the Fedora operating system,” according to Fedora press release.

Fedora comes in 3 editions: Workstation, Cloud, and Atomic Host. The latest version of Fedora’s desktop-focused edition provides new tools and features for general users as well as developers with the inclusion of GNOME 3.30. Fedora is putting its weight behind Flatpack.

Ubuntu also comes in different editions: Ubuntu Desktop, Ubuntu Server, Ubuntu Cloud, and Ubuntu for IoT. There are different flavors of Ubuntu that support various desktop environments, including KDE Plasma, LXQt, etc.

Snap is the default app packaging and delivery mechanism of Ubuntu that competes with Flatpack. Canonical said that Ubuntu’s Linux app store includes 4,100 snaps from over 1,700 developers with support across 24 Linux distributions.18.10 enables native desktop controls to access files via the host system.

While Fedora remains a distribution for developers (Linus Torvalds himself uses Fedora), Ubuntu still appeals to a wider audience, from gamers to enterprise customers.

Download Ubuntu: https://www.ubuntu.com/download

Download Fedora: https://getfedora.org/en/workstation/download/

Source

The Linux Foundation Open Source Leadership Summit is the premier forum where open source leaders convene to drive digital transformation with open source technologies and learn how to collaboratively manage the largest shared technology investment of our time.

An intimate, by invitation only event, Open Source Leadership Summit fosters innovation, growth and partnerships among the leading projects and corporations working in open technology development. It is a must-attend for business and technical leaders looking to advance open source strategy, implementation and investment.

Read more

Source

Posted by Anthony Pell

An update for libvirt is now available for Red Hat Enterprise Linux 6.6 Advanced Update Support and Red Hat Enterprise Linux 6.6 Telco Extended Update Support. Red Hat Product Security has rated this update as having a security impact —–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

=====================================================================
Red Hat Security Advisory

Synopsis: Important: libvirt security update
Advisory ID: RHSA-2018:3400-01
Product: Red Hat Enterprise Linux
Advisory URL: https://access.redhat.com/errata/RHSA-2018:3400
Issue date: 2018-10-30
CVE Names: CVE-2018-3639
=====================================================================

1. Summary:

An update for libvirt is now available for Red Hat Enterprise Linux 6.6
Advanced Update Support and Red Hat Enterprise Linux 6.6 Telco Extended
Update Support.

Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.

2. Relevant releases/architectures:

Red Hat Enterprise Linux Server AUS (v. 6.6) – x86_64
Red Hat Enterprise Linux Server Optional AUS (v. 6.6) – x86_64
Red Hat Enterprise Linux Server Optional TUS (v. 6.6) – x86_64
Red Hat Enterprise Linux Server TUS (v. 6.6) – x86_64

3. Description:

The libvirt library contains a C API for managing and interacting with the
virtualization capabilities of Linux and other operating systems. In
addition, libvirt provides tools for remote management of virtualized
systems.

Security Fix(es):

* An industry-wide issue was found in the way many modern microprocessor
designs have implemented speculative execution of Load & Store instructions
(a commonly used performance optimization). It relies on the presence of a
precisely-defined instruction sequence in the privileged code as well as
the fact that memory read from address to which a recent memory write has
occurred may see an older value and subsequently cause an update into the
microprocessor’s data cache even for speculatively executed instructions
that never actually commit (retire). As a result, an unprivileged attacker
could use this flaw to read privileged memory by conducting targeted cache
side-channel attacks. (CVE-2018-3639 virt-ssbd AMD)

Note: This is the libvirt side of the CVE-2018-3639 mitigation.

Red Hat would like to thank Ken Johnson (Microsoft Security Response
Center) and Jann Horn (Google Project Zero) for reporting this issue.

4. Solution:

For details on how to apply this update, which includes the changes
described in this advisory, refer to:

https://access.redhat.com/articles/11258

After installing the updated packages, libvirtd will be restarted
automatically.

5. Bugs fixed (https://bugzilla.redhat.com/):

1566890 – CVE-2018-3639 hw: cpu: speculative store bypass

6. Package List:

Red Hat Enterprise Linux Server AUS (v. 6.6):

Source:
libvirt-0.10.2-46.el6_6.9.src.rpm

x86_64:
libvirt-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-client-0.10.2-46.el6_6.9.i686.rpm
libvirt-client-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-debuginfo-0.10.2-46.el6_6.9.i686.rpm
libvirt-debuginfo-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-devel-0.10.2-46.el6_6.9.i686.rpm
libvirt-devel-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-python-0.10.2-46.el6_6.9.x86_64.rpm

Red Hat Enterprise Linux Server TUS (v. 6.6):

Source:
libvirt-0.10.2-46.el6_6.9.src.rpm

x86_64:
libvirt-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-client-0.10.2-46.el6_6.9.i686.rpm
libvirt-client-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-debuginfo-0.10.2-46.el6_6.9.i686.rpm
libvirt-debuginfo-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-devel-0.10.2-46.el6_6.9.i686.rpm
libvirt-devel-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-python-0.10.2-46.el6_6.9.x86_64.rpm

Red Hat Enterprise Linux Server Optional AUS (v. 6.6):

x86_64:
libvirt-debuginfo-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-lock-sanlock-0.10.2-46.el6_6.9.x86_64.rpm

Red Hat Enterprise Linux Server Optional TUS (v. 6.6):

x86_64:
libvirt-debuginfo-0.10.2-46.el6_6.9.x86_64.rpm
libvirt-lock-sanlock-0.10.2-46.el6_6.9.x86_64.rpm

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://access.redhat.com/security/team/key/

7. References:

https://access.redhat.com/security/cve/CVE-2018-3639
https://access.redhat.com/security/updates/classification/#important
https://access.redhat.com/security/vulnerabilities/ssbd

8. Contact:

The Red Hat security contact is . More contact
details at https://access.redhat.com/security/team/contact/

Copyright 2018 Red Hat, Inc.
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1

iQIVAwUBW9hmt9zjgjWX9erEAQjL3w//REIrMBGNTNbKYC8OHWDjEloO/PxqCPQr
e0wxa/67xN+8i/DFZGd0scd8UghTIoZqj4IK7ZVjxxq1Vf5YlNhC3ot4uAFZ5zi2
d+HxmA5X5901w7bOIbkQNBak6IP6KQbZW1VcucBC5uMdklzogEwAyhYkZOnzXPNd
ix9Ul1IcrTmM+hr8qzJ/KZuTkweXIuSZ+B+cKa2cGc5ZlGp2a+jrnndVO2qyILmo
9KjpfN2BuAc+bK+NveFIJYXFXTbbTqIjA3Ax5t01k+Q7Kz4nhA3qdUsmXdgsL5hz
mUnmsagQrnPhsLw7VetbD4/R65HRxR/W/Vskudt2rYo1Qm9PnLOYK1VrTTgv4Ee/
UTf3utrlGXmX7vHgMUqOlZviN4Izy8qFW/iLas5XuLHtVb2rNyt5qVeAcOmnW6x2
oMvMVIg0znfwpdK07SO3SDhGoRKnqAVGeHY1laZS/j14NdFcP1UjyZr2gxtcsj2W
Crhj6qbnk+5FvjreXRyaoWWOVAWqcq3LIU0t1LHhBk336R06S1y/zZAuYeCW4gFV
uKqnJaMVZfaWQeWKU+1JrTXjy2Sd7gwDvPIwWXIakhBfSM6vY3VEqE/3sAE4tpfV
snb/ASJ3g3sOUasw8t+sMI0g+eqShcOKoGLOOj655HlhNkFCRb5m31+EYYkg/jmD
0gzfMxuSQf4=
=znp/
—–END PGP SIGNATURE—–

—
RHSA-announce mailing list
RHSA-announce@redhat.com
https://www.redhat.com/mailman/listinfo/rhsa-announce

Source

Source

Let’s talk about Amazon CloudWatch.

For those fortunate enough to not be stuck in the weeds of Amazon Web
Services (AWS), CloudWatch is, and I quote from the official
AWS description, “a monitoring and
management service built for developers, system operators, site reliability
engineers (SRE), and IT managers.” This is all well and good, except for the
part where there isn’t a single named constituency who enjoys working with
the product. Allow me to dispense some monitoring heresy.

Better, let me describe this in the context of the 14 Amazon
Leadership Principles that reportedly guide every decision Amazon makes.
When you take a hard look at CloudWatch’s complete failure across all
14 Leadership Principles, you wonder how this product ever made it out
the door in its current state.

“Frugality”

I’ll start with billing. Normally left for the tail end of articles like
this, the CloudWatch billing paradigm is so terrible, I’m leading with
it instead. You get billed per metric, per month. You get billed per
thousand metrics you request to view via the API. You get billed per
dashboard per month. You get billed per alarm per month. You get charged for
logs based upon data volume ingested, data volume stored and “vended logs”
that get published natively by AWS services on behalf of the customer. And,
you get billed per custom event. All of this can be summed up best as
“nobody on the planet understands how your CloudWatch metrics and logs get
billed”, and it leads to scenarios where monitoring vendors can inadvertently
cost you thousands of dollars by polling CloudWatch too frequently. When the
AWS charges are larger than what you’re paying your monitoring vendor, it’s
not a wonderful feeling.

“Invent and Simplify”

CloudWatch Logs, CloudWatch Events, Custom Metrics, Vended Logs and Custom
Dashboards all mean different things internally to CloudWatch from what you’d
expect, compared to metrics solutions that actually make some fathomable
level of sense. There are, thus, multiple services that do very different
things, all operating under the “CloudWatch” moniker. For example, it’s not
particularly intuitive to most people that scheduling a Lambda function to
invoke once an hour requires a custom CloudWatch Event. It feels overly
complicated, incredibly confusing, and very quickly, you find yourself in a
situation where you’re having to build complex relationships to monitor
things that are themselves far simpler.

“Think Big”

All business people, when asked what they want from a monitoring platform,
will respond with something that resembles “a dashboard” or “a
single pane of glass view”. CloudWatch offers minutia up the wazoo, but
it categorically offers no global view, no green/yellow/red status
indicator that gives you even a glimmer of the overall health of your site.
Want a graph of each core in your instance’s CPU for the past 30
seconds? Easy! Want to know if your entire company should be putting out the
burning fire that is the current production state of your website? Keep
looking—CloudWatch has nothing to offer you.

“Insist on the Highest Standards”

By its very nature, CloudWatch feels like small thinking. The entire
experience, start to finish, smacks of “what’s the absolute least we
could do and get away with it?” They built their MVP, and then just
sorta…stopped, frozen in amber. They created a set of building blocks,
except they didn’t solve the problem of “how do I monitor my AWS resources?”
Instead, it feels like the entire team phoned it in and let a large market
of monitoring vendors develop as a result. None of those vendors have the
level of access to the raw data that CloudWatch does; all of them have built
better products. You’d think the CloudWatch team would take a clue from
the innovation that’s rapidly happening in this space, but that’d
require someone to Learn and Be Curious.

“Are Right, a Lot”

Recent data is “eventually consistent”, so you always get graphs like the
one shown in Figure 1.

Figure 1. Example CloudWatch Graph

Here in reality, that would be a terrifying thing to see on an accurate
dashboard—something is obviously very wrong with your site! For better or
worse, the “accurate” description doesn’t apply to CloudWatch, and that’s
just how your graphs always look. “Your metrics will be eventually
consistent” is very nearly the last thing you want to hear about your
monitoring platform, second only to “what metrics?” This ties directly
to…

“Earn Trust”

Let me be very clear here—the real issue isn’t the ingestion problem.
Absolutely every vendor on the planet has the same issue—you can’t
display data you don’t have. Where CloudWatch drops the ball is in
exposing this behavior to the end user without explanation as to what’s
going on. Thus, until you grow accustomed to it, you have a heart-stopping
moment of “what the hell just happened to the site” whenever you
glance at a dashboard. This conditions you to be entirely too calm when
looking at sensible dashboards when a disaster just happened. If you trust
what the CloudWatch dashboards show you, you’re making a terrible
mistake.

“Dive Deep”

If you’re using Lambda or Fargate, you have no choice but to use CloudWatch
Logs, wherein searching for everything is absolutely terrible. If you’re
using CloudWatch Logs to diagnose anything, congratulations: you’re
diving so deep, you may drown before making it back to the surface.
For example, if I have a Lambda function that throws an error, in order to
diagnose the problem, I must:

• Find the fact that it encountered an error in the first place by looking at
  the invocation error CloudWatch dashboard. I also could set up a filter to
  run a continuous query on the logs and alert when something shows up, except
  that isn’t natively supported—I need a third-party tool for that (such
  as
  PagerDuty).
• Go diving into a variety of CloudWatch log groups and find the one named
  after the specific erroring function.
• Scroll manually through the many, many, many pages of log groups to find the
  specific invocation that threw an error.
• Realize that the JSON object that’s retained isn’t enough to troubleshoot
  with, cry in despair, and go write an article just like this one.
• Do some quick math and realize I’m paying an uncomfortable percentage of my
  AWS bill for a service that’s only of somewhat marginal utility at best.

“Deliver Results”

All of your metrics, all of your logs—they’re locked away inside
CloudWatch’s various components. You’re not going to find a
“page me when this threshold is exceeded” option in CloudWatch; your
options are relegated to “design an alert delivery pipeline with baling
wire and SNS” or pay a non-AWS vendor for another monitoring product.

“Customer Obsession”

CloudWatch keeps all of your metrics. It keeps your logs. It lets you build
custom dashboards to view your metrics all in one place. The building blocks
of a great service are already here—it’s the expression of that utility
that falls short, sometimes drastically. The fact that large monitoring
vendors are premier sponsors of AWS events would be laughable if CloudWatch
ever were to get its act together. You’d not need a third party to make
sense of a pure AWS environment, and many of them would starve to death as
they grow too weak to interrupt your conversation to ask if they can scan
your badge. Choosing to use CloudWatch vs. literally anything else is like
buying a car. “Why yes, I would like to buy the Yugo instead of the Honda.
After all, it checks all the boxes of technically being a car, so it’s fine,
right?”

“Disagree and Commit”

It may very well be that the root cause of many of CloudWatch’s failings
comes from the product engineers who built it misunderstanding this
(admittedly slippery!) Leadership Principle. It’s envisioned as
passionately expressing your reservations about a decision, but once
it’s reached that you commit to the decision that was made.
Unfortunately, it appears that the engineering teams responsible for
CloudWatch decided to “Disagree in Commits” and inflict their
arguments upon the world in the form of the product.

“Ownership”

If I were to go on the internet and post about how terrible virtually any
other AWS service was, people would rally to that service’s defense.
It’s the internet; people will do that. But when these and many more
similar comments about CloudWatch appear, and nobody from AWS pipes in to
say “wow, I’m sorry, why do you feel that way?”, it’s
abundantly clear that if any people on the CloudWatch team really care about
the product, they’ve been locked in a malfunctioning bathroom stall for
the better part of a decade. These comments go back at least that far, but
Amazon
is
totally
on
it, rocking
the company’s “Bias for Action” principle.

“Hire and Develop the Best”

The people who build CloudWatch aren’t terrible at their jobs; I
genuinely believe they don’t quite grasp how their product is perceived.
Given that it’s poor form to write a rant like this and not offer
suggestions for positive improvement, here are some product enhancements I’d
like to see:

• Give me the option to rate-limit API calls at arbitrary levels rather than
  being surprised at month end by a bill that’s approximately Zanzibar’s
  GDP.
• “Here’s an error that your Lambda function threw, here’s the log output from
  that specific function” should be at most two clicks away—not 30.
• If your dog has a litter of 14 puppies, perhaps you don’t need to name
  all of them subtle variations of the term “CloudWatch”. The proliferation of
  services and companies that all start with the word “Cloud” is the subject
  of a completely separate rant.

Please don’t misunderstand me. I use, enjoy and promote AWS services,
and I’m considered to be “an authentic voice” largely because in
addition to praising things that are wonderful, I’ll call out things
that aren’t, as I’ve just done. I’ve built my career and
business on working within that ecosystem. I find AWS employees to be
intelligent and well-intentioned, and most of their services quite good.
CloudWatch could get there with some work, but it’s got a number of very
painful usability issues that keep it from being good, let alone great.

Source

How to Install cPanel on CentOS 7

cPanel is the most popular and most widely-used control panel for managing and automating web hosting tasks. It is the world’s most intuitive and user-friendly control panel, with a very simple and straight-to-the-point graphical interface. cPanel is a Linux-based web hosting control panel, that utilizes a 3 tier structure for system administrators, resellers and end-user website owners, all via a web-browser. Other than the beautiful user interface, cPanel has command line access and API-based access for third-party software integration, for web hosting providers or developers and administrators to automate their system administration processes. In this tutorial, we will show you how to install WHM and cPanel on CentOS 7.

cPanel Installation Requirements

• CentOS 7 VPS
• Minimum of 1GB RAM (2GB RAM is recommended)
• Minimum 20GB disk space (40GB recommended)
• cPanel license (there is also 15 day trial period which gets activated as soon as the installation is complete)

Installation of cPanel in CentOS 7

1. Connect to your server

First, you need to connect to your server via SSH.

To connect to your server via SSH as user root, use the following command:

ssh root@IP_ADDRESS -p PORT_NUMBER

and replace “IP_ADDRESS” and “PORT_NUMBER” with your actual server IP address and SSH port number.

2. WHM/cPanel installation

Cpanel is written in Perl, so before we start the installation you must make sure that you have Perl installed on your server.

To install Perl in your server, run the following command:

yum install perl

WHM/cPanel also requires that the hostname of your server is a Fully Qualified Domain Name (FQDN) that does not match any of your server’s domains. In our example, we will set the hostname of our server to host.mydomain.com (you can replace mydomain.com with your actual domain name). To change the hostname of your server you can use the following command:

hostnamectl set-hostname host.mydomain.com

To download the cPanel installation script you will need to use the cURL command. If cURL is not present on your server you can install it with the following command:

yum install curl

Before you download the script, let’s change your current directory to /home with the following command:

cd /home

You can now download the latest version of cPanel & WHM with:

curl -o latest -L https://securedownloads.cpanel.net/latest

To start the installation, execute the following command:

sh latest

You should see the following output on your screen, indicating that the installation has been started:

Verifying archive integrity… All good.
Uncompressing cPanel & WHM Installer……
____ _
___| _ __ _ _ __ ___| |
/ __| |_) / _` | ‘_ / _ |
| (__| __/ (_| | | | | __/ |
___|_| __,_|_| |_|___|_|

Installer Version v00080 rfaafe3bcf5b92fd14d1cb80357765325dd0f351a

Beginning main installation.

The installation process may take up to 30 minutes. After the installation is complete, you may be asked to reboot your server. The following output will be displayed on your screen:

cPanel install finished in 17 minutes and 44 seconds!
2018-10-19 13:08:18 1195 ( INFO): Congratulations! Your installation of cPanel & WHM 11.74 is now complete. The next step is to configure your server.
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): Before you configure your server, ensure that your firewall allows access on port 2087.
2018-10-19 13:08:18 1195 ( INFO): On RHEL, CentOS, and CloudLinux systems, execute /scripts/configure_firewall_for_cpanel to accomplish this.
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): After ensuring that your firewall allows access on port 2087, you can configure your server.
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): 1. Open your preferred browser
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): 2. Type https://1.2.3.4:2087 in the address bar
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): 3. Enter the word root in the Username text box
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): 4. Enter your root password in the Password text box
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): 5. Click the Login button
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): Visit https://go.cpanel.net/whminit for more information about first-time configuration of your server.
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): Visit http://support.cpanel.net or https://go.cpanel.net/whmfaq for additional support
2018-10-19 13:08:18 1195 ( INFO):
2018-10-19 13:08:18 1195 ( INFO): Thank you for installing cPanel & WHM 11.74!

You can now open your browser and navigate to https://your-server-ip:2087

This will give you access to WHM (Web Host Manager) from where you can finish the installation in your browser. WHM is a web hosting manager that allows administrative access so you can manage every cPanel hosting account on your server.

With WHM you can create cPanel user accounts, manage them, establish pricing tiers, monitor the services running on the server and the server resources, generate user backups, transfer data between WHM hosts, and more.

To log in, enter “root” as username and use your root password.

Once logged in, you need to read the cPanel and WHM End User License Agreement and then click on I Agree/Go to Step 2 to proceed to the next step.

You will be taken to the Set Up Networking part of the configuration. Here you will need to enter your contact information. Enter your email address in the Server Contact Email Address field. In the Hostname section, you will also be able to enter a new hostname.

In the Resolvers section, cPanel will automatically detect and fill in the details with the resolvers provided by your internet service provider. If your ISP does not have DNS resolvers, you can use Google’s public DNS resolvers. The last section lets you choose the Main Network or Ethernet Device. After you are done, you can click on Save and Go to Step 3.

In Step 3, you will be able to set your server’s main IP address. You can also add additional IPs if you have more than one IP address assigned to your server. Once you are done with this step, you can click on Go to Step 4.

In Step 4, you can choose your Nameserver Configuration. There are multiple options available and you can check the advantages and disadvantages of each of them. It is recommended that you choose the BIND name server option. If you do not want to have DNS server on your VPS you can choose the Disabled option.

If you scroll down, you will also be able to enter the nameservers that will be assigned to your server (for example ns1.mydomain.com/ns2.mydomain.com). In the end, you will need to check the Add “A Entries” for Hostname checkbox and enter your server IP address. When you are done, click on Save and Go to Step 5.

In the next step, you can choose which FTP server you would like to use on your server. The recommended option is Pure-FTPD, but if you want to use an FTP server you can choose the Disabled option. You can also enable and configure the cPHulk Brute Force Protection on this page.

And finally, on the last step, you will be able to choose to enable file system quotas or not. If you want to be able to track the amount of disk space used by individual users, you should make sure that file system quotas are enabled. To finish the initial configuration click on the Finish button.

You can now access the main WHM home page. If you already have a valid cPanel license and it is not yet activated on your server, you can log back to your server via SSH and run the following command:

/usr/local/cpanel/cpkeyclt

And that’s it. WHM/cPanel has now been installed on your server. For more information about cPanel, its features, and configuration, you can check the official cPanel documentation page.

Of course, you don’t have to Install cPanel on CentOS 7 if you use one of our cPanel hosting services, in which case you can simply ask our expert Linux admins to install Install cPanel on CentOS 7, for you. They are available 24×7 and will take care of your request immediately.

PS. If you liked this post, on Installing cPanel on CentOS 7, please share it with your friends on the social networks using the buttons below or simply leave a comment in the comments section. Thanks.

Source

Game Dev Studio, another game to let you attempt to rise to greatness in the games industry just recently added a Linux version.

Here’s what they said about it:

With that said, the game now features a Linux build on the default (non-develop) branch of the game. This does not mean that the game officially supports Linux yet (it will when Update #23 is released). However it does mean that support for it is right around the corner. So if you have any friends that have been interested in the game, but weren’t able to play it because they run Linux, now is a good time to tell them that this is about to change! As usual, because this content is still in-development, there may be stability issues with it. It’s best to wait until Update #23 is formally released before trying out the Linux build of the game.

As the developer said, it might be best to wait until the next update where it will have “official” support. Still, it’s really great to see more developers put up early Linux builds to get more feedback and it’s something I applaud.

The game does sound quite interesting and a little more open than previous attempts at this type of game. With the ability to expand by purchasing new buildings, dealing with building game engines as well as the games, various forms of advertising, the ability to buy out your competitors along with different game modes. It certainly sounds quite interesting.

Find it on Steam.

Hat tip to NuSuey/TuxDB.

Source

If your company is in need of a Content Management System (CMS), there are a bevy of available options, many of which are open source. One such option is the Subrion CMS. Subrion is a free, open source CMS that includes all the features you need:

• Admin Dashboard
• Easy content management (including blogs, custom fields, languages, emails)
• Templates
• Plugins
• SEO Inclusive
• Mobile friendly
• User/group management
• One-click upgrades

Subrion can be installed on any platform that includes the following requirements:

• Apache 1.3 or above (mod_rewrite module installed)
• MySQL 4.1 or above
• PHP 5 or above (GD lib, XML lib, FreeType installed)

SEE: Side-by-side chart of popular Linux distros (Tech Pro Research)

I’m going to walk you through the process of installing Subrion on the Ubuntu Server 16.04 platform. The process isn’t difficult, nor should it consume too much of your time.

Let’s get to work.

Update/Upgrade

The first thing will do is update and upgrade our server. Remember, this process could upgrade your kernel, which would require a reboot. If this is a production server, make sure the upgrade happens at a time when a reboot is feasible.

To update and upgrade the Ubuntu Server, open a terminal window and issue the commands:

sudo apt-get update
sudo apt-get upgrade

Once those commands finish, if the kernel is upgraded, reboot the server with the command sudo reboot.

Installing dependencies

The next step is to install the necessary dependencies. We’ll first install the web and database servers with the following commands:

sudo apt-get install apache2
sudo apt-get install mysql-server

During the MySQL server install, you will be required to create/verify an admin user password.

Now we’ll install the remaining dependencies. Back at the terminal window, issue the following command:

sudo apt-get install php libapache2-mod-php php-mysql php-mbstring php-xml php-gd unzip

Create the database

We now must create a database for Subrion. From the terminal window, issue the command:

mysql -u root -p

Type the admin user password you created during the MySQL server installation. From the MySQL prompt, type the following commands:

CREATE DATABASE subrion;
GRANT ALL PRIVILEGES ON subrion.* TO ‘subrionuser’@’localhost’ IDENTIFIED BY ‘PASSWORD’ WITH GRANT OPTION;
FLUSH PRIVILEGES;
EXIT;

where PASSWORD is a unique, strong password.

Configure Apache

Apache must be configured to know about Subrion, as well as have mod_rewrite, php7.0, and mpm_prefork enabled. The first thing to do is edit the default Apache .conf file to add the mod_rewrite options. Issue the command:

sudo nano /etc/apache2/sites-available/000-default.conf

In that file, add the following under the DocumentRoot /var/www/html line:

<Directory /var/www/html>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
</Directory>

Save and close that file.

Enable the modules with the commands:

sudo a2enmod mpm_prefork
sudo a2enmod php7.0

Restart Apache with the command:

sudo systemctl restart apache2

Download the Installer Package

Now we’re going to download the source package, unpack it, and give it the necessary permissions. First change into the /var/www/html directory with the command:

cd /var/www/html

Download the necessary file with the command:

sudo wget https://tools.subrion.org/get/latest.zip

Unzip the file with the command:

sudo unzip latest.zip

Set the necessary permissions with the following commands:

sudo chmod -R 777 tmp/ modules includes/
sudo chmod 777 backup/ uploads/

Start the web-based installer

Open a browser and point it to http://SERVER_IP/install (where SERVER_IP is the IP address of the server hosting Subrion). This should land you on the pre-installation check, where everything should test out okay (Figure A).

Figure A

The Subrion pre-installation checks out.

 

Click Next to begin the installation. This process requires the following:

• License agreement (it’s a GPL license, so just click Next).
• General/Database/Administrator setup (Figure B).

Figure B

The Subrion install configuration page.

 

Once you’ve configured Subrion, click Next and you’ll find yourself on the final page (Figure C), where you can install plugins, or go directly to either the Admin panel or the Home page.

Figure C

The Subrion installation is complete.

 

The final step is to change the permissions of the Subrion configuration file so that it is unwritable and remove the install.php file. Do this with the commands:

sudo chmod u-w /var/www/html/includes/config.inc.php
sudo rm /var/www/html/install/modules/module.install.php

At this point you can continue configuring Subrion to perfectly meet the needs of your business. Congratulations on successfully installing a powerful, flexible, open source Content Management System.

Also see

• How to monitor your Linux server with Glances (TechRepublic)
• How to install Zentyal Server on Ubuntu Server 16.10 (TechRepublic)
• How to install OrangeHRM on Ubuntu 16.04 (TechRepublic)
• How to install the Dolibarr ERP/CRM on Ubuntu 18.04 (TechRepublic)
• Around 62 percent of all Internet sites will run an unsupported PHP version in 10 weeks (ZDNet)
• Pretty low level, pretty big deal: Apache Kafka and Confluent Open Source go mainstream (ZDNet)

Source