Re: [Virtuoso-users] Port 8890

2017-12-05 Thread Hugh Williams
Hi Jason,You can place static HTML pages in  the “vsp” file system directory which the “ServerRoot” in the “HTTP Server” of the  virtuoso.ini config file points to ie[HTTPServer]  ServerPort = 80  ServerRoot = ../vspOr you can create file system or DAV  Virtual DIrectories for hosting web server content as detailed in the docs at:	http://docs.openlinksw.com/virtuoso/webserver/Best RegardsRe: [Virtuoso-users] Port 8890Hugh WilliamsProfessional ServicesOpenLink Software, Inc.  //  http://www.openlinksw.com/Weblog   -- http://www.openlinksw.com/blogs/LinkedIn -- http://www.linkedin.com/company/openlink-software/Twitter  -- http://twitter.com/OpenLinkGoogle+  -- http://plus.google.com/100570109519069333827/Facebook -- http://www.facebook.com/OpenLinkSoftwareUniversal Data Access, Integration, and Management Technology ProvidersOn 5 Dec 2017, at 15:27, Jason Haag  wrote:I turned off Apache2 and it is running now. However, if I want to upload some static pages where do I do this? Via conductor? Or is there www path on the virtuoso server where HTML pages can be delivered. Previously, Apache was handling this.On Tue, Dec 5, 2017 at 8:30 AM, Jason Haag  wrote:Thanks for the tip! Looks like Apache is running and using port 80 after all.tcp6   0  0 :::80   :::*    LISTEN  1122/apache2   On Tue, Dec 5, 2017 at 6:54 AM, Hugh Williams  wrote:Hi Jason,As you are starting with sudo that would eliminate the possibility of it being permission issue preventing it from running on port 80 . Have you checked that something is not actually running on port 80 already with a  command like:    netstat -tulpn | grep :80as it would seem to me the port is in use.The URIQA DefaultHost would not be stopping it from starting on port 80 but in theory should be set to localhost:80 or just localhost or the hostname of the external domain you might want to publish Linked Data URI on on as detailed at:    http://docs.openlinksw.com/virtuoso/uriqainifile/Best RegardsHugh WilliamsProfessional ServicesOpenLink Software, Inc.  //  http://www.openlinksw.com/Weblog   -- http://www.openlinksw.com/blogs/LinkedIn -- http://www.linkedin.com/company/openlink-software/Twitter  -- http://twitter.com/OpenLinkGoogle+  -- http://plus.google.com/100570109519069333827/Facebook -- http://www.facebook.com/OpenLinkSoftwareUniversal Data Access, Integration, and Management Technology Providers
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


Re: [Virtuoso-users] Port 8890

2017-12-05 Thread Jason Haag
I turned off Apache2 and it is running now. However, if I want to upload
some static pages where do I do this? Via conductor? Or is there www path
on the virtuoso server where HTML pages can be delivered. Previously,
Apache was handling this.

On Tue, Dec 5, 2017 at 8:30 AM, Jason Haag  wrote:

> Thanks for the tip! Looks like Apache is running and using port 80 after
> all.
>
> tcp6   0  0 :::80   :::*
> LISTEN  1122/apache2
>
> On Tue, Dec 5, 2017 at 6:54 AM, Hugh Williams 
> wrote:
>
>> Hi Jason,
>>
>> As you are starting with sudo that would eliminate the possibility of it
>> being permission issue preventing it from running on port 80 . Have you
>> checked that something is not actually running on port 80 already with a
>> command like:
>>
>> netstat -tulpn | grep :80
>>
>> as it would seem to me the port is in use.
>>
>> The URIQA DefaultHost would not be stopping it from starting on port 80
>> but in theory should be set to localhost:80 or just localhost or the
>> hostname of the external domain you might want to publish Linked Data URI
>> on on as detailed at:
>>
>> http://docs.openlinksw.com/virtuoso/uriqainifile/
>>
>> Best Regards
>> Hugh Williams
>> Professional Services
>> OpenLink Software, Inc.  //  http://www.openlinksw.com/
>> Weblog   -- http://www.openlinksw.com/blogs/
>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>> Twitter  -- http://twitter.com/OpenLink
>> Google+  -- http://plus.google.com/100570109519069333827/
>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>> Universal Data Access, Integration, and Management Technology Providers
>>
>>
>>
>> > On 4 Dec 2017, at 23:29, Haag, Jason  wrote:
>> >
>> > Sorry for the late reply on this. I was on travel and just getting
>> > around to sending the log. I'm running the server as sudo (sudo
>> > virtuoso-t -f & +debug +configfile
>> > /usr/local/var/lib/virtuoso-opensource-7/db/virtuoso.ini ). Virtuoso
>> > is the only thing installed on this server. It's on an AWS and I
>> > checked all outbound traffic is allowed. HTTP is on port 80 for
>> > outbound traffic. I also have a custom TCP port set up for 8890. I
>> > suspect I don't need this if is allowed on 80 by simply chaning the
>> > "ServerPort" variable in the [HTTPServer] section of virtuoso.ini.
>> >
>> > I noticed there is also a "DefaultHost" variable in the [URIQA]
>> > section using localhost:8890. Does this need to be changed as well?
>> > Here's the log:
>> >
>> >
>> >Mon Dec 04 2017
>> > 23:18:26 INFO: { Loading plugin 1: Type `plain', file `wikiv' in
>> > `/usr/local/lib/virtuoso-opensource-7/hosting'
>> > 23:18:26 ERROR:   FAILED  plugin 1: Unable to locate file }
>> > 23:18:26 INFO: { Loading plugin 2: Type `plain', file `mediawiki' in
>> > `/usr/local/lib/virtuoso-opensource-7/hosting'
>> > 23:18:26 ERROR:   FAILED  plugin 2: Unable to locate file }
>> > 23:18:26 INFO: { Loading plugin 3: Type `plain', file `creolewiki' in
>> > `/usr/local/lib/virtuoso-opensource-7/hosting'
>> > 23:18:26 ERROR:   FAILED  plugin 3: Unable to locate file }
>> > 23:18:26 INFO: { Loading plugin 4: Type `plain', file `im' in
>> > `/usr/local/lib/virtuoso-opensource-7/hosting'
>> > 23:18:26 INFO:   IM version 0.6 from OpenLink Software
>> > 23:18:26 INFO:   Support functions for Image Magick 6.7.7
>> > 23:18:26 INFO:   SUCCESS plugin 4: loaded from
>> > /usr/local/lib/virtuoso-opensource-7/hosting/im.so }
>> > 23:18:26 INFO: OpenLink Virtuoso Universal Server
>> > 23:18:26 INFO: Version 07.20.3215-pthreads for Linux as of Feb  4 2016
>> > 23:18:26 INFO: uses parts of OpenSSL, PCRE, Html Tidy
>> > 23:18:26 INFO: Database version 3126
>> > 23:18:26 INFO: SQL Optimizer enabled (max 1000 layouts)
>> > 23:18:27 INFO: Compiler unit is timed at 0.000438 msec
>> > 23:18:28 INFO: Roll forward started
>> > 23:18:28 INFO: 3 transactions, 185 bytes replayed (100 %)
>> > 23:18:28 INFO: Roll forward complete
>> > 23:18:29 INFO: Checkpoint started
>> > 23:18:29 INFO: Checkpoint finished, log reused
>> > 23:18:29 ERROR: Failed HTTP listen at 80.
>> > 23:18:29 INFO: Server exiting
>> >
>> >
>> > -
>> > Jason Haag
>> > Advanced Distributed Learning (ADL) Initiative
>> > http://www.adlnet.gov
>> > Twitter: @ADL_Initiative
>> > Mobile: 850-471-1300
>> >
>> >
>> > On Wed, Nov 22, 2017 at 4:28 PM, Hugh Williams <
>> hwilli...@openlinksw.com> wrote:
>> >> Hi Jason,
>> >>
>> >> I trust you have checked there is not another web server running on
>> port 80
>> >> on the machine already and that the Virtuoso server is being run as
>> root (or
>> >> with root privileges) which is a requirement on a Unix based system to
>> run a
>> >> service on that special port.
>> >>
>> >> Failing that please provide the output of the virtuoso.log file so we
>> can
>> >> see the startup attempt and 

Re: [Virtuoso-users] Port 8890

2017-12-05 Thread Jason Haag
Thanks for the tip! Looks like Apache is running and using port 80 after
all.

tcp6   0  0 :::80   :::*LISTEN
1122/apache2

On Tue, Dec 5, 2017 at 6:54 AM, Hugh Williams 
wrote:

> Hi Jason,
>
> As you are starting with sudo that would eliminate the possibility of it
> being permission issue preventing it from running on port 80 . Have you
> checked that something is not actually running on port 80 already with a
> command like:
>
> netstat -tulpn | grep :80
>
> as it would seem to me the port is in use.
>
> The URIQA DefaultHost would not be stopping it from starting on port 80
> but in theory should be set to localhost:80 or just localhost or the
> hostname of the external domain you might want to publish Linked Data URI
> on on as detailed at:
>
> http://docs.openlinksw.com/virtuoso/uriqainifile/
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.  //  http://www.openlinksw.com/
> Weblog   -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter  -- http://twitter.com/OpenLink
> Google+  -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
>
>
> > On 4 Dec 2017, at 23:29, Haag, Jason  wrote:
> >
> > Sorry for the late reply on this. I was on travel and just getting
> > around to sending the log. I'm running the server as sudo (sudo
> > virtuoso-t -f & +debug +configfile
> > /usr/local/var/lib/virtuoso-opensource-7/db/virtuoso.ini ). Virtuoso
> > is the only thing installed on this server. It's on an AWS and I
> > checked all outbound traffic is allowed. HTTP is on port 80 for
> > outbound traffic. I also have a custom TCP port set up for 8890. I
> > suspect I don't need this if is allowed on 80 by simply chaning the
> > "ServerPort" variable in the [HTTPServer] section of virtuoso.ini.
> >
> > I noticed there is also a "DefaultHost" variable in the [URIQA]
> > section using localhost:8890. Does this need to be changed as well?
> > Here's the log:
> >
> >
> >Mon Dec 04 2017
> > 23:18:26 INFO: { Loading plugin 1: Type `plain', file `wikiv' in
> > `/usr/local/lib/virtuoso-opensource-7/hosting'
> > 23:18:26 ERROR:   FAILED  plugin 1: Unable to locate file }
> > 23:18:26 INFO: { Loading plugin 2: Type `plain', file `mediawiki' in
> > `/usr/local/lib/virtuoso-opensource-7/hosting'
> > 23:18:26 ERROR:   FAILED  plugin 2: Unable to locate file }
> > 23:18:26 INFO: { Loading plugin 3: Type `plain', file `creolewiki' in
> > `/usr/local/lib/virtuoso-opensource-7/hosting'
> > 23:18:26 ERROR:   FAILED  plugin 3: Unable to locate file }
> > 23:18:26 INFO: { Loading plugin 4: Type `plain', file `im' in
> > `/usr/local/lib/virtuoso-opensource-7/hosting'
> > 23:18:26 INFO:   IM version 0.6 from OpenLink Software
> > 23:18:26 INFO:   Support functions for Image Magick 6.7.7
> > 23:18:26 INFO:   SUCCESS plugin 4: loaded from
> > /usr/local/lib/virtuoso-opensource-7/hosting/im.so }
> > 23:18:26 INFO: OpenLink Virtuoso Universal Server
> > 23:18:26 INFO: Version 07.20.3215-pthreads for Linux as of Feb  4 2016
> > 23:18:26 INFO: uses parts of OpenSSL, PCRE, Html Tidy
> > 23:18:26 INFO: Database version 3126
> > 23:18:26 INFO: SQL Optimizer enabled (max 1000 layouts)
> > 23:18:27 INFO: Compiler unit is timed at 0.000438 msec
> > 23:18:28 INFO: Roll forward started
> > 23:18:28 INFO: 3 transactions, 185 bytes replayed (100 %)
> > 23:18:28 INFO: Roll forward complete
> > 23:18:29 INFO: Checkpoint started
> > 23:18:29 INFO: Checkpoint finished, log reused
> > 23:18:29 ERROR: Failed HTTP listen at 80.
> > 23:18:29 INFO: Server exiting
> >
> >
> > -
> > Jason Haag
> > Advanced Distributed Learning (ADL) Initiative
> > http://www.adlnet.gov
> > Twitter: @ADL_Initiative
> > Mobile: 850-471-1300
> >
> >
> > On Wed, Nov 22, 2017 at 4:28 PM, Hugh Williams 
> wrote:
> >> Hi Jason,
> >>
> >> I trust you have checked there is not another web server running on
> port 80
> >> on the machine already and that the Virtuoso server is being run as
> root (or
> >> with root privileges) which is a requirement on a Unix based system to
> run a
> >> service on that special port.
> >>
> >> Failing that please provide the output of the virtuoso.log file so we
> can
> >> see the startup attempt and also a copy of the virtuoso.ini for review
> ...
> >>
> >> Best Regards
> >> Hugh Williams
> >> Professional Services
> >> OpenLink Software, Inc.  //  http://www.openlinksw.com/
> >> Weblog   -- http://www.openlinksw.com/blogs/
> >> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> >> Twitter  -- http://twitter.com/OpenLink
> >> Google+  --