Linode provides a convenient XML data feed that provides information about your CPU usage and Network Usage. The graph for the CPU Usage seems a little useless, but I have included it here as the XML feed provides the data.
You will need your linode account number to use the graphs, you can find this number by looking at the graphs provided to you in your Linode account management interface. The title of the graph will be “http://www.linode.com/ – yourhostname (linode12345) – CPU – …….”. You will need the text from inside the ( ) for your username ie linode12345.
Read more…
I recently wrote a three part article on using Autoyast to automate the installation of OpenSUSE machines. I this article I will show you how to setup a local software update repository as well.
Read more…
OpenSUSE and SLES (SuSE Linux Enterprise Server) both come with AutoYaST which is a very powerful tool that allows administrators to quickly and easily deploy servers that have an identical configuration for rapid server deployment.
In this three part series we will explore creating a repository for use with multiple systems, creating and customizing the AutoInstall file, and finally running through an install procedure.
Part 3 – Putting it all together and installing a server
In this part we will look at running through a machine install making use of our newly created repository and AutoInstall file.
Read more…
OpenSUSE and SLES (SuSE Linux Enterprise Server) both come with AutoYaST which is a very powerful tool that allows administrators to quickly and easily deploy servers that have an identical configuration for rapid server deployment.
In this three part series we will explore creating a repository for use with multiple systems, creating and customizing the AutoInstall file, and finally running through an install procedure.
Part 2 – Creating and Customizing the AutoInstall file
In this part we will look at creating an AutoInstall file for use with AutoYast.
Read more…
I thought I would write a quick post on this error, it is very simple to fix. If you receive the following error when importing a Cacti Template:
Error: XML: Hash version does not exist
This simply means the template was generated on a version of Cacti newer than the one you are importing to. Don’t despair, there are simple upgrade instructions on the cacti website.
Just make sure you make a full backup of your database and Cacti webfiles before attempting the upgrade (As a cautionary tale, if you installed cacti from a package you should first check to see if an updated package is available. Package installs can sometimes put the different files required in different places)