Thank you all for the help.
As instructed, I edited this file binsrc/virtuoso/viunix.c and increased the 
thread_initial value from 60000 to 140000.
The build was successful on the Mac (10.8.5).

Regards,
Eliza

From: Mark Thompson <mark9...@gmail.com<mailto:mark9...@gmail.com>>
Date: Tuesday, March 17, 2015 5:04 AM
To: Hugh Williams <hwilli...@openlinksw.com<mailto:hwilli...@openlinksw.com>>
Cc: Eliza Chan <elc2...@med.cornell.edu<mailto:elc2...@med.cornell.edu>>, 
"virtuoso-users@lists.sourceforge.net<mailto:virtuoso-users@lists.sourceforge.net>"
 
<virtuoso-users@lists.sourceforge.net<mailto:virtuoso-users@lists.sourceforge.net>>
Subject: Re: [Virtuoso-users] FAILED: Could not start Virtuoso Server within 
120 seconds

Hi,

I experienced the same issue as Eliza yesterday on MacOS 10.7.5 (Lion) when I 
git cloned VOS using "-b stable/7". However, when I dropped the -b parameter 
there was no problem.

Apparently in the later version thread_initial was already set to 140000.

Cheers,
Mark


On Tue, Mar 17, 2015 at 4:29 AM, Hugh Williams 
<hwilli...@openlinksw.com<mailto:hwilli...@openlinksw.com>> wrote:
Hi Eliza,

If you are running on Yosemite  then you probably need to increase your 
“thread_initial size as indicated below:


diff --git a/binsrc/virtuoso/viunix.c b/binsrc/virtuoso/viunix.c
index 4076248..bba1592 100644
--- a/binsrc/virtuoso/viunix.c
+++ b/binsrc/virtuoso/viunix.c
@@ -572,7 +572,7 @@ main (int argc, char **argv)

  process_exit_hook = viunix_terminate;

-  thread_initial (60000);
+  thread_initial (80000);
  if (!background_sem)
    background_sem = semaphore_allocate (0);

See, https://github.com/openlink/virtuoso-opensource/issues/277

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 13 Mar 2015, at 19:34, Eliza Chan 
<elc2...@med.cornell.edu<mailto:elc2...@med.cornell.edu>> wrote:

Hi Hugh,

Thanks for the suggestions.
Looks like it's a Mac specific issue.
When building on two Linux servers, it was successful.
But with the Mac, there may be some issues with one or more libraries.
Please see below the output from ./autogen.sh on the Mac:

Checking build environment ... Using aclocal (GNU automake) 1.14.1 Using 
autoconf (GNU Autoconf) 2.69 Using autoheader (GNU Autoconf) 2.69 Using 
automake (GNU automake) 1.14.1 Using libtoolize (GNU libtool) 2.4.4 Using bison 
(GNU Bison) 2.3 Using flex 2.5.35 Apple(flex-31) Using GNU Awk 3.1.8 Using GNU 
gperf 3.0.3 Using OpenSSL 0.9.8y 5 Feb 2013 Generating build scripts ... 
Running libtoolize ... libtoolize: putting auxiliary files in 
AC_CONFIG_AUX_DIR, 'binsrc/config'. libtoolize: copying file 
'binsrc/config/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 
'binsrc/config'. libtoolize: copying file 'binsrc/config/libtool.m4' 
libtoolize: copying file 'binsrc/config/ltoptions.m4' libtoolize: copying file 
'binsrc/config/ltsugar.m4' libtoolize: copying file 
'binsrc/config/ltversion.m4' libtoolize: copying file 
'binsrc/config/lt~obsolete.m4' Running aclocal ... Running autoheader ... 
Running automake ... Running autoconf ... Please check the INSTALL and README 
files for instructions to configure, build and install Virtuoso on your system. 
Certain build targets are only enabled in maintainer mode: ./configure 
--enable-maintainer-mode ... Bootstrap script completed successfully.

Thank you again.
Eliza




From: Hugh Williams <hwilli...@openlinksw.com<mailto:hwilli...@openlinksw.com>>
Date: Friday, March 6, 2015 5:31 PM
To: Eliza Chan <elc2...@med.cornell.edu<mailto:elc2...@med.cornell.edu>>
Cc: 
"virtuoso-users@lists.sourceforge.net<mailto:virtuoso-users@lists.sourceforge.net>"
 
<virtuoso-users@lists.sourceforge.net<mailto:virtuoso-users@lists.sourceforge.net>>
Subject: Re: [Virtuoso-users] FAILED: Could not start Virtuoso Server within 
120 seconds

Hi Eliza,

The default port number 1111 being is use is the most probably cause for this. 
You can check with "netstat -a | grep 1111” if it is in use still or change the 
port used wit the   --with-port(=NUMBER) configure option

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 6 Mar 2015, at 17:24, Eliza Chan 
<elc2...@med.cornell.edu<mailto:elc2...@med.cornell.edu>> wrote:

Hi,

I am trying to install the latest stable version of Virtuoso 7.2.

However, during the build process it threw the following error:

VAD Sticker vad_fs.xml creation...
VAD Sticker vad_dav.xml creation...
Starting Virtuoso server ...
The VDBMS server process terminated prematurely
after opening the database.
***FAILED: Could not start Virtuoso Server within 120 seconds
make[2]: *** [conductor_dav.vad] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

There was an earlier version of Virtuoso (7.1). But I have already stopped the 
instance and I made sure virtuoso-t was not running. I even deleted this folder 
/usr/local/virtuoso-opensource.

Did I miss out any other steps?

Thank you so much for the help.

Regards,
Eliza



------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. 
http://goparallel.sourceforge.net/_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. 
http://goparallel.sourceforge.net/_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to