How to manage Linux systems through web browser (cockpit for Linux): CentOS 7, CentOS 8, RHEL 7, RHEL 8, Fedora, Ubuntu and Debian systems.




    Cockpit is a web accessible interactive admin interface for Linux machines. Cockpit can usually be accessed on port 9090 of the machine it's installed on.

    The cockpit-ws web service listens on port 9090 and is started on demand by systemd. The Cockpit web service authenticates the user, loads Cockpit into the browser, and starts cockpit-bridge in a Linux user session. The cockpit-bridge provides Cockpit in the web browser with access to the system APIs. It does this over its standard in and standard out.

    Cockpit can be installed in the following Operating systems. Please not that this list is where I installed and tested, that does not mean that it will not work on other Operating Systems.

  • RHEL 7 & RHEL 8
  • CentOS 7 & CentOS 8
  • Ubuntu
  • Debian


    Cockpit is a very helpful tool which can be used to access the Linux servers through a web browser and do all kind of administration tasks. Some of the main features of Cockpit are:

  • Web GUI administration of local and remote servers.
  • Manage multiple servers in single window.
  • Access to remote terminal through web browser.
  • Management of Docker containers and Kubernetes.
  • Dashboard of local and remote servers to monitor the performance and utilization.
  • Gather diagnostics reports.


    Though I am describing the installation procedure on Debian and Ubuntu in this document, the main focus is on installing and configuring it on CentOS and Linux systems.

Below packages are required for the configuration of Cockpit in CentOS and RHEL systems.

Cockpit              << -- Package to rum cockpit as a service.        
cockpit-storaged            << -- Package required to enable storage utilities in the browser.        
cockpit-ws                          << -- Manage web server 
cockpit-dashboard         << -- Package required to enable dashboard of local and remote systems.        
cockpit-docker                << -- Manage docker container
cockpit-kubernetes       << -- Manage Kubernetes
cockpit-packagekit       << -- manage packages

    Cockpit uses the port number “9090” for web browser access. Please make sure to enable the necessary firewall rules to access the cockpit web browser.

Installation procedure:

CentOS 7 & Cent OS 8 Systems

Install the basic package of cockpit.
# yum install cockpit -y

Enable the service for system start up and start the service.
# systemctl enable cockpit.socket
# systemctl start cockpit.socket

Enable the firewall rules and reload the service.
# firewall-cmd --add-service=cockpit --permanent
# firewall-cmd --reload

This procedure would work of Fedora systems as well.


RHEL 7 & RHEL 8 systems

In RHEL systems before we start the installation enable the necessary repository of cockpit.
For RHEL 7:
# subscription-manager repos --enable rhel-7-server-extras-rpms
 For RHEL 8:
# subscription-manager repos --enable rhel-8-server-extras-rpms

Install the basic package of cockpit.
# yum install cockpit -y

Enable the service for system start up and start the service.
# systemctl enable cockpit.socket
# systemctl start cockpit.socket

Enable the firewall rules and reload the service.
# firewall-cmd --add-service=cockpit --permanent
# firewall-cmd --reload

Ubuntu Systems
Enable the repository and update the packages before installation.
# add-apt-repository ppa:cockpit-project/cockpit
# apt-get update

Install the basic package of cockpit.
# apt-get install cockpit

Enable the service for system start up and start the service.
# systemctl enable --now cockpit.socket

Debian Systems
Need to use an external repository for Debian systems. Configure the repository by editing the file /etc/apt/sources.list and adding the below entry.
deb https://fedorapeople.org/groups/cockpit/debian unstable main
Enable the keys and update the packages by below commands.
# apt-key adv --keyserver sks-keyservers.net --recv-keys F1BAA57C
# apt-get update

Install the software and start the service.
# apt-get install cockpit
# systemctl enable --now cockpit.socket

How to access the cockpit.
As I mentioned above, cockpit uses the port 9090 by default. The cockpit can be accessed through web browser by using the below URL.
http://<IP Address or FQDN of your server>:9090

You will get a web page for login like below. The login credentials are the same you use for the server.

Once you logged in you will see the details like below in the system tab. You will see that the hardware type of the system, host name and system profile as highlighted below. You will get the over all picture of the resource utilization of CPU, Memory, Disk IO and network interfaces from the system page itself.

I have provided the screenshot of  some of the important fields below.
1.        Log watch
The below screenshot shows the current logs on the system. From the above drop-down boxes you can select the log periods and the type of logs to watch.

2.        Disk configuration
From this page you will get to know the details of file systems and their utilization, RAID devices configured, Volume groups, VDO devices, iSCSI devices and their performance etc. This page will help you to make necessary modification to your storage disks as well. For example, file system mount & unmount, lv, vg, partition creations, deletions, extensions etc.

3.        Network configuration
All network configurations can be viewed and modified here.

4.        Terminal
You can access the terminal of the system here.


Configuring remote systems in the dashboard.

So far, we saw the details and how to configure the devices locally. Now we are going to see the same set of details in the remote server.

Minimum requirements are:
1.        Cockpit and its components to be installed in remote system, cockpit service to be up and running and the port 9090 should be enabled for remote access.
2.        The package “cockpit-dashboard” to be installed in the system where the dash board to be enabled, usually where the remote systems are connected for remote administration.
Here in this demo, we have already installed the cockpit packages and its components in the remote system which I am going to connect. My remote system is “labhst1”.  We need to install the package “cockpit-dashboard” in the local system so that I can see another tab called “Dashboard” in the console as below.

# yum install cockpit-dashboard -y



Go to dashboard and click on the below + button to add new hosts. You can add the hosts by either keys or giving login credentials.

Here you can see that the new system added to the dashboard and you can select the remote servers from the drop-down as below.

The individual system details can be seen, and the system can be administrated through web browser as below.


I hope these documents helped you to some extend at least. Thanks for vising this page. You may contact us through email or giving a comment below.

Comments

Post a comment

Popular posts from this blog

AIX Firefox Installation

Overview           Mozilla Firefox for AIX is an Open Source Web Browser. It delivers helpful new features and continues to lead the way in on-line security. It implements technologies like the Gecko layout engine, and supports Web standards or draft standards like HTML, XHTML, XML, CSS, DOM, and many more . Version of Firefox Mozilla Firefox with version 3.5.13.1 can be installed in AIX 5.3 and later. Installation Procedure The following rpm s are the pre requisites for Firefox(64 bit). These packages will be available from the AIX Toolbox for Linux Applications CD/DVD. Before installing the prerequisites check the availability of 150MB free space on the /opt file system. atk-1.12.3-2.aix5.2.ppc.rpm cairo-1.8.8-1.aix5.2.ppc.rpm expat-2.0.1-1.aix5.2.ppc.rpm fontconfig-2.4.2-1.aix5.2.ppc.rpm freetype2-2.3.9-1.aix5.2.ppc.rpm gettext-0.10.40-6.aix5.1.ppc.rpm glib2-2.12.4-2.aix5.2.ppc.rpm gtk2-2.10.6-4.aix5.2.ppc.rpm libjpeg-6b-6.aix5.1.ppc.rpm libpng
Read more

AIX Commands

Usefull Commands for AIX =================== bootinfo –r     shows available RAM in KB lsattr –E l sys0 –a realmem    shows available RAM in KB rmss -c 512    To change the memory size to 512 MB rmss -r          resets the memory size to the original value lsattr  -El  en0     shows en0 driver params lsattr  -El  ent0     shows ent0 HW params lsattr -El rmt0     shows tape params lscfg -vpl rmt0     shows information about the tape drive lsattr  -El  sys0     shows system type, firmware, etc  driver params lscfg –v     lists all system HW configuration lsdev –C sscsi     list all scsi devices lsdev –C spci     list all pci devices lsparent –Ck scsi     list all scsi adapters cfgmgr     To onfigure devices lsdev –Cc disk      Shows all disks lsdev –Cc tape               Shows all tapes cfgmgr -vl < device > –v    Specifies verbose output. The cfgmgr command shows information about what it is doing. cfgmgr -vl < device >      Here <device> is a particular dev
Read more

How to increase swap size on CentOS 8 / RHEL 8

Swap space is the second type of memory in modern Linux systems. The primary function of swap space is to substitute disk space for RAM memory when real RAM fills up and more space is needed. Linux uses swap space to increase the amount of virtual memory available to a host. It can use one or more dedicated swap partitions or a swap file on a regular filesystem or logical volume. Now we are going to check: •              Current swap space in the system. •              How to identify swap volumes in the system. •              How to increase the size of swap volume. •              How to add one more swap device to system. This documentation is based on the test done in a CentOS 4.18.0-80.el8.x86_64 machine. The same procedure can be applied on RHEL 8 as well. We follow the LVM method to manage the volumes here though a normal partition also can be used for swap. We will see both the options here when we add another device as a swap volume. How to check the cu
Read more

How to configure NTP in RHEL8 or CentOS 8 by chronyd.

Network Time Protocol is used in systems to get the clock synced between them. All systems will sync their clock with NTP server is they are configured to do so. In RHEL8 or CentOS 8 it is achieved through “ chronyd ”. The “ chronyd ” daemon can be managed by the command “ chronyc ”. Below steps involve in configuring NTP through chronyd in linux systems. ·         Install the necessary packages. ·         Configure chrony service to sync with NTP server. ·         Set NTP synchronization. ·         Enable necessary firewall rules. ·         Enable and start chronyd service. Installation of chrony on RHEL8 or CentOS8. The below command helps to install chronyd in RHEL/CentOS 8. [root@system1 ~]# yum install chrony -y Chrony (NTP) server configuration The main configuration file for “ chronyd ” is /etc/chrony.conf . [root@system1 ~]# vim /etc/chrony.conf Below the minimum details to be set in the chrony.conf file. ·         pool 2.centos.pool.ntp.org iburst   # The name of the pool wh
Read more

How to find big files in Linux, Unix, AIX

      Most often we see that the utilization of file systems grows up and we need to do some sort of housekeeping in the file system. Mainly we identify which file consumes more space in the file systems. Sometimes we see chunk of files with small size of single file with more size consume more space in the file systems. In either situation our goal is to find out what is consuming more space, identify the necessity of those files in the file system and decide to housekeep the file system by removing the unwanted files. Here are some ways to find the big files in a directory. People mostly use the below steps to identify the big files in a directory. 1.        By using “ du ” command. 2.        By using “ find ” command By using “du” command. Eg .   # du -a / Here “ du ” command will look for all the files in the directory including filesystems mounted on directories under “ / ” directory and list them with their size on kilo bites (KB). If you want to sort
Read more

How to enable VNC server (get GUI remotely) in CentOS 7, RHEL 7, CentOS 8 and RHEL 8 servers.

Minimum requirements to connect a server remotely to access GUI are: 1.        Display server running in your workstation (I used MobaXterm. Software like Xming and VNC clients are also can be used.) 2.        Server running with GNOM workstation and VNC server. As I mentioned above, I have “MobaXterm” installed in my laptop that will work as a display server to connect my CentOS or RHEL server remotely. You may download it from here . It is very easy to use. If you have restrictions to install it in your laptop, then you can use the portable version of it. It can be just executed like PuTTy. To make sure my CentOS or RHEL server running with Desktop software, I use below commands to install them. In CentOS 7 or RHEL 7: [root@labsrv1 ~]# yum groupinstall “GNOME Desktop” In CentOS 8 or RHEL 8: [root@labsrv1 ~]#   yum groupinstall "Server with GUI To install the VNC server, use the below command. Install its dependencies as well, if it prompts for the same.
Read more

Remote X11 forwarding for AIX in command line.

Most of the Unix administrators love to work with command line and it is the most convenient way to work with Unix systems. There were occasions where we had to invoke the GUI for some applications to work with it like, invoke a Firefox browser to browse the internet through Unix systems, install an application in GUI mode etc. Here I am going to describe how can we address such situations by invoking GUI over CLI. Assumptions:           You have an AIX system with remote connection through ssh.           You need to invoke the GUI of an application through Xming or MobaXterm – a DISPLAY server. X Window in AIX server Minimum installation for X Window includes below filesets: X11.base.lib X11.base.rte X11.apps.config X11.apps.clients   (optional to run xclock program – in this case, just for testing purpose) Install the above-mentioned packages to invoke the GUI remotely through command line. Connect through SSH X11 port forwarding On the
Read more

YUM configuration in AIX.

    In earlier days all RPM packages in AIX were installed by the command “rpm”. The limitation for RPM command is that the difficulty to resolve the dependent packages.   Like other Linux operating system like RedHat, CentOS etc. there is a possibility to setup YUM to install packages in AIX. The below procedure will take you through the steps of configuring YUM in AIX (7.1) systems.     After having many trial and error experiments, the final solution came up with YUM configuration on the system, which is already installed with any RPM packages, we may need to follow the steps like: 1.        Take a backup of system (mksysb) 2.        Have the list of currently installed RPM packages. 3.        Remove the existing RPM packages. 4.        Configure YUM as described below. 5.        Install the previous packages again. Let’s start with the configuration now. Assuming that all required backups are in place to do a roll-back in case of any worst-case scenario.
Read more

Upgrade curl 7.29 to 7.69 in CentOS 7 or RedHat 7

By default we can see 7.29 as the latest version of curl in CentOS or RHEL7. Here we are going to see how we can upgrade it to version 7.69. We use city-fan.org repo for the upgrade of curl. Lets see how to install and enable this repo and upgrade the curl package. Install the "city-fan.org" repo # rpm -Uvh http://www.city-fan.org/ftp/contrib/yum-repo/city-fan.org-release-2-1.rhel7.noarch.rpm Enable the repo "city-fan.org" in configuration file. Open the file /etc/yum.repos.d/city-fan.org.repo and enable the repo "city-fan.org" # vim /etc/yum.repos.d/city-fan.org.repo Upgrade the "curl" package from this repo. # yum update curl -y Once the update is done you can check the version of curl package by "rpm" command. # rpm -qa |grep curl libcurl-devel-7.69.1-1.1.cf.rhel7.x86_64 python-pycurl-7.19.0-19.el7.x86_64 libcurl-7.69.1-1.1.cf.rhel7.x86_64 curl-7.69.1-1.1.cf.rhel7.x86_64 #
Read more