Hi, Kurt --

On Mar 20, 2009, at 09:42 AM, Kurt J wrote:

sorry took me a while to try this - been busy at websci :-)

As an aside, check your networking setup by doing a double-lookup on
hostname:

# dig +short cognac.elec.qmul.ac.uk
138.37.xx.xx
# dig +short -x $(dig +short cognac.elec.qmul.ac.uk)

first command gives the ip address.  second command returns nothing.
is this right? what should be in host.conf?  sorry i'm a server admin
noob :-)


I don't believe the second return is correct.

hostname is a command -- when wrapped in the ` characters, it executes, and
its return gets substituted into the full command you're running.

Please copy and paste these three commands into your terminal session, so
they run on the Virtuoso host, exactly as shown --

   hostname
   dig +short `hostname`
   dig +short -x $(dig +short `hostname`)

For comparison, in my local environment, I get back --

   macted$ hostname
   dyn248.usnet.private
   macted$ dig +short `hostname`
   192.168.11.248
   macted$ dig +short -x $(dig +short `hostname`)
   dyn248.usnet.private.
   macted$


...



On Mar 20, 2009, at 09:56 AM, Kurt J wrote:

[Hugh] In your virtuoso.ini configuration file what is the value of the
"DefaultHost" param in the "[URIQA]" section as I do believe the
localhost:8890

[URIQA]
DynamicLocal                    = 1
DefaultHost                     = localhost:8890

tried changin this to hostname:80 and got the same old error.


localhost:8890 is only valid if the Web browser you're running can load
that URL -- including by local port forwarding -- which must be served up by the Virtuoso instance. This address generally only works when running
all Web clients directly on the Virtuoso host.

hostname:80 is only valid if that has been set up with port-forwarding
and/or vhost or similar settings, such that it reaches hostname:8890
(presuming 8890 is the Virtuoso instance's HTTP port).

Generally speaking, this should be set to the fully-qualified domain name (and Virtuoso HTTP port) of the Virtuoso host server -- but that presumes
that the host and port are generally addressable, not behind a firewall.

You'll need to set this to whatever <FQDN>:<port> can be used by both the
Virtuoso instance itself *and* your end client to reach the Virtuoso
listener on that port.

Hope that helps,

Ted





--
A: Yes.                      http://www.guckes.net/faq/attribution.html
| Q: Are you sure?
| | A: Because it reverses the logical flow of conversation.
| | | Q: Why is top posting frowned upon?

Ted Thibodeau, Jr.           //               voice +1-781-273-0900 x32
Evangelism & Support         //        mailto:tthibod...@openlinksw.com
OpenLink Software, Inc.      //              http://www.openlinksw.com/
                                 http://www.openlinksw.com/weblogs/uda/
OpenLink Blogs              http://www.openlinksw.com/weblogs/virtuoso/
                               http://www.openlinksw.com/blog/~kidehen/
    Universal Data Access and Virtual Database Technology Providers




Reply via email to