i assume that your hostname is proper (li141-187.members.linode.com)
in /etc/apache2/httpd.conf change the line below,
NameVirtualHost *
to NameVirtualHost 109.74.194.187:80
& there can be a duplicate NameVirtualHost in your /etc/apache2/sites-enabled/webmin.1273066327.conf file in line 1. check if exists. if yes delete that line.
& edit the VirtualHost definition in /etc/apache2/sites-enabled/000-default file as follows.
<VirtualHost 109.74.194.187:80>
ServerName 109.74.194.187
.......
& edit the lines in /etc/apache2/sites-enabled/www.accontax.be as follows.
<VirtualHost 109.74.194.187:80>
ServerName accontax.be
ServerAlias www.accontax.be
.......
then apache2ctl restart
.
& and also check you bind's zone file for accontax.be, it should be like configuration below.
$ttl 38400
@ IN SOA accontax.be li141-187.members.linode.com. (
SOA_SERIAL_NUMBER
10800
3600
604800
38400 )
accontax.be. IN NS ns1.linode.com.
accontax.be. IN NS ns2.linode.com.
accontax.be. IN A 109.74.194.187
www.accontax.be. IN A 109.74.194.187
ftp.accontax.be. IN A 109.74.194.187
webmail.accontax.be. IN A 109.74.194.187
mail.accontax.be. IN A 109.74.194.187
accontax.be. IN MX 5 mail.accontax.be.
accontax.be. IN TXT "v=spf1 a mx a:accontax.be ip4:109.74.194.187 ?all"
there should be your own serial number for domain, intodns.com says so.
change SOA_SERIAL_NUMBER with your own above.
& this link will give you more information about DNS configuration.
http://www.intodns.com/accontax.be
it seems your are using webmin.
it's much better to do all these changes in webmin for you.
Check everything under "Servers" menu, in apache menu, check your module config is ok before changing anything. & also change startup command for apache in webmin to apache2ctl. do not allow webmin to use /etc/init.d/apache2 script.
Best Answer
you can double check that there are no process still running by do something like this: -
if apache2 is still running it will display results
kill them using
You will need to determine why the process went rouge from the
init
control. this can happen if you are running a very busy apache server, it will indicate that there is some performance related issue but the reason for this are many.check that there are no other web applications running that might be starting apache2 or even a mod version httpd manually with a /usr/sbin/apache2 -d statment. I doubt it though as you would more likely incur port locking issues especially if both using standard ports
of course what are the apache logs saying?