Sites stopped working

[Toucan]

This morning all my test sites have stopped working. They have been working well since Monday.

The dns records seem to have resolved ok with wooodsidekennels.com using my ns1.badbison.co.uk

my own dns records haven't changed and point to 93.97.188.1.

If I type the ip address directly into a browser it displays the default apache page.

The only change I've noticed this morning is the mail server has now resolved and delivering all mail. Also there was a warning message on ispconfig advising of an update required. To deal with this from the command line I typed:
apt-get update
apt-get upgrade
and it performed the commands.
I then rebooted the server from command line.

The warning message is now gone from ispconfig but it's stil not serving the sites up.

Can anyone suggest what might have happened? Do I need to restart any services or something?

The server was setup using the karmic perfect guide.

[falko]

Are there any errors in Apache's error log?

[Toucan]

[Wed Dec 16 20:41:11 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Wed Dec 16 20:42:26 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Wed Dec 16 20:45:32 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Wed Dec 16 20:50:50 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 09:32:01 2009] [notice] caught SIGTERM, shutting down
[Thu Dec 17 09:33:02 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Thu Dec 17 09:33:04 2009] [notice] Apache/2.2.12 (Ubuntu) PHP/5.2.10-2ubuntu6.3 with Suhosin-Patch mod_ssl/2.2.12 OpenSSL/0.9.8g configured -- resuming normal operations
[Thu Dec 17 09:46:37 2009] [notice] caught SIGTERM, shutting down
[Thu Dec 17 09:47:36 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Thu Dec 17 09:47:38 2009] [notice] Apache/2.2.12 (Ubuntu) PHP/5.2.10-2ubuntu6.3 with Suhosin-Patch mod_ssl/2.2.12 OpenSSL/0.9.8g configured -- resuming normal operations
[Thu Dec 17 10:44:34 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 10:58:50 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 12:51:58 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 13:53:41 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 14:50:54 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 15:27:25 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 15:55:12 2009] [notice] caught SIGTERM, shutting down
[Thu Dec 17 15:56:12 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
Use of uninitialized value $DBI_DUMP in alarm at /usr/local/ispconfig/server/scripts/vlogger line 531, <CONF> line 1.
202,1
[Thu Dec 17 15:56:12 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
Use of uninitialized value $DBI_DUMP in alarm at /usr/local/ispconfig/server/scripts/vlogger line 531, <CONF> line 1.
[Thu Dec 17 15:56:13 2009] [notice] Apache/2.2.12 (Ubuntu) PHP/5.2.10-2ubuntu6.3 with Suhosin-Patch mod_ssl/2.2.12 OpenSSL/0.9.8g configured -- resuming normal operations
[Thu Dec 17 16:05:32 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 16:36:56 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 18:26:08 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 19:56:01 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 20:27:16 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Thu Dec 17 22:52:36 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Fri Dec 18 01:46:48 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Fri Dec 18 02:37:41 2009] [error] [client 221.195.73.68] script '/usr/local/ispconfig/interface/web/prx2.php' not found or unable to stat
[Fri Dec 18 08:25:00 2009] [notice] caught SIGTERM, shutting down
[Fri Dec 18 08:25:59 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Fri Dec 18 08:26:01 2009] [notice] Apache/2.2.12 (Ubuntu) PHP/5.2.10-2ubuntu6.3 with Suhosin-Patch mod_ssl/2.2.12 OpenSSL/0.9.8g configured -- resuming normal operations
[Fri Dec 18 15:44:38 2009] [notice] caught SIGTERM, shutting down
[Fri Dec 18 15:45:38 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
Use of uninitialized value $DBI_DUMP in alarm at /usr/local/ispconfig/server/scripts/vlogger line 531, <CONF> line 1.
[Fri Dec 18 15:45:41 2009] [notice] Apache/2.2.12 (Ubuntu) PHP/5.2.10-2ubuntu6.3 with Suhosin-Patch mod_ssl/2.2.12 OpenSSL/0.9.8g configured -- resuming normal operations
[Fri Dec 18 20:38:16 2009] [notice] caught SIGTERM, shutting down
[Fri Dec 18 20:39:16 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)

I got a bad feeling about all those logs!
Help

[falko]

Can you post one of the vhost configurations that isn't working?
What's the output of

ifconfig

?

[Toucan]

Thanks for the help. I took a different approach Friday - started again on debian lenny, transferred a domain to schlundtech to use as a glue record and no2 ns server left it over the weekend to propogate and this morning it's all started working fine!

All test websites can be accessed from different Internet areas. Hooray.

I've not tried it yet but i'm confident the mail services work too. What I would like to do is set up pop or imap mail services so any poiinters there would be good. I'm guessing it'll be just a case of setting up dns records?

If anyone knows of any howtos to cover that it would be appreciated.

Thanks

[falko]

Did you follow this tutorial? http://www.howtoforge.com/perfect-se...nny-ispconfig3
Then POP3 and IMAP are already running. All you have to do is use a hostname/domain or IP address in your email client that points to the server.

[Toucan]

yes I did and oh wow! It does work! I just used the IP address.

What should I use as the outgoing server details though? The IP address doesn't seem to work and neither does mail.mydomain.com

Also I'm having a little trouble with incoming mails. Some get through fine and others just never seem to appear.

[falko]

Originally Posted by Toucan

What should I use as the outgoing server details though? The IP address doesn't seem to work and neither does mail.mydomain.com

The same address that you use for POP3/IMAP. Make sure that port 25 is accessible from the outside.

Originally Posted by Toucan

Also I'm having a little trouble with incoming mails. Some get through fine and others just never seem to appear.

Any errors in your mail log?

[Toucan]

Thanks. The ip address as the outgoing host worked perfect.

I'll put this all into a beginners tutorial for others so you don't keep getting the same questions rephrased by people.

There were no errors in the mail error log but there were warnings in that log that I'll paste at the end.

There is something I haven't managed to get my head around regarding secondary name servers. I appreciate that I've told the schundtech registry to use my ip glued to a domain as the primary server. And it also knows the ns10.schlundtech.de is the secondary. And I understand that in my dns records I've added the ip of ns10 to allow export of the records.

Does this mean that my ns will contact the schlundtech one and give it the details, or does ns10 somehow know to contact my ns to get the records?

I'm nearly done With beginners questions (i think)

Dec 20 14:29:46 badbuntu postfix/smtpd[26623]: warning: 189.34.170.147: hostname bd22aa93.virtua.com.br verification failed: Name or service not known
Dec 20 17:10:41 badbuntu postfix/smtpd[28966]: warning: 187.11.152.222: hostname 187-11-152-222.dsl.telesp.net.br verification failed: Name or service not known
Dec 21 01:31:26 badbuntu postfix/smtpd[21179]: warning: 200.59.62.225: hostname adsl225.infracom.com.ar verification failed: Name or service not known
Dec 21 09:50:02 badbuntu postfix/smtpd[9630]: warning: 89.120.127.209: hostname adsl89-120-127-209.romtelecom.net verification failed: Name or service not known
Dec 21 15:39:00 badbuntu postfix/smtpd[14690]: warning: 95.231.50.201: hostname host201-50-static.231-95-b.business.telecomitalia.it verification failed: Name or service not known
Dec 21 18:27:19 badbuntu postfix/smtpd[17287]: warning: 110.136.246.75: hostname 75.subnet110-136-246.speedy.telkom.net.id verification failed: Name or service not known
Dec 21 19:26:57 badbuntu postfix/smtpd[18144]: warning: 201.240.183.68: hostname client-201.240.183.68.speedy.net.pe verification failed: Name or service not known
Dec 22 04:47:02 badbuntu postfix/smtpd[11222]: warning: 222.78.76.254: hostname 254.76.78.222.board.ly.fj.dynamic.163data.com.cn verification failed: Name or service not known
Dec 22 06:18:35 badbuntu postfix/smtpd[12584]: warning: 113.161.0.10: address not listed for hostname localhost
Dec 22 07:57:47 badbuntu postfix/smtpd[27649]: warning: 123.19.237.142: address not listed for hostname localhost
Dec 22 08:22:20 badbuntu postfix/smtpd[28021]: warning: 190.192.128.186: hostname 186-128-192-190.cab.prima.net.ar verification failed: Name or service not known
Dec 22 09:49:25 badbuntu postfix/smtpd[29260]: warning: 118.68.184.204: hostname adsl-dynamic-pool-xxx.hcm.fpt.vn verification failed: Name or service not known
Dec 22 13:09:32 badbuntu postfix/smtpd[32154]: warning: 122.160.96.227: hostname ABTS-North-Static-227.96.160.122.airtelbroadband.in verification failed: Name or service not known
Dec 22 16:37:02 badbuntu postfix/smtpd[2766]: warning: 95.19.18.207: hostname 207.18.19.95.dynamic.jazztel.es verification failed: Name or service not known
Dec 22 16:37:04 badbuntu postfix/smtpd[2768]: warning: 95.19.18.207: hostname 207.18.19.95.dynamic.jazztel.es verification failed: Name or service not known
Dec 22 18:08:08 badbuntu postfix/smtpd[4218]: warning: 190.48.250.16: hostname 190-48-250-16.speedy.com.ar verification failed: Name or service not known
Dec 22 18:25:15 badbuntu postfix/smtpd[4483]: warning: 212.118.142.76: hostname 212-118-142-76.saudi.net.sa verification failed: Name or service not known
Dec 22 20:08:40 badbuntu postfix/smtpd[3683]: warning: 190.247.219.54: hostname 54-219-247-190.fibertel.com.ar verification failed: Name or service not known
Dec 22 21:59:23 badbuntu postfix/smtpd[5276]: warning: 187.41.67.211: hostname 18741067211.user.veloxzone.com.br verification failed: Name or service not known
Dec 22 23:06:46 badbuntu postfix/smtpd[23644]: warning: 190.186.48.204: hostname dynamic-ip-adsl-190.186.48.204.cotas.com.bo verification failed: Name or service not known
Dec 22 23:42:00 badbuntu postfix/smtpd[24153]: warning: 189.83.193.111: hostname 18983193111.user.veloxzone.com.br verification failed: Name or service not known
Dec 23 00:18:55 badbuntu postfix/smtpd[24684]: warning: 189.121.119.236: hostname bd7977ec.virtua.com.br verification failed: Name or service not known
Dec 23 01:32:07 badbuntu postfix/smtpd[25847]: warning: 201.245.247.233: hostname adsl201-245247233.dyn.etb.net.co verification failed: Name or service not known
Dec 23 02:26:57 badbuntu postfix/smtpd[26650]: warning: 122.164.162.100: hostname ABTS-TN-dynamic-100.162.164.122.airtelbroadband.in verification failed: Name or service not known
Dec 23 08:27:47 badbuntu postfix/smtpd[13178]: warning: 125.164.199.47: hostname 47.subnet125-164-199.speedy.telkom.net.id verification failed: Name or service not known
Dec 23 09:15:13 badbuntu postfix/smtpd[13878]: warning: 89.122.156.84: hostname adsl89-122-156-84.romtelecom.net verification failed: Name or service not known
Dec 23 11:36:35 badbuntu postfix/smtpd[15916]: warning: 123.16.127.246: address not listed for hostname localhost
Dec 23 12:26:24 badbuntu postfix/smtpd[16656]: warning: 92.241.94.50: hostname host-92-241-94-50-customer.wanex.net verification failed: Name or service not known
Dec 23 12:31:10 badbuntu postfix/smtpd[16731]: warning: 95.87.198.86: hostname mladost-95-87-198-86.net1.bg verification failed: Name or service not known
Dec 23 13:07:26 badbuntu postfix/smtpd[17266]: warning: 85.100.126.247: hostname dsl.static85100126247.ttnet.net.tr verification failed: Name or service not known
Dec 23 14:01:15 badbuntu postfix/smtpd[18032]: warning: 212.125.23.99: hostname 99.23.125.212.dsl.static.turk.net verification failed: Name or service not known
Dec 23 14:05:35 badbuntu postfix/smtpd[18113]: warning: 77.78.67.74: hostname assigned-77-78-67-074.casablanca.cz verification failed: Name or service not known
Dec 23 14:31:44 badbuntu postfix/smtpd[18504]: warning: 115.48.149.17: hostname hn.kd.ny.adsl verification failed: Name or service not known
Dec 23 15:32:59 badbuntu postfix/smtpd[19389]: warning: 187.14.147.13: hostname 18714147013.user.veloxzone.com.br verification failed: Name or service not known

[falko]

Originally Posted by Toucan

There is something I haven't managed to get my head around regarding secondary name servers. I appreciate that I've told the schundtech registry to use my ip glued to a domain as the primary server. And it also knows the ns10.schlundtech.de is the secondary. And I understand that in my dns records I've added the ip of ns10 to allow export of the records.

Does this mean that my ns will contact the schlundtech one and give it the details, or does ns10 somehow know to contact my ns to get the records?

The secondary DNS will contact the primary one and get the records.

It seems as if there's something wrong with your name resolution. What's in /etc/resolv.conf? Are these valid nameservers?