Ubuntu lds landscape howto and troubleshooting issues in the cloud

The need arose to add a few LDS landscape standalone servers to manage cloud instance inventory over a few clients in virtual private clouds. We identified the version we wanted to use and went 16.04 LTS. Your server needs a hostname that is resolvable either by public[cringe]/private dns or your host edits; The hostname will be used later when connecting to the server directly to add the first standalone user.

sudo apt-get update
sudo apt-get upgrade
sudo add-apt-repository ppa:landscape/16.06
sudo apt-get update
sudo apt-get install landscape-server-quickstart

Installed – updated – and using the quickstar….; whoa nelly it got messy..

On the first try we overlooked the fact that the cloud instance lacked sufficient memory and the installer made it only partially the way and left the system with an inconsistent postgresql install. Being installed all by its lonesome we can just purge and blow out postgres and landscape , landscape-server, landscape-server-quickstart and start over..

apt-get --purge remove postgresql\*
rm -r /etc/postgresql/
rm -r /etc/postgresql-common/
rm -r /var/lib/postgresql/
apt-get --purge remove landscape\*

Now Lets start over..

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install landscape-server-quickstart


If while trying to add the stand alone user on submit you are greeted with an apache htpasswd authorization window and have no entries in the .conf ?! you are not using the proper hostname – localhost and will not work it have to be the host name.
If while running the quickstart you see python errors your system could be out of date and you missed the upgrade call above

Cpanel Linux

Watch cpanel log files

From time to time you will need to examine logs looking to identify problems. An easy way to watch these files is with tail, grep, and zgrep. I will cover both and provide a few examples that I think will make it easier to quickly find issues on a Cpanel server without getting overly complicated.

Tail:  built to display the last few lines of files. Read the tail man page to find a full list of options.

Display file with (-f) follow then (-n)  the last 20 lines of the file. The second command displayed below will follow and display the three listed files, add more files by adding “-f -n /file” as many times as needed, or use a wildcard such as “*.com”. When using a wildcard care should be used as the number of sites you host fitting the wild card example could lead to a mess instead of usable info. Maybe this is a good time to set your window or scroll back to a few thousand lines plus. Also note when using tail and other programs that leave the file open for reading remove the follow option or your script will hang.

tail -f -n 20 /usr/local/apache/domlogs/
tail -f -n 20 /usr/local/apache/domlogs/ -f -n 20 /usr/local/apache/domlogs/ -f -n 20 /usr/local/apache/domlogs/


tail -f -n 20 /usr/local/apache/domlogs/*.com

Grep: Print lines matching a pattern

Grep: Provides an easy way to look into specific files or groups of files. Open file (-r) recursively looking for a specific pattern, only needed when looking into multiple files. Read the grep and zgrep man pages to find a full list of options.

Generic example:

grep "data-to-find" /file/location/

Cpanel example:

grep "data-to-find" /usr/local/apache/domlogs/

You can grep on multiple files at one.
Generic example

grep -r "data-to-find" /var/log/*

Cpanel example:

grep -r "data-to-find" /usr/local/apache/domlogs/*.com

zgrep: Allows you to look into archived log so no need to decompress before reading. The main different between grep and zgrep in this instance is that you do not need the (-r) option as zgrep recursively looks at multiple files if selected.

zgrep "data-to-find" /usr/local/apache/domlogs/

Assuming Cpanel is set to archive past logs.

zgrep "data-to-find" /home/username/logs/*.gz