• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problem with hostname resolution
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with hostname resolution


  • Subject: Re: Problem with hostname resolution
  • From: Jonathan Rochkind <email@hidden>
  • Date: Mon, 26 Jan 2004 11:21:41 -0600

In the past, I've had problems with my WO server machine, that I think were somehow due to the fact that it had multiple host names. Note, it does NOT have multiple IP addresses/network interfaces. It has a single IP, but through DNS aliasing or whatever mechanism (I'm not in charge of that) there were several FQDNs that corresponded to that IP.

That _shouldn't_ logically cause any problem at all, but somehow it appeared to.

What I ended up doing: First I tried using the -WOHost argument (to wotaskd, to JavaMonitor, to all my applications: Karl Hsu said only to wotaskd should be neccesary, and everything else should kind of inherit it from wotaskd). This didn't seem to neccesarily work either.

At first my 'host' in JavaMonitor was set up with one of the DNS names that wasn't the 'main' one for the IP. By 'main' one, I mean the DNS name that you'll get from reverse lookup of the numerical IP. So, i changed my configuration so I added the host in JavaMonitor under this 'main' DNS name. I also left the -WOHost argument to wotaskd, with the value being this 'main' name again. I'm not sure the WOHost argument was really neccesary, I think it was using the 'main' DNS hostname in JavaMonitor that finally dis-confused it.

[I also forget exactly _how_ you set a launch argument to wotaskd. I remember it was confusing and not really documented.]

I don't know if this is related to the problem you are having or not, but that's my experience, maybe it'll be helpful to you.

--Jonathan

At 8:47 PM -0500 1/22/04, Christopher Payne wrote:
An addendum to my earlier message: if I try to connect from a Web browser on the server, it works. Connecting from any other machine causes the error.

My forward and reverse DNS entries seem to be accurate.

My HOSTNAME entry is set properly in /etc/hostconfig.

I also run into this problem when trying to access JavaMonitor, so it doesn't seem to be something specific to my WO app. With JavaMonitor, either hostname or IP work on the server, but only IP will work from another machine; using the hostname generates the "An Internal Server Error Occurred" message.

-CTP

On Jan 22, 2004, at 6:58 PM, Christopher Payne wrote:

Greetings. I'm deploying a WO application on OS X Server 10.3, and I've run into a problem with DNS name resolution. If I try to connect to my WO application using the server hostname, I get an error message: "An Internal Server Error Has Occurred." If, on the other hand, I try to connect using the IP address, the connection goes through.

It seems to me I've seen mention of this problem somewhere before, but I've been unable to find either the problem description or, more importantly, the solution. Can anyone tell me how to get this fixed?

-CTP
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Problem with hostname resolution (From: Christopher Payne <email@hidden>)
 >Re: Problem with hostname resolution (From: Christopher Payne <email@hidden>)

  • Prev by Date: Objective-C with WebObjects?
  • Next by Date: RE: Should we upgrade from 4.5.1 to 5.2(.2)
  • Previous by thread: Re: Problem with hostname resolution
  • Next by thread: Problem with scheduled shutdown
  • Index(es):
    • Date
    • Thread