Cockpit – A remote manager for GNU/Linux servers

Sponsored Link
Cockpit is an interactive server admin interface. It is easy to use and very light weight.

Cockpit Features

Easy to use

Cockpit is perfect for new sysadmins, allowing them to easily perform simple tasks such as storage administration, inspecting journals and starting and stopping services.

No interference

Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface.

Multi-server

You can monitor and administer several servers at the same time. Just add them with a single click and your machines will look after its buddies.

Note:- Unless you got Cockpit via a stable release of an OS, treat it as pre-release software. We recommend installing pre-release versions in a virtual machine.

Install cockpit on ubuntu 15.04/15.10

Open the terminal and run the following commands

sudo add-apt-repository ppa:jpsutton/cockpit

sudo apt-get update

sudo apt-get install cockpit

Once you finish the installation you need to start the cockpit service using the following command

sudo systemctl start cockpit

If you want to start cockpit service automatically when you reboot your server use the following command

sudo systemctl enable cockpit.socket

Cockpit GUI access

You can access cockpit GUI using the following URL

https://server-ip:9090

Once it opens you should see the following screen here you need to enter your login details to enter

1

Once it opens you should see the following screen

2

Cockpit Screenshots

3

4

5

If you want to manage multiple servers using cockpit first you have to install cockpit on all the servers.

Sponsored Link

You may also like...

12 Responses

  1. Jo says:

    This howto is only for 15.04/15.10

    Neither are LTS release AFAIK. Is therre a howto for LTS releases of Ubuntu server?

  2. Miguel Nunes says:

    I’d also like to see this on 14.04 LTS.

  3. JD says:

    +1 for LTS release support.

    Anyone running a server should begin and end with an LTS release. The only reason to run a non-LTS release is for a lab or when the server shutdown date is within the 6 month support window for the non-LTS release. Just remember that company management will **always** change their mind and having a server running a non-supported OS is a complete failure of the IT team.

  4. zaxebo1 says:

    it can not run on 14.04LTS because it neds systemd, which was supported in ubuntu only since 15.04. So if you want LTS to support cockpit , then you will have to really wait for ubuntu 16.04LTS

  5. RoseHosting says:

    to run cockpit on ubuntu 14.04 you must install glib-networking

    sudo apt-get install glib-networking

    and then run

    sudo /usr/sbin/remotectl certificate –ensure –user=root –group=
    sudo /usr/libexec/cockpit-ws

    or create an upstart/init script

  6. ronator says:

    Thank you, RoseHosting for these information. I would like too add one more step for Linux Mint (which uses Ubuntu Packages) to get cockpit running. I had some errors like:

    cockpit-bridge-Message: pcp-archive: couldn’t create pcp archive context for /var/log/pcp/pmlogger/somehost.somedomain: No such file or directory
    […]
    Error Parsing ASCII PMNS: Cannot open “/var/lib/pcp/pmns/root”

    There were no graphs drawed in the webinterface. To solve this error, simply install ‘pcp’ with all dependencies:

    # sudo apt-get install pcp

    Afterwards, restart cockpit and it should work.

  7. Tim H says:

    This doesn’t seam to be available on 15.10(wily) as stated….

    Checking http://ppa.launchpad.net/jpsutton/cockpit/ubuntu/dists/wily/ gives..
    The requested URL /jpsutton/cockpit/ubuntu/dists/wily/ was not found on this server.

    Also, apt-get update gives…

    W: Failed to fetch http://ppa.launchpad.net/jpsutton/cockpit/ubuntu/dists/wily/main/binary-amd64/Packages 404 Not Found

    W: Failed to fetch http://ppa.launchpad.net/jpsutton/cockpit/ubuntu/dists/wily/main/binary-i386/Packages 404 Not Found

    This is following the howto above. Has something changed?

  8. Aasif Saifuddin Auvi (@auvipy) says:

    not working

  9. Robert M Koretsky says:

    I second Tim H’s comment of Nov 6 2015. Same errors on Dec 31 2015.

  10. Ed Overton says:

    I get systemctl: command not found
    I do a sudo apt-cache search systemctl, nothing comes back
    What is the replacement command for systemctl?
    I am running mint 17 which uses ubuntu 14.04

  11. jordinja says:

    I’ll add to Tim H and Robert M Koretsky’s comments – no update to the PPA for Wily (15.10)

    However, I ran this in terminal:
    sudo nano /etc/apt/sources.list

    and added the following lines:
    deb http://ppa.launchpad.net/jpsutton/cockpit/ubuntu vivid main
    deb-src http://ppa.launchpad.net/jpsutton/cockpit/ubuntu vivid main

    After that, ‘sudo apt-get install cockpit’ and ‘sudo systemctl start cockpit’ to start it, as per the intructions.

    Seems to work ok-ish – better with root enabled, and it helps if docker is installed too, of course.

  12. andrii furdyha says:

    Still gives after apt-get update
    W: Failed to fetch http://ppa.launchpad.net/jpsutton/cockpit/ubuntu/dists/wily/main/binary-amd64/Packages 404 Not Found

    W: Failed to fetch http://ppa.launchpad.net/jpsutton/cockpit/ubuntu/dists/wily/main/binary-i386/Packages 404 Not Found

    On CentOS i have 0.114 version. How i can update to 0.114 from ubuntu 15.10?

Leave a Reply

Your email address will not be published. Required fields are marked *