quasar.jar

[Nigel David]

I downloaded quasar-repl-assembly-18.7.4.jar from the Quasar release page. I put it in my home directory then ran this command:pointed to it with this command: java -jar ~/quasar-web-assembly-18.7.4.jar --content-path public 

But I get the following error:  Invalid or corrupt jarfile /home/ubuntu/quasar-web-assembly-18.7.4.jar

Am I missing something?

[do...@slamdata.com]

We've seen this error message when people are using Java 7. Quasar requires Java 8 to run.

[Nigel David]

Thanks for the tip. Helped eliminate that error.

But now when I run java -jar ~/quasar-web-assembly-18.7.4.jar --content-path public, I get the following error: /home/ubuntu/.config/quasar/quasar-config.json

Do I need to create this file myself?

[do...@slamdata.com]

Since you are not passing in a qausar-config.json file, it should just use the default values for things. You will see a warning that the file doesn't exist, but quasar should still start up and be listening on port 20223.

You stated you get an error, but your post just shows the path to the config file. What is the exact message of the error?

You can create a basic quasar-config.json file with the following contents:

{
  "server": {
    "port": 20223
  }
}

Save that as /home/ubuntu/.config/quasar/quasar-config.json and you shouldn't see the warning any more.

[Nigel David]

That was in fact the exact message of the error. "Error: /home/ubuntu/.config/quasar/quasar-config.json"

But I cannot cd into that directory "/.config" or anything.

[Nigel David]

Oh yeah, and I didn't get the message Server started listening on port 20223 Press Enter to stop.

[do...@slamdata.com]

Thanks for the update. You mentioned that you could not cd into /.config. I'm assuming you meant that you could not cd into ~/.config. The way it's written you would be looking for the directory off the root of the file system. Using the ~ means to look for the directory in your home folder.

If you do the following:

cd ~
ls -alh

You will see a list of all of the file/directories in your home directory.

If you don't see a .config directory there you will have to create the directory with

mkdir -p ~/.config/quasar

This will create both the .config and quasar subdirectories, and then you can create the quasar-config.json file under that directory based off the sample I provided earlier.

[Nigel David]

When I run cd ~/.config I get permission denied. 

I do see the folder with ls -alh

I think the problem is that it is owned by root.

I'll try changing privileges for my user and redo it, and get some support from our IT guy on this.

Cheers, 

[do...@slamdata.com]

Having the folder owned by root would definitely cause issues. Running chown on the .config file and all contents underneath it using your user name will allow you to be able to access that folder.

[Nigel David]

without sudo, I get a bunch of errors:

ubuntu@volttroncentral:~/slamdata$ java -jar ~/quasar-web-assembly-18.7.4.jar --content-path public

Read web config from /home/ubuntu/.config/quasar/quasar-config.json

Using metastore: jdbc:h2:file:/home/ubuntu/.config/quasar/quasar-metastore.db

log4j:WARN No appenders could be found for logger (com.zaxxer.hikari.HikariConfig).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

org.h2.message.DbException: Log file error: "/home/ubuntu/.config/quasar/quasar-metastore.db.trace.db", cause: "java.io.FileNotFoundException: /home/ubuntu/.config/quasar/quasar-metastore.db.trace.db (Permission denied)" [90034-192]

org.h2.message.DbException: Log file error: "/home/ubuntu/.config/quasar/quasar-metastore.db.trace.db", cause: "java.io.FileNotFoundException: /home/ubuntu/.config/quasar/quasar-metastore.db.trace.db (Permission denied)" [90034-192]

        at org.h2.message.DbException.get(DbException.java:168)

        at org.h2.message.TraceSystem.logWritingError(TraceSystem.java:286)

        at org.h2.message.TraceSystem.openWriter(TraceSystem.java:307)

        at org.h2.message.TraceSystem.writeFile(TraceSystem.java:255)

        at org.h2.message.TraceSystem.write(TraceSystem.java:239)

        at org.h2.message.Trace.error(Trace.java:182)

        at org.h2.engine.Database.setBackgroundException(Database.java:2037)

        at org.h2.mvstore.db.MVTableEngine$1.uncaughtException(MVTableEngine.java:94)

        at org.h2.mvstore.MVStore.panic(MVStore.java:375)

        at org.h2.mvstore.MVStore.<init>(MVStore.java:358)

        at org.h2.mvstore.MVStore$Builder.open(MVStore.java:2893)

        at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:154)

        at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:99)

        at org.h2.engine.Database.getPageStore(Database.java:2463)

        at org.h2.engine.Database.open(Database.java:692)

        at org.h2.engine.Database.openDatabase(Database.java:270)

        at org.h2.engine.Database.<init>(Database.java:264)

        at org.h2.engine.Engine.openSession(Engine.java:64)

        at org.h2.engine.Engine.openSession(Engine.java:176)

        at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)

        at org.h2.engine.Engine.createSession(Engine.java:137)

        at org.h2.engine.Engine.createSession(Engine.java:27)

        at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:349)

        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:118)

        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:102)

        at org.h2.Driver.connect(Driver.java:72)

        at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:95)

        at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:101)

        at com.zaxxer.hikari.pool.BaseHikariPool.addConnection(BaseHikariPool.java:444)

        at com.zaxxer.hikari.pool.BaseHikariPool.initializeConnections(BaseHikariPool.java:548)

        at com.zaxxer.hikari.pool.BaseHikariPool.<init>(BaseHikariPool.java:172)

        at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:60)

        at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:48)

        at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:104)

        at doobie.contrib.hikari.hikaritransactor$HikariTransactor$$anonfun$2.apply(HikariTransactor.scala:14)

        at doobie.contrib.hikari.hikaritransactor$HikariTransactor$$anonfun$2.apply(HikariTransactor.scala:14)

        at scalaz.concurrent.Task$$anonfun$delay$1.apply(Task.scala:339)

        at scalaz.concurrent.Task$$anonfun$delay$1.apply(Task.scala:339)

        at scalaz.concurrent.Task$$anonfun$suspend$1$$anonfun$7.apply(Task.scala:347)

        at scalaz.concurrent.Task$$anonfun$suspend$1$$anonfun$7.apply(Task.scala:347)

        at scalaz.concurrent.Task$.Try(Task.scala:457)

        at scalaz.concurrent.Task$$anonfun$suspend$1.apply(Task.scala:347)

        at scalaz.concurrent.Task$$anonfun$suspend$1.apply(Task.scala:347)

        at scalaz.concurrent.Future.step(Future.scala:119)

        at scalaz.concurrent.Future.unsafePerformListen(Future.scala:75)

        at scalaz.concurrent.Future.unsafePerformAsync(Future.scala:159)

        at scalaz.concurrent.Future.unsafePerformSync(Future.scala:184)

        at scalaz.concurrent.Task.unsafePerformSync(Task.scala:99)

        at quasar.server.Server$.main(Server.scala:147)

        at quasar.server.Server.main(Server.scala)

Caused by: org.h2.jdbc.JdbcSQLException: Log file error: "/home/ubuntu/.config/quasar/quasar-metastore.db.trace.db", cause: "java.io.FileNotFoundException: /home/ubuntu/.config/quasar/quasar-metastore.db.trace.db (Permission denied)" [90034-192]

        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)

        ... 50 more

Caused by: java.io.FileNotFoundException: /home/ubuntu/.config/quasar/quasar-metastore.db.trace.db (Permission denied)

        at java.io.FileOutputStream.open0(Native Method)

        at java.io.FileOutputStream.open(FileOutputStream.java:270)

        at java.io.FileOutputStream.<init>(FileOutputStream.java:213)

        at java.io.FileOutputStream.<init>(FileOutputStream.java:101)

        at org.h2.store.fs.FilePathDisk.newOutputStream(FilePathDisk.java:290)

        at org.h2.store.fs.FileUtils.newOutputStream(FileUtils.java:233)

        at org.h2.message.TraceSystem.openWriter(TraceSystem.java:303)

        ... 47 more

Error: While verifying MetaStore schema: Exception during pool initialization. Is the metastore database running?

If I use sudo, I get less:

ubuntu@volttroncentral:~/slamdata$ sudo java -jar ~/quasar-web-assembly-18.7.4.jar --content-path public

Configuration file '/root/.config/quasar/quasar-config.json' not found, using default configuration.

Using metastore: jdbc:h2:file:/root/.config/quasar/quasar-metastore.db

log4j:WARN No appenders could be found for logger (com.zaxxer.hikari.HikariConfig).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Error: MetaStore requires initialization, try running the 'initUpdateMetaStore' command.

In the docs it does say anything about using sudo, or running the "initUpdateMetaStore" command.

is there still hope?

[Nigel David]

update:

I hadn't changed ownership of the contents. When I did this, I ran the command java -jar...   without sudo and got the second trace I shared. Now wondering about initializing Metastore.

Thanks

[do...@slamdata.com]

You can initialize the metastore with the following command:

 java -jar ~/quasar-web-assembly-18.7.4.jar initUpdateMetaStore

This will run and drop you back out to the command line. At that point you should be able to run your normal command again to start SlamData up:

 

java -jar ~/quasar-web-assembly-18.7.4.jar --content-path public

[Nigel David]

Thanks!

I was able to get a better output:

ubuntu@volttroncentral:~/slamdata$ java -jar ~/quasar-web-assembly-18.7.4.jar --content-path public -c ~/.config/quasar/quasar-config.json

Read web config from /home/ubuntu/.config/quasar/quasar-config.json

Using metastore: jdbc:h2:file:/home/ubuntu/.config/quasar/quasar-metastore.db

log4j:WARN No appenders could be found for logger (com.zaxxer.hikari.HikariConfig).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Server started listening on port 20223

Press Enter to stop.

So that's good.

But this is running on a cloud-server, not my local machine. When I go to the public ip/20220/slamdata, the page cannot be found.

Is there some configuration I need to do for this?

[do...@slamdata.com]

I'm not sure if what you entered was a typo or not, but you want to go to publicip:20223/slamdata. Also since you're on a cloud machine, make sure that you have either whitelisted your local machine's IP address (best practice) so you can access SlamData on that machine and port, or open that port to the world (which I don't recommend). At this point in time it's configuration of the server that you're running on and not configuration of the SlamData service itself.

[Chao Fang]

Hi, I was able to compile from source code and run the 4.2.2 version on my 12GB memory desktop without any issue. Now I just did exactly same steps on my another machine which only has 3GB memory, when I enter 127.0.0.1:20223, I got white page with no any error prompt. (it should show icons, let me mount mongodb...) based your online doc, my desktop should meet your minimum hardware requirements... any idea?

[Chao Fang]

never mind, issue was gone by installing released 4.2.2. (not pre-released version)