User`s guide

Troubleshooting 196
Nmap run completed -- 1 IP address (1 host up) scanned
in 169 seconds
to check if any ports are open that should normally be closed.
That could however be a problem to remove a rootkit from a Container and make sure it is
100% removed. If you're not sure, create a new Container for that customer and migrate his/her
sites and mail there.
 Check the /var/log/ directory on the server to find out what is happening on the system.
There are a number of log files that are maintained by the system and Parallels Server Bare
Metal (the boot.log, messages, etc.), but other services and programs may also put
their own log files here depending on your distribution of Linux and the services and
applications that you are running. For example, there may be logs associated with running a
mail server (the maillog file), automatic tasks (the cron file), and others. However, the
first place to look into when you are troubleshooting is the /var/log/messages log file.
It contains the boot messages when the system came up as well as other status messages as
the system runs. Errors with I/O, networking, and other general system errors are reported in
this file. So, we recommend that you read to the messages log file first and then proceed
with the other files from the /var/log/ directory.
 Subscribe to bug tracking lists. You should keep track of new public DoS tools or remote
exploits for the software and install them into Containers or at servers.
 When using iptables, there is a simple rule for Chains usage to help protect both the
server and its Containers:
 use INPUT, OUTPUT to filter packets that come in/out the server
 use FORWARD to filter packets that are designated for Containers