File not found exceptions when adding a db

Support
1

Hi. I’m receiving the following error after installing stardog from a package manager. Same error occured on AWS Linux and Ubuntu 16.

ERROR 2018-05-01 20:32:17,045 [stardog-user-15] com.stardog.http.server.undertow.ErrorHandling:writeError(180): Unexpected error on the server

com.complexible.stardog.StardogException: Problem while building index
at com.complexible.stardog.StardogKernel.bulkLoad(StardogKernel.java:1324) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.StardogKernel.createDatabase(StardogKernel.java:1451) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.protocols.http.server.AdminDatabaseService.createNewDatabase(AdminDatabaseService.java:433) ~[stardog-protocols-http-server-5.2.3.jar:?]
at com.stardog.http.server.undertow.jaxrs.ExtractRoutes.lambda$handleIt$5(ExtractRoutes.java:196) ~[stardog-protocols-http-server-5.2.3.jar:?]
at org.apache.shiro.subject.support.SubjectRunnable.doRun(SubjectRunnable.java:120) ~[shiro-core-1.2.3.jar:1.2.3]
at org.apache.shiro.subject.support.SubjectRunnable.run(SubjectRunnable.java:108) ~[shiro-core-1.2.3.jar:1.2.3]
at com.stardog.http.server.undertow.ErrorHandling.lambda$safeDispatch$1(ErrorHandling.java:71) ~[stardog-protocols-http-server-5.2.3.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_162]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_162]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162]
Caused by: com.complexible.stardog.index.IndexException: Problem while building index
at com.complexible.stardog.index.disk.ConcurrentDiskIndexLoader.build(ConcurrentDiskIndexLoader.java:167) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.index.disk.ConcurrentDiskIndexLoader.build(ConcurrentDiskIndexLoader.java:56) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.StardogKernel.bulkLoad(StardogKernel.java:1320) ~[stardog-5.2.3.jar:?]
… 9 more
Caused by: com.complexible.stardog.index.IndexException: /var/opt/stardog/{INDEX}/index.metadata (No such file or directory)
at com.complexible.stardog.index.disk.DiskIndex.(DiskIndex.java:65) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.index.disk.ConcurrentDiskIndexLoader.build(ConcurrentDiskIndexLoader.java:156) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.index.disk.ConcurrentDiskIndexLoader.build(ConcurrentDiskIndexLoader.java:56) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.StardogKernel.bulkLoad(StardogKernel.java:1320) ~[stardog-5.2.3.jar:?]
… 9 more
Caused by: java.io.FileNotFoundException: /var/opt/stardog/PolarisAlpha/index.metadata (No such file or directory)
at java.io.FileOutputStream.open0(Native Method) ~[?:1.8.0_162]
at java.io.FileOutputStream.open(FileOutputStream.java:270) ~[?:1.8.0_162]
at java.io.FileOutputStream.(FileOutputStream.java:213) ~[?:1.8.0_162]
at java.io.FileOutputStream.(FileOutputStream.java:162) ~[?:1.8.0_162]
at com.complexible.stardog.index.AbstractIndex.persistMetadata(AbstractIndex.java:745) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.index.disk.DiskIndex.(DiskIndex.java:62) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.index.disk.ConcurrentDiskIndexLoader.build(ConcurrentDiskIndexLoader.java:156) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.index.disk.ConcurrentDiskIndexLoader.build(ConcurrentDiskIndexLoader.java:56) ~[stardog-5.2.3.jar:?]
at com.complexible.stardog.StardogKernel.bulkLoad(StardogKernel.java:1320) ~[stardog-5.2.3.jar:?]
… 9 more

Any suggestions?

2

First thing that comes to my mind is to ask if /var/opt/stardog exists. I know it’s the STARDOG_HOME from the docs, so it’s worth making sure that the directory you’re telling Stardog to use for its home is there.

3

Hi Stephen,

Yes it does exist.It is owned by the stardog user too. Is there particular permissions the parent directories need? Here is the wierd thing too. If I create a db from the ui or the cli, there is no error, it occurs when using the java client.

I’ll keep digging and post updates. Thanks for the help,

Richard

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.