Bennyland » server http://blog.bennyland.com this server is running in my bedroom - benny’s learning how to run a linux server Thu, 06 Jan 2011 16:41:43 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Serving ASP.NET pages in Apache on CentOS 5 http://blog.bennyland.com/2010/02/06/serving-asp-net-pages-in-apache-on-centos-5/ http://blog.bennyland.com/2010/02/06/serving-asp-net-pages-in-apache-on-centos-5/#comments Sat, 06 Feb 2010 18:59:32 +0000 benny http://blog.bennyland.com/?p=78 I'm starting to love ASP.NET and the ability to do everything in C# (I'm currently working on an internal silverlight app at work and creating a RESTful API is more fun in C#). Anyway, you can do a yum install mod_mono, but it's a pretty old version so I did some research and found a guide on building it yourself along with two other guides that were roughly the same, but not as good... (1, 2) and somehow ended up with a working server. This is a companion to that guide with more up to date versions of things. (it took me SEVERAL trial and error attempts to get things working :/ so hopefully i didn't miss any steps)

Let me preface this with the fact that if you're running one of the already supported OSs (debian or unbuntu for instance) you shouldn't follow this guide - instead you should just look on the mono website for information.

First thing I did was grab the most up-to-date mono and xst sources (i matched versions)

cd /tmp
wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.6.tar.bz2
wget http://ftp.novell.com/pub/mono/sources/mod_mono/mod_mono-2.6.tar.bz2
wget http://ftp.novell.com/pub/mono/sources/xsp/xsp-2.6.tar.bz2

Then unpack everything

tar -jxvf mono-2.6.tar.bz2
 tar -jxvf xsp-2.6.tar.bz2
 tar -jxvf mod_mono-2.6.tar.bz2

then build mono first (change anything on the ./configure line to your liking, I do suggest picking a place to put mono, letting it install wherever it wants to makes the rest of the process very painful!):

cd /tmp/mono-2.6
./configure --prefix=/opt/mono
make ; make install
echo export PKG_CONFIG_PATH=/opt/mono/lib/pkgconfig:$PKG_CONFIG_PATH>>~/.bash_profile
echo export PATH=/opt/mono/bin:$PATH>>~/.bash_profile
source ~/.bash_profile

after a bit you'll have mono installed :)

Now build xsp (i had to add pkgconfig to an environment variable to get it to work)

cd /tmp/xsp-2.6
./configure --prefix=/opt/mono
make ; make install

Finally build mod_mono, you'll probably need to tell it where apache's apr-config is... it took a while for me to find it.. heh

find / -iname apr*config
cd /tmp/mod_mono-2.6
./configure --prefix=/opt/mono --with-mono-prefix=/opt/mono --with-apr-config=/usr/bin/apr-1-config
make ; make install

you should now find mod_mono in your apache modules dir (in my case /usr/lib64/httpd/modules/)

ls /usr/lib64/httpd/modules/mod_mono*
17 Feb  5 22:54 /usr/lib64/httpd/modules/mod_mono.so -> mod_mono.so.0.0.0
145511 Feb  5 22:54 /usr/lib64/httpd/modules/mod_mono.so.0.0.0

the mod_mono install seems to have automatically created mod_mono.conf in my httpd/conf folder, but you may want to make sure it's there

vim /etc/httpd/conf/mod_mono.conf
# mod_mono.conf

# Achtung! This file may be overwritten
# Use 'include mod_mono.conf' from other configuration file
# to load mod_mono module.

<IfModule !mod_mono.c>
    LoadModule mono_module /usr/lib64/httpd/modules/mod_mono.so
</IfModule>

<IfModule mod_headers.c>
    Header set X-Powered-By "Mono"
</IfModule>

AddType application/x-asp-net .aspx
AddType application/x-asp-net .asmx
AddType application/x-asp-net .ashx
AddType application/x-asp-net .asax
AddType application/x-asp-net .ascx
AddType application/x-asp-net .soap
AddType application/x-asp-net .rem
AddType application/x-asp-net .axd
AddType application/x-asp-net .cs
AddType application/x-asp-net .vb
AddType application/x-asp-net .master
AddType application/x-asp-net .sitemap
AddType application/x-asp-net .resources
AddType application/x-asp-net .skin
AddType application/x-asp-net .browser
AddType application/x-asp-net .webinfo
AddType application/x-asp-net .resx
AddType application/x-asp-net .licx
AddType application/x-asp-net .csproj
AddType application/x-asp-net .vbproj
AddType application/x-asp-net .config
AddType application/x-asp-net .Config
AddType application/x-asp-net .dll
DirectoryIndex index.aspx
DirectoryIndex Default.aspx
DirectoryIndex default.aspx

Now, you need to get this to work with ISPConfig3, since if you've followed my other tutorials, that's what you have running things on the back end.

Modify your httpd.conf file to include mod_mono.conf. You want to do this at the very bottom, just before the NameVirtualHost directives (ISPConfig puts 3 directives at the very bottom of httpd.conf, you want to place this line just before them:

vim /etc/httpd/conf/httpd.conf
Include /etc/httpd/conf/mod_mono.conf
# this is where ISPConfig's stuff is, don't modify it, this comment is so you know where to put the line above the comment ;)
NameVirtualHost *:80
NameVirtualHost *:443
Include /etc/httpd/conf/sites-enabled/

now, restart apache

service httpd restart

and open up ISPConfig. go to sites > website > Select the website you want to add a mono enabled directory to, then click on the "Options" tab for that site. Enter the following into the Apache Directives (replace /var/www/path/to/the/web/folder with the path to that site's web folder)

MonoPath default "/opt/mono/lib/mono/2.0"
MonoServerPath default /opt/mono/bin/mod-mono-server
AddMonoApplications default "/test:/var/www/path/to/the/web/folder/test"
<location /test>
	MonoSetServerAlias default
	SetHandler mono
</location>

and finally restart httpd

service httpd restart

here's a test page, create it in your /var/www/path/to/the/web/folder/test directory and set the permissions to whatever the other site's permissions are, or apache.apache

<html>
<body>
<% Response.Write("Hello World!"); %>
</body>
</html>

now, once ISPConfig restarts apache (sometimes this is instant but i've seen it take up to 5 minutes) you'll see Hello World! displayed

]]> http://blog.bennyland.com/2010/02/06/serving-asp-net-pages-in-apache-on-centos-5/feed/ 3 Dynamic DNS support for WHM using ddclient http://blog.bennyland.com/2010/01/20/dynamic-dns-support-for-whm-using-ddclient/ http://blog.bennyland.com/2010/01/20/dynamic-dns-support-for-whm-using-ddclient/#comments Wed, 20 Jan 2010 23:11:01 +0000 benny http://blog.bennyland.com/?p=36 The server which I use to use to host my websites is now primarily used as my DNS and also a backup ftp space for this server to store backups (that way I don't have to buy some sort of tape backup thing). This is great except for the fact that my IP changes a couple of times a year. Up until now I was pushing requests from the webhost's DNS to dyndns and then to my home server running ddclient to update dyndns. Of course I could have paid around $30 a year per domain but I'm cheap.

So I modified ddclient so that it would update my host's DNS server. My host uses cpanel/WHM which luckily has a JSON API!

Here's how you can make the same modifications:

Install ddclient on your server - this is easy

yum install ddclient

You're also going to need some perl mods:

cpan

note: don't just copy and paste these 4 lines at once, some of the installs may have you type "yes" at some point. In the case of WWW::Mechanize, it forced me to type "yes" at least 4 times.

install JSON
install JSON::XS
install WWW::Mechanize
exit

Now, make sure you have version 3.7.3 of ddclient and then patch it with this ddclient 3.7.3 patch file

cd /tmp
wget http://blog.bennyland.com/wp-content/uploads/2010/01/ddclient.tar.gz
tar -zxvf ddclient.tar.gz
cd ddclient patch -p0 /usr/sbin/ddclient < ddclient.patch

Alternatively you can follow these directions:

vim /usr/sbin/ddclient
replace this:

require 5.004;
use strict;
use Getopt::Long;
use Sys::Hostname;
use IO::Socket;

with:

require 5.004;
use strict;
use Getopt::Long;
use Sys::Hostname;
use IO::Socket;
use WWW::Mechanize;
use JSON -support_by_pp;
replace this:

    'sitelutions' => {
        'updateable' => undef,
        'update'     => \&nic_sitelutions_update,
        'examples'   => \&nic_sitelutions_examples,
        'variables'  => merge(
                          { 'server'       => setv(T_FQDNP,  1, 0, 1, 'www.sitelutions.com',   undef)    },
                          { 'min-interval' => setv(T_DELAY,  0, 0, 1, 0, interval('5m')),},
                          $variables{'service-common-defaults'},
                        ),
    },

with:

    'sitelutions' => {
        'updateable' => undef,
        'update'     => \&nic_sitelutions_update,
        'examples'   => \&nic_sitelutions_examples,
        'variables'  => merge(
                          { 'server'       => setv(T_FQDNP,  1, 0, 1, 'www.sitelutions.com',   undef)    },
                          { 'min-interval' => setv(T_DELAY,  0, 0, 1, 0, interval('5m')),},
                          $variables{'service-common-defaults'},
                        ),
    },
    'whm' => {
        'updateable' => undef,
        'update'     => \&nic_whm_update,
        'examples'   => \&nic_whm_examples,
        'variables'  => merge(
                          { 'min-interval' => setv(T_DELAY,  0, 0, 1, interval('5m'), 0),},
                          $variables{'service-common-defaults'},
                        ),
    },
replace this:

sub split_by_comma {
    my $string = shift;

    return split /\s*[, ]\s*/, $string if defined $string;
    return ();
}

with:

sub split_by_comma {
    my $string = shift;

    return split /\s*[, ]\s*/, $string if defined $string;
    return ();
}
sub split_by_semi {
    my $string = shift;

    return split /\s*[; ]\s*/, $string if defined $string;
    return ();
}
and at the very bottom of the file replace this:

######################################################################
# vim: ai ts=4 sw=4 tw=78 :

with:

######################################################################

######################################################################
## nic_whm_examples
######################################################################
sub nic_whm_examples {
    return <<EoEXAMPLE;

o 'whm'

The 'whm' protocol is an API provided by the cpanel/WHM system.

Configuration variables applicable to the 'whm' protocol are:
  protocol=whm                                   ##
  server=ip.of.your.whm.login  ## defaults to sitelutions.com
  login=service-login          ## login name and password  registered with the service
  password=service-password    ## whm hash used for API (not your whm password)
  host.to.update;host.to.update. #

Example ${program}.conf file entries:
  ## single host update
  protocol=whm,                                                                                                                                 \\
  login=my-whm-login,                                                                                                           \\
  password=a-really-long-hash-string                                            \\
  myhost.com;myhost.com.;subdomain1.myhost.com.;subdomain2.myhost.com.,myotherhost.com;subdomain2.myotherhost.com.

EoEXAMPLE
}
######################################################################
## nic_whm_update
##
## written by Benny Raymond
##
######################################################################
sub nic_whm_update {
    debug("\nnic_whm_update -------------------");
                my $has_failed = 0;
    ## update each configured host
    foreach my $h (@_) {
        my @host_and_names = split_by_semi($h);
        my $host_to_update = $host_and_names[0];
        my %hosts_names;
        undef %hosts_names;
        my $i = 0;
                for (@host_and_names) {
                        if ($i==0) {
                                $i++;
                        } else {
                                $hosts_names{$_} = 1;
                        }
                }
        info("setting IP address to %s for %s", $ip, $host_to_update);
        verbose("UPDATE:","updating %s", $host_to_update);

        my $url_lookup;
        $url_lookup     = "http://$config{$h}{'server'}/json-api/dumpzone";
        $url_lookup .= "?domain=$host_to_update";

        my $api_output = json_whm_fetch($config{$h}{'login'},$config{$h}{'password'},$url_lookup);
        if (!defined($api_output) || !$api_output) {
            failed("updating %s: Could not connect to %s.", $h, $url_lookup);
            last;
        }
        if (json_whm_status($api_output) != 1)
        {
                failed("updating %s: %s - %s", $h, json_whm_status_msg($api_output),  $url_lookup);
        }

        # loop through names and update
        # get the A records
        my(@a_records) = @{(json_whm_a_records($api_output))};
        # and update the DNS table
        foreach (@a_records)
        {
                my(%record) = %{($_)};
                if ($hosts_names{$record{name}})
                {
                    if ($record{address} eq $ip)
                    {
                        success("updating '%s' - '%s': good: IP already set to %s", $host_to_update, $record{name}, $ip);
                    }
                    else
                    {
                                # update this line
                    #    print $record{Line} . ">" . $record{name};
                        $url_lookup     = "http://$config{$h}{'server'}/json-api/editzonerecord";
                        $url_lookup .= "?domain=$host_to_update";
                        $url_lookup .= "&Line=$record{Line}";
                        $url_lookup .= "&address=$ip";
                        my $api_update_output = json_whm_fetch($config{$h}{'login'},$config{$h}{'password'},$url_lookup);

                        if (json_whm_status($api_update_output) != 1)
                        {
                                failed("updating '%s' - '%s': %s %s", $host_to_update, $record{name}, json_whm_status_msg($api_update_output), $url_lookup);
                                $has_failed = 1;
                                $config{$h}{'status'} = 'failed';
                        } else {
                                success("updating '%s' - '%s': good: IP address set to %s", $host_to_update, $record{name}, $ip);
                        }
                     }
                } else {
                        # warning("name '%s' not found for host '%s'", $record{name}, $host_to_update);
                }
        }

        if ($has_failed == 0)
        {
          $config{$h}{'ip'}     = $ip;
          $config{$h}{'mtime'}  = $now;
          $config{$h}{'status'} = 'good';
        }
    }
}
sub json_whm_a_records
{
        my(%json) = %{(shift)};
        my(@records) = @{($json{result}[0]{record})};
        my(@a_records);
        foreach (@records)
        {
                my(%record) = %{($_)};
                if ($record{type} eq "A")
                {
                        push(@a_records, \%record);
                }
        }
        return \@a_records;
}
sub json_whm_status
{
        my(%json) = %{(shift)};
        my $status = $json{result}[0]{status};
        return $status;
}
sub json_whm_status_msg
{
        my(%json) = %{(shift)};
        my $status = $json{result}[0]{statusmsg};
        return $status;
}
sub json_whm_fetch
{
        my ($whm_api_login) = $_[0];
        my ($whm_api_key) = $_[1];
        my ($json_url) = $_[2];
        my $browser = WWW::Mechanize->new();
        my @args = (
                Authorization => "WHM " . $whm_api_login . ":" . $whm_api_key
        );
        my $json_text = "";
        eval{
                # download the json page:
                # print "Getting json $json_url\n";
                $browser->get( $json_url, @args );
                my $content = $browser->content();
                my $json = new JSON;

                # these are some nice json options to relax restrictions a bit:
                $json_text = $json->allow_nonref->utf8->relaxed->escape_slash->loose->allow_singlequote->allow_barekey->decode($content);
        };
        # catch crashes:
        if($@){
                print STDERR "[[JSON ERROR]] JSON parser crashed! $@\n";
                return "";
        } else {
                return $json_text;
        }
}

######################################################################
# vim: ai ts=4 sw=4 tw=78 :

Save and close ddclient

:wq

Now, edit ddclient.conf.

vim /etc/ddclient/ddclient.conf

Here's a simple version (note: you need to log into WHM and get your API key or none of this is going to work. You'll be entering your API key as one line - in WHM it is copied as several lines, just remove the carriage returns and enter it in one huge line as your password). Notice how my domain looks, it's my domain name, followed by a colon, followed by colon seperated hostnames to update - they all have periods after them!

daemon=300                              # check every 300 seconds
syslog=yes                              # log update msgs to syslog
mail=root                               # mail all msgs to root
mail-failure=root                       # mail failed update msgs to root
pid=/var/run/ddclient.pid               # record PID in file.
ssl=yes                                 # use ssl-support.  Works with
                                        # ssl-library
## To obtain an IP address from Web status page (using the proxy if defined)
use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address

##
## WHM
##
server=host.or.ip.of.your.whm.maybe.with.port,       \
protocol=whm,                   \
login=your-whm-username,                 \
password=crazy-long-api-key-as-one-long-line               \
hostname.com;hostname.com.;subdomain.hostname.com.

Save and close ddclient.conf

:wq

And finally run it and tell it to run every time the server reboots:

/sbin/chkconfig ddclient on
/sbin/service ddclient start
]]> http://blog.bennyland.com/2010/01/20/dynamic-dns-support-for-whm-using-ddclient/feed/ 0 Forwarding all mail to your ISP’s smtp server with postfix and CentOS 5.4 http://blog.bennyland.com/2010/01/18/forwarding-all-mail-to-your-isps-smtp-server-with-postfix-and-centos-5-4/ http://blog.bennyland.com/2010/01/18/forwarding-all-mail-to-your-isps-smtp-server-with-postfix-and-centos-5-4/#comments Mon, 18 Jan 2010 19:01:44 +0000 benny http://blog.bennyland.com/?p=13 I needed to forward all server mails to external email addresses and I had to use my ISP's smtp to do it. This is because everything is blocked by my ISP to combat spammers just making their own smtp server at home and then running it all hours of the day. To do this, you should have postfix installed and running already.

Setting up Postfix to use your ISP's smtp

Note: if your ISP requires authentication for smtp, you'll have to do some googleing.  If they don't (mine doesn't) then this will work fine for you.

vim /etc/postfix/main.cf

Next, you need to add the relayhost variable, you may have to enclose the domain in brackets, I didn't have to but I've read everywhere that you should:

relayhost = [your.isps.smtp.com]

Other items to potentially edit:

myhostname = your.host.name
mydomain = your.domain
myorigin = $mydomain
inet_interfaces = all
mydestination = $myhostname, localhost.$mydomain, localhost
unknown_local_recipient_reject_code = 550
relay_domains = $mydestination

Now, restart postfix

service postfix reload

Forwarding name@yourdomain.com to a real e-mail address

First things first, you need to edit main.cf

vim /etc/postfix/main.cf

Next, either add or edit the following lines. You can add as many domains as you want. If you followed the Perfect Server tutorial, you'll have all sorts of junk in these variables, just replace them.

virtual_alias_domains = yourdomain.com yourotherdomain.com.
virtual_alias_maps = hash:/etc/postfix/virtual

Now, edit the /etc/postfix/virtual file to add your forward rules:

vim /etc/postfix/virtual

forward all mail sent to *@yourdomain.com to your@email.com and name@yourotherdomain.com to your@email.com:

@yourdomain.com your@email.com
name@yourotherdomain.com your@email.com

Now, restart postfix

postmap /etc/postfix/virtual
service postfix reload
]]> http://blog.bennyland.com/2010/01/18/forwarding-all-mail-to-your-isps-smtp-server-with-postfix-and-centos-5-4/feed/ 0 Installing P5KPL-CM network drivers on CentOS 5.4 http://blog.bennyland.com/2010/01/18/installing-p5kpl-cm-network-drivers-on-centos-5-4/ http://blog.bennyland.com/2010/01/18/installing-p5kpl-cm-network-drivers-on-centos-5-4/#comments Mon, 18 Jan 2010 18:43:15 +0000 benny http://blog.bennyland.com/?p=9 Once CentOS was installed, the first thing I had to do to make the server useful was to build and install the network drivers for myASUS P5KPL-CM Motherboard.  Here's how to do it:

First, you're going to need the LinuxDrivers zip file.  You'll need to unzip and then unrar l1e-l2e-linux-v1.0.0.4.rar (found in the LinuxDrivers/L1e_Lan directory in the zip).  I had to do this on my Windows PC since I couldn't install unrar on the server (no network, remember?)

Once you're transfered the contents of l1e-l2e-linux-v1.0.0.4.rar to the server, follow these steps:

su -
cd /path/to/LinuxDrivers/src/
make clean
KBUILD_NOPEDANTIC=1 make clean
KBUILD_NOPEDANTIC=1 make
KBUILD_NOPEDANTIC=1 make install
cd /lib/modules/2.6.18-92.el5xen/kernel/drivers/net/atl1e/
mv atl1e.ko atl1e.ko.old
mv /path/to/LinuxDrivers/src/atl1e.ko atl1e.ko
insmod ./atl1e.ko

Once that is done, reboot your server and then configure your network however you need to. If all goes well, you should have eth0. I remember the first time I set this server up I attempted to install an incorrect driver that was on the installation disc. This caused me a lot of headaches when it came to installing the correct driver. This time I ignored network all together during setup and I was pleasantly surprised how easy it was to build and install the drivers this time.

]]> http://blog.bennyland.com/2010/01/18/installing-p5kpl-cm-network-drivers-on-centos-5-4/feed/ 0 Server Specs http://blog.bennyland.com/2010/01/18/server-specs/ http://blog.bennyland.com/2010/01/18/server-specs/#comments Mon, 18 Jan 2010 18:26:01 +0000 benny http://blog.bennyland.com/?p=6 This a post from the old setup... but the server is still the same.  There was a note about forgetting how I installed ReviewBoard, and how much of a pain in the ass it was - I havn't done that yet... OH BOY!

Here's the original post, minus the ReviewBoard comment:

Someone asked me last week what the specs of the server I put together were.  Here’s the low down

OS: CentOS 5.2 64 bit
Installed: Apache2 (pre installed), Subversion, Trac, ReviewBoard, WordPress

Server Specs (my main goals included low price and low noise):

]]> http://blog.bennyland.com/2010/01/18/server-specs/feed/ 0