← Revision 1 as of 2004-11-04 10:22:44
Size: 3038
Comment:
|
← Revision 2 as of 2004-11-04 10:25:28 →
Size: 3038
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 20: | Line 20: |
* '''nocat''': ''You will notice a perl process that is the actual nocat service.'' | * '''nocat''': ''You will notice a perl process that is the actual NoCat service.'' |
Line 28: | Line 28: |
A good check to verify that the machine is operating correctly is to see when the last user authenticated using nocat. You can check this by looking at the entries in the file {{{/var/log/nocat.log}}}. In this file you will notice entries describing hosts entering and leaving the network. You can check the most recent timestamps of these entries to verify that the node is operating as expected. | A good check to verify that the machine is operating correctly is to see when the last user authenticated using NoCat. You can check this by looking at the entries in the file {{{/var/log/nocat.log}}}. In this file you will notice entries describing hosts entering and leaving the network. You can check the most recent timestamps of these entries to verify that the node is operating as expected. |
Line 50: | Line 50: |
A way to detect any configuration changes on a box is to use {{{aide}}}. Running aide will show you which files have been changes recently. This will give you a good idea about what is going on with the box. You can run {{{aide}}} as follows: | A way to detect any configuration changes on a box is to use {{{aide}}}. Running aide will show you which files have been changed recently. This will give you a good idea about what is going on with the box. You can run {{{aide}}} as follows: |
This page describes some general maintenance operations you can perform on an installed node.
Gaining administrative access to a node
You will need to create a ssh authentication key and give your public key to a member of the operations team. This key will be placed on the nodes for which you need administrative access. Take a look at the command ssh-keygen to create your keys.
Once you do have the rights to get onto a node you can simply connect to it using secure shell. For example:
ssh nodexyz.personaltelco.net
This will allow you to connect to the host as a normal user. You will also be provided with sudo rights, which basically gives you the right to execute commands as root. A command is executed with root priviledges as follows:
sudo <command>
Some of the commands described on this page requires you to have root priviledges. These are not explicitly indicated but if you get "permission denied" errors, try running the command using sudo.
Verify correct services
The PTP boxes run several services. Once you are logged into a node you should check if the following important services are running:
nocat: You will notice a perl process that is the actual NoCat service.
apache: The local web server. There may be more than one running - depending on how many people are connected.
dhcpd: The dhcp server.
snmpd: The SNMP deamon that allows us to monitor the box with Nagios.
named: This is the DNS server and there may be several named processes running.
Verify services are running correctly
A good check to verify that the machine is operating correctly is to see when the last user authenticated using NoCat. You can check this by looking at the entries in the file /var/log/nocat.log. In this file you will notice entries describing hosts entering and leaving the network. You can check the most recent timestamps of these entries to verify that the node is operating as expected.
Updating packages
It is a good idea to keep the nodes updates with recent packages. The commands used for this are:
% sudo apt-get clean % sudo apt-get update % sudo apt-get dist-upgrade % sudo apt-get clean
Updating configuration files
You can also update a node with the latest configuration files as created by the PTP operations team. You update the configuration files as follows:
% cd /home/web % sudo svn update
Change detection
A way to detect any configuration changes on a box is to use aide. Running aide will show you which files have been changed recently. This will give you a good idea about what is going on with the box. You can run aide as follows:
% sudo aide --update | less
Notify the ops team if you notice a lot of files in the list. The database that changed files are compared against may need updating, but they should decide this.