|
Replies
:
7
-
Pages
:
1
-
Last Post
:
Mar 30, 2008 12:18 PM
by: Antonio Rocco
|
|
|
Posts:
13
From:
Netherlands
Registered:
Nov 25, 2007
|
|
|
|
Web Server not working any more
Posted:
Mar 28, 2008 1:31 PM
|
|
|
Could somebody help me out on this one. I changed the server name and setup DNS for it. And started SSL with a self signed certificate. Now the webserver is grayed out and when I want to adjust things it's not possible and there are pop up windows with the follwing text.
Uncaught Exception raised in the web client side plugin.
The log file showes:
3/28/08 9:24:20 PM com.apple.launchd[1] (org.apache.httpd96926) Exited with exit code: 1
3/28/08 9:24:20 PM com.apple.launchd[1] (org.apache.httpd) Throttling respawn: Will start in 10 seconds
3/28/08 9:24:30 PM org.apache.httpd96932 httpd: apr_sockaddr_info_get() failed for server.mvg.nl
3/28/08 9:24:30 PM org.apache.httpd96932 httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
The name of the server now is mvgdesign iso mvg.
Is there a easy way to solve this problem.
MacPro
Mac OS X (10.5.1)
|
|
Posts:
4,307
From:
UK
Registered:
Oct 31, 2005
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 28, 2008 2:56 PM
in response to: xmacmanx2
|
|
|
Hi
Changing the Server name from what was initially set is always going to have repercussions for pretty much any DNS dependent service.
You could try this. Stop the Web Service and issue this command on the server itself:
sudo changeip -checkhostname
It will probably tell you that the names don't match and you need to run the repair utility. In which case if the Server is Standalone issue this command:
sudo changeip - oldIPaddress newIPaddress oldHostname newHostname
In your case the only the hostname will change. By Hostname I mean the server's fully qualified hostname (FQDN). It should look something like this:
server.mydomain.com
When you run the above command you'll be prompted for the Administrator account name and password. Once the repair utility has run restart the server. On successful log in issue the checkhostname command again. If it tells you the names match there is nothing to change restart the web service and you should be OK thereafter.
If the Server is an Open Directory Master then the command takes this form:
sudo changeip /LDAPv3/127.0.0.1 oldIPaddress newIPaddress oldHostname newHostname
This time you will also be prompted for the Directory Administrator account name and password. Restart the server and follow the advice given above.
If DNS has become totally screwed to the point where changeip won't fix it then backup whatever data seems appropriate to you, stop any service that requires DNS as well as stopping the DNS Service itself (if hosted on the server). Take the time to sort out your DNS Service. Thoroughly test and qualify the service and make sure it resolves fully on the Forward and Reverse Lookup Zones and that the server has a valid Reverse Pointer for itself. Once you are happy with that restart your DNS dependent services one by one and hopefully you might be OK.
Hope this helps, Tony
|
|
Posts:
9,715
From:
San Jose, CA
Registered:
Mar 13, 2002
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 28, 2008 3:42 PM
in response to: xmacmanx2
|
|
|
The first thing to do would be to remove the server name from the virtual host.
If you're telling your web site it's server.mvg.nl and that hostname doesn't resolve to an IP address on this server, then your startup will fail.
This is very common when you're in a NAT network, where the hostname resolves to some public IP address and you're using port forwarding (or similar) to get traffic to your server on an internal network.
Mac OS X (10.5.2)
|
|
Posts:
13
From:
Netherlands
Registered:
Nov 25, 2007
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 29, 2008 12:24 PM
in response to: Antonio Rocco
|
|
|
Thx for the input Tony I will give it a go and see if it helps
MacPro
Mac OS X (10.5.1)
|
|
Posts:
13
From:
Netherlands
Registered:
Nov 25, 2007
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 29, 2008 12:25 PM
in response to: Camelot
|
|
|
Hello Camelot,
How would I remove the name from the virtual host. Everything in the server admin regarding to the Web settings is grayed out and the given error pops up when I click on it.
MacPro
Mac OS X (10.5.1)
|
|
Posts:
13
From:
Netherlands
Registered:
Nov 25, 2007
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 29, 2008 12:31 PM
in response to: Antonio Rocco
|
|
|
Hello Tony,
After checking the Server with your given command line: sudo changeip -checkhostname. It tells me the name and IP of the server but also tells me that the DNS name of the server is not available and I should repair DNS. Can I repair DNS from the terminal ???
This probably points in the direction of the problem I am having.
MacPro
Mac OS X (10.5.1)
|
|
Posts:
13
From:
Netherlands
Registered:
Nov 25, 2007
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 29, 2008 1:33 PM
in response to: Camelot
|
|
|
OK I ran the changeip command from the Terminal and thought it would also solve the DNS problem. It does not. The output is the following:
Primary address = 192.168.2.100
Current HostName = server.mvgdesign.nl
The DNS hostname is not available, please repair DNS and re-run this tool.
What would be the best way to repair DNS
MacPro
Mac OS X (10.5.1)
|
|
Posts:
4,307
From:
UK
Registered:
Oct 31, 2005
|
|
|
|
Re: Web Server not working any more
Posted:
Mar 30, 2008 12:18 PM
in response to: xmacmanx2
|
|
|
Hi
Have you read carefully the reply to your post? The reply gives instructions on how to run the repair utility via the command line. Checking the hostname will also result in a 'helpful' instruction on how to repair DNS using the command line.
If all you have done is changed the domain name and/or hostname but kept the IP address the same and if the Server is Standalone you should be able to repair DNS by issuing:
sudo changeip - 192.168.2.100 192.168.2.100 server.mvgdesign.nl server.mvgdesign.nl
Once you've keyed the above into terminal, press the enter key or the carriage return key. You'll be prompted for the Administrator account password, supply it and that should be it. Restart the server afterwards. Again read the reply to your original post.
Tony
|
|
|
