On 04/09/13 09:08, Danny Ayers wrote:
I /may/ have a use case for using a specific IP address. Running on
OpenShift hosting, as far as I can tell the only available IP is provided
by an environment variable. This can be supplied in jetty.xml, as in [1] :
...
<New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
<Set name="port"><Env name="OPENSHIFT_DIY_PORT" default="8080"/></Set>
<Set name="host"><Env name="OPENSHIFT_DIY_IP" default="127.0.0.1"/></Set>
...
There is --port for the command line.
By default, Fuseki listens on all interfaces for the port -- does that
cause a specific problem on OpenShift?
We run with port blocking (on AWS) with only 22, 80, and 443 open (and
some specific point-to-point for monitoring: e.g. ganglia and nagios).
Fuseki listens on 3030 and hence only hears localhost. We don't use
--locaalhost; it's not needed.
Without this, command-line startup from the latest Fuseki release gets a
Permission denied (I've not tried the --localhost option yet, svn is
downloading as I type).
Is the error message illuminating?
You can download a build -
https://repository.apache.org/content/groups/snapshots/org/apache/jena/jena-fuseki/1.0.0-SNAPSHOT/
but if you are on a slowish link by being half way up a mountain,
then a grab of SVN, maven caching and local builds off increments may
save you bandwidth.
What I'm aiming for is essentially the same as the Fuseki-behind-Apache
setup, though using some node.js stuff rather than Apache (with Fuseki
running on port 15000 to hide it).
Cheers,
Danny.
Andy
[1] https://github.com/semfact/openshift-fuseki/blob/master/conf/jetty.xml
On 8 August 2013 21:41, Andy Seaborne (JIRA) <[email protected]> wrote:
[
https://issues.apache.org/jira/browse/JENA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733888#comment-13733888]
Andy Seaborne commented on JENA-499:
------------------------------------
http://jena.staging.apache.org/ is already updated.
Presumably, you have both v4 and v6 running.
The Fuseki code sets host "localhost" to name the interface -- that should
return some 127.?.?.? block address (for IPv4) or ::1 (IPv6). I don't see
ATM how to do both.
What's your machine setup? What does "dig localhost" / "nslookup
localhost" return?
fuseki-server command does not accept --host argument
-----------------------------------------------------
Key: JENA-499
URL: https://issues.apache.org/jira/browse/JENA-499
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 0.2.7
Environment: Mac OS 10.7.5
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11G63)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)
Reporter: Nicholas Humfrey
Assignee: Andy Seaborne
Fix For: Fuseki 0.2.8
The Fuseki command line help describes at the {{--host}} argument is
supported:
{noformat}
fuseki-server --help
fuseki [--config=FILE] [--mem|--desc=AssemblerFile|--file=FILE] [--port
PORT] [--host HOST] /DatasetPathName
{noformat}
But when trying to use it I get an error:
{noformat}
~ $ fuseki-server --port 8080 --host 127.0.0.1 --mem /data
Unknown argument: host
{noformat}
The {{--host}} argument is also documented here:
http://jena.apache.org/documentation/serving_data/#running-a-fuseki-server
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
