Nick,
Just wanted to let you know that I’m still seeing our “refresh
workspace” issue. The Amazon folks rebooted our instance on January 4th, I
believe, after looking at the AWS console.
Here are my notes from today:
XMLInsert2 didn't work.
>From the TBL log:
!ENTRY org.topbraid.core 1 0 2017-12-16 19:24:31.046
!MESSAGE Live v5.3.0.v20170419-1607R: started
(org.topbraidlive.tbl.TBLPersonality)
…interestingly, no mention of starting TBL on January 4th, so I may be wrong
about the AWS reboot.
...then after I tried calling XMLInsert2, the next entry is:
!ENTRY org.topbraid.eclipsex 2 0 2018-01-06 19:17:38.000
!MESSAGE WARN [http-nio-8080-exec-6] (E_Function.java:78) - URI
<http://epic/scripts/triplestoreOperations#XMLInsert2
<http://epic/scripts/triplestoreOperations#XMLInsert2>> >; has no registered
function factory
_____
I went online and did:
cd /var/lib/topbraid/ontologies
ubuntu@ip-172-30-0-42:/var/lib/topbraid/ontologies$ ll
total 32
drwxr-x--- 8 tomcat tomcat 4096 Dec 16 19:24 ./
drwxrwx--- 6 tomcat tomcat 4096 Jun 13 2017 ../
drwxr-x--- 3 tomcat tomcat 4096 Jun 6 2017 fonm.org/
drwxr-x--- 3 tomcat tomcat 4096 Dec 16 19:24 .metadata/
drwxr-x--- 9 tomcat tomcat 4096 Sep 25 20:27 SemanticModels/
drwxr-x--- 5 tomcat tomcat 4096 Dec 16 19:24 server.topbraidlive.org/
drwxr-x--- 6 tomcat tomcat 4096 Jun 7 2017 siemens.com/
drwxr-x--- 15 tomcat tomcat 4096 Dec 16 19:24 TopBraid/
ubuntu@ip-172-30-0-42:/var/lib/topbraid/ontologies$ find | grep tdb.lock
ubuntu@ip-172-30-0-42:/var/lib/topbraid/ontologies$
...so, no lock files.
Went to Admin console and clicked on "Refresh Workspace" and everything started
working again.
So it *may* be related to a reboot, or it may be due to something else.
Regardless, we would like to be able to programmatically refresh the workspace,
if you can tell us how.
- Steve
Steven R. Ray, Ph.D.
Distinguished Research Fellow
Carnegie Mellon University
NASA Research Park
Building 23 (MS 23-11)
P.O. Box 1
Moffett Field, CA 94305-0001
Email: [email protected]
Phone: (650) 587-3780
Cell: (202) 316-6481
Skype: steverayconsulting
cid:[email protected]
From: [email protected] [mailto:[email protected]]
On Behalf Of Nick Abston
Sent: Thursday, December 14, 2017 11:50 AM
To: [email protected]
Subject: Re: [topbraid-users] Programmatically refreshing the TBL workspace
Hi Steve,
Thanks for the update. I suspect you have gotten TDB locks in your workspace
from the abrupt restart of the server.
Shutdown TopBraid and go into your workspace and looking for these locks and
remove them
as with anything, backup your workspace first:
sudo cp -a /var/lib/topbraid/ontologies /var/lib/topbraid/ontologies-14Dec2017
now lets find and remove locks if there are any.
cd /var/lib/topbraid/ontologies
find | grep tdb.lock
if you have some, remove them like so
rm -rf $(find . -type f | grep tdb.lock)
once the tdb locks are removed, restart TopBraid
On Thu, Dec 14, 2017 at 12:46 PM, Steve Ray <[email protected]> wrote:
Nick,
No, we’re using the built-in triple store that comes with TBL. It’s
not relying on any other software package. We are accessing it via the endpoint
at :8080/tbl/tbl/sparql <http://epicdr.org:8080/tbl/tbl/sparql> . The odd
thing is that at least one of our SELECT queries worked fine, but others (doing
SELECTs or INSERTs) came back blank. Specifically, invoking the queries via a
web browser returned the headers of the SELECT, but no results. I didn’t
investigate more deeply because we wanted to get back to normal working mode,
which happened as soon as I hit the “Refresh Workspace” button on the console.
If it helps you to diagnose, the only thing I had done to cause
this was to create an Image of our AWS instance. I’m not sure exactly what
happens at the Amazon end, but it appears that doing that caused the instance
to reboot, because all our other processes also had to be restarted.
- Steve
Steven R. Ray, Ph.D.
Distinguished Research Fellow
Carnegie Mellon University
NASA Research Park
Building 23 (MS 23-11)
P.O. Box 1
Moffett Field, CA 94305-0001
Email: [email protected]
Phone: (650) 587-3780 <tel:(650)%20587-3780>
Cell: (202) 316-6481 <tel:(202)%20316-6481>
Skype: steverayconsulting
cid:[email protected]
From: [email protected] [mailto:[email protected]]
On Behalf Of Nick Abston
Sent: Thursday, December 14, 2017 8:00 AM
To: [email protected]
Subject: Re: [topbraid-users] Programmatically refreshing the TBL workspace
Hi Steve,
The 'refreshing' of the workspace is actually done on TopBraid startup. Was
there by any chance, a SDB database resource that was not available during this
time, that became available later (when you re-did the refresh manually)?
A programmatic way do refresh the workspace could be done. But if the server
is not right after a fresh startup, I would be more interested in what is
causing that, instead of triggering a refresh.
On Wed, Dec 13, 2017 at 8:21 PM, Steve Ray (CMU) <[email protected]> wrote:
Hi,
I recently was doing a routine image backup of our implementation
on AWS (which includes TBL). It seems that doing so caused the AWS instance to
reboot. Not a problem, I thought, because TBL started up again. However, it was
not behaving normally until I went to the TBL console and clicked “Refresh
Workspace”.
My question is, is there some way to programmatically refresh the workspace, so
that we can invoke that in a startup script?
- Steve
Steven R. Ray, Ph.D.
Distinguished Research Fellow
Carnegie Mellon University
NASA Research Park
Building 23 (MS 23-11)
P.O. Box 1
Moffett Field, CA 94305-0001
Email: [email protected]
Phone: (650) 587-3780 <tel:(650)%20587-3780>
Cell: (202) 316-6481 <tel:(202)%20316-6481>
Skype: steverayconsulting
cid:[email protected]
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
Nick Abston, Systems Administrator
TopQuadrant, Inc., <http://www.topquadrant.com/> www.topquadrant.com
@TopQuadrant <http://twitter.com/topquadrant> http://twitter.com/topquadrant
Office/Cell: [USA] (919)-809-9827 <tel:(919)%20809-9827>
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
www.avg.com
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
Nick Abston, Systems Administrator
TopQuadrant, Inc., <http://www.topquadrant.com/> www.topquadrant.com
@TopQuadrant <http://twitter.com/topquadrant> http://twitter.com/topquadrant
Office/Cell: [USA] (919)-809-9827
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
