ServerBuddies Support Blog

How can I see all running processes from the shell ?

Use either:

Unpacking and configuring kvm components

Prerequisites

*kvm-release.tar.gz
*A VT capable Intel processor, or an SVM capable AMD processor

qemu prerequisites:

`zlib` libraries and headers
`SDL` libraries and headers
`alsa` libraries and headers (optional alsa support: disabled by default but can be enabled with –enable-alsa)
`gnutls` libraries and headers (optional VNC TLS support: enabled by default but can be disabled with –disable-vnc-tls)
kernel headers (on Fedora, the kernel-devel package)

On a debian etch system you can install the prerequisites with:

If you’re not running a patched kernel:

Downloads

http://www.linux-kvm.org/page/Downloads

Can’t login to DirectAdmin on port 2222

1. DirectAdmin might not be running or
2. You have a firewall blocking port 2222.

In case issue 2º is the one affecting you,

Check your /var/log/directadmin/error.log to check for any errors as to why it isn’t starting:

Common problems are:

1. Incorrect ethernet_dev set in the /usr/local/directadmin/conf/directadmin.conf file. guide
2. Invalid license, either due to wrong uid/lid, IP, or date. Try: Updating your DirectAdmin License manually
3. Binaries for a different operating system.

You can always try running DirectAdmin by hand (if it’s not already running) to see what the problem is.

Updating DirectAdmin Manually

If you need to update your copy of DirectAdmin manually, you can do so by running the following commands:

Where 123 and 1234 are your Client ID and License ID, respectively. Note that if you are running FreeBSD, you might need to add a \ before the ? character in the wget line. If there are errrors extracting the update.tar.gz file, then run:

to search for an error.

Apache won’t start nothing in the logs

Chance are, if apache isn’t starting and isn’t logging anything, the error_log is full preventing apache from starting. To double check that, run:

If any file is around 2-3 gig (or more), then chances are, that’s the problem.

The solution is to remove the logs, restart apache, and then implement preventative measures.

Get logrota to rotate daily.