Hi Pascal,
Yes, that latest windows build from the FTP Server was built with a later VS
2012 version than the official one available on the open source web site and
thus does require the newer VS 2012 runtime redistributable, but the one
available on the web does still need the VS 2010 redistributable and thus is
correct ...
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 24 Jul 2014, at 07:33, Pascal Heus <pascal.h...@mtna.us> wrote:
> High:
> Finally got to look into this. When I simply replace our existing
> virtuoso-t.exe (3207) with the latest one you provided (3211), I get an
> MSVCR110.dll missing error which seem to be part if Visual Studio 2011 or
> 2012. This can be retrieved at
> http://www.microsoft.com/en-us/download/details.aspx?id=30679
> I'll try to this shortly distribution shortly.
> Did you recently upgrade to a more recent version os VS?
> Note that your web site page below points to the 2010 distribution:
> http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VOSUsageWindows
> best
> *P
>
> On 7/16/14, 1:10 PM, Hugh Williams wrote:
>> Hi Pascal,
>>
>> Unfortunately the log does not provide any information as to the cause of
>> the crash.
>>
>> The latest Windows open source Virtuoso 7.1 binary can be downloaded from:
>>
>> ftp://download.openlinksw.com/support/db/virtuoso-t.zip
>>
>> Simply run a checkpoint, shutdown Virtuoso, unzip and replace the current
>> virtuoso-t.exe file with this one and restart.
>>
>> The version details being:
>>
>> ..\bin\virtuoso -t -?
>> Virtuoso Open Source Edition (multi threaded)
>> Version 7.1.0.3211-threads as of Jul 10 2014
>> Compiled for Win64 (x86_64-generic-win-64)
>> Copyright (C) 1998-2014 OpenLink Software
>>
>> Can you update your database to this version and see if the problem persists
>> ...
>>
>> 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 14 Jul 2014, at 20:25, Pascal Heus <pascal.h...@mtna.us> wrote:
>>
>>> Hugh:
>>> Just to let you know our development server crashed as well today, so
>>> doesn't seem to be a server specific issue. Maybe something wrong we're
>>> doing in our java code?
>>> best
>>> *P
>>>
>>> On 7/13/14, 9:14 AM, Pascal Heus wrote:
>>>> Hugh:
>>>> We a few more crashes and turned tracing on. Don't see anything in
>>>> particular right before the server terminates but not sure either how to
>>>> interpret the trace either. Is there any particular trace option we should
>>>> turn on/off.
>>>> We do see lots of transactions rollback/restart/logout groups at the end
>>>> and throughout the log, along with numerous begin/commit/restart. I
>>>> noticed that the same transaction ID may appear multiple time.
>>>> I'll sent you shortly an email with a link to download the full log if
>>>> that helps. Any suggestion as to what we could do next?
>>>> Note that the puzzling part is that we experience this on the staging
>>>> server, our development server is stable. The differences I can think of
>>>> are two CPU instead of one, a bit more memory (8Gb vs 4Gb), and hosting
>>>> company.
>>>> best
>>>> *P
>>>>
>>>> ...
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1077 Rollback transact
>>>> 000000018D9B3990 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1077 Restart transact
>>>> 000000018D9B3990
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1077 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1078 Rollback transact
>>>> 0000000192DFA590 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1078 Restart transact
>>>> 0000000192DFA590
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1078 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1080 Rollback transact
>>>> 0000000192DF98C0 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1080 Restart transact
>>>> 0000000192DF98C0
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1080 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1081 Rollback transact
>>>> 00000001AD117060 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1081 Restart transact
>>>> 00000001AD117060
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1081 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1079 Rollback transact
>>>> 000000000DF5B990 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1079 Restart transact
>>>> 000000000DF5B990
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1079 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1082 Rollback transact
>>>> 00000001A46E7B30 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1082 Restart transact
>>>> 00000001A46E7B30
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1082 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1083 Rollback transact
>>>> 00000001D03793E0 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1083 Restart transact
>>>> 00000001D03793E0
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1083 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1084 Rollback transact
>>>> 000000018D9B43D0 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1084 Restart transact
>>>> 000000018D9B43D0
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1084 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1085 Rollback transact
>>>> 00000001D037B530 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1085 Restart transact
>>>> 00000001D037B530
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1085 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1086 Rollback transact
>>>> 000000000DF5C140 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1086 Restart transact
>>>> 000000000DF5C140
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1086 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1087 Rollback transact
>>>> 0000000193EBC460 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1087 Restart transact
>>>> 0000000193EBC460
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1087 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1089 Rollback transact
>>>> 0000000192DF8440 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1089 Restart transact
>>>> 0000000192DF8440
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1088 Rollback transact
>>>> 00000001D2141FB0 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1088 Restart transact
>>>> 00000001D2141FB0
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1089 logout
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1088 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1091 Rollback transact
>>>> 00000001D21408A0 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1091 Restart transact
>>>> 00000001D21408A0
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1091 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1090 Rollback transact
>>>> 000000016CD6ED40 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1090 Restart transact
>>>> 000000016CD6ED40
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1090 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1092 Rollback transact
>>>> 000000018F39AFD0 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1092 Restart transact
>>>> 000000018F39AFD0
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1092 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1093 Rollback transact
>>>> 00000001D037AD80 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1093 Restart transact
>>>> 00000001D037AD80
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1093 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1094 Rollback transact
>>>> 00000001D2142C80 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1094 Restart transact
>>>> 00000001D2142C80
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1094 logout
>>>> 18:04:10 LTRS_1 cms 172.23.79.34 1111:1095 Rollback transact
>>>> 00000001D0379900 0
>>>> 18:04:10 LTRS_2 cms 172.23.79.34 1111:1095 Restart transact
>>>> 00000001D0379900
>>>> 18:04:10 USER_0 cms 172.23.79.34 1111:1095 logout
>>>> *** SERVER TERMINATES AT 18:04:12 - WINDOWS EVENT LOG ***
>>>>
>>>> On 7/10/14, 11:48 AM, Hugh Williams wrote:
>>>>> Hi Pascal,
>>>>>
>>>>> The windows event log errors does not really tell much about why the
>>>>> server shutdown. The first place to look would be in the Virtuoso server
>>>>> log file "virtuoso.log" in the database directory where there maybe an
>>>>> indication as to why , if the problem occurred in Virtuoso itself. You
>>>>> can also enable more verbose logging of server activities to the virtuoso
>>>>> log file using the trace_on() function as detailed at:
>>>>>
>>>>> http://docs.openlinksw.com/virtuoso/fn_trace_on.html
>>>>>
>>>>> Although not it full tracing is turned on it will be very verbose and
>>>>> write a lot of information to the log, thus you should turn it off when
>>>>> done with the trace_off function ...
>>>>>
>>>>> 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 10 Jul 2014, at 09:20, Pascal Heus <pascal.h...@mtna.us> wrote:
>>>>>
>>>>>> We're running Virtusoso 07.10.3207 on a NT 2008 R2 cloud server with 8Gb
>>>>>> memory and two CPU cores.
>>>>>> The server stopped abruptly with following in the Windows event. Does
>>>>>> this indicate anything regarding the potential cause of the problem?
>>>>>> This is not the first time this happens. As mentioned in previous post,
>>>>>> it there a recommended way to log/debug/diagnose/monitor the server?
>>>>>> best
>>>>>> *P
>>>>>>
>>>>>> Faulting application name: virtuoso-t.exe, version: 7.0.1.3207, time
>>>>>> stamp: 0x53025c94
>>>>>> Faulting module name: virtuoso-t.exe, version: 7.0.1.3207, time
>>>>>> stamp: 0x53025c94
>>>>>> Exception code: 0xc0000005
>>>>>> Fault offset: 0x00000000004a721c
>>>>>> Faulting process id: 0xcd0
>>>>>> Faulting application start time: 0x01cf8ee1599f1056
>>>>>> Faulting application path: c:\software\virtuoso\bin\virtuoso-t.exe
>>>>>> Faulting module path: c:\software\virtuoso\bin\virtuoso-t.exe
>>>>>> Report Id: 8cd934d9-0558-11e4-a5af-005056bb67de
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Open source business process management suite built on Java and Eclipse
>>>>>> Turn processes into business applications with Bonita BPM Community
>>>>>> Edition
>>>>>> Quickly connect people, data, and systems into organized workflows
>>>>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>>>>>> http://p.sf.net/sfu/Bonitasoft
>>>>>> _______________________________________________
>>>>>> Virtuoso-users mailing list
>>>>>> Virtuoso-users@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>>
>>>> _______________________________________________
>>>> Virtuoso-users mailing list
>>>> Virtuoso-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>>
>>
>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
