Used DBs about papka24-core

[MaximBelov]

I set 4 DBs up. And then it was start without errors.

[VladyslavKurmaz]

@MaximBelov
Thanks!
...
Where can I define cassandra host name?
tried: localhost/127.0.0.1:9042
config.properties has no properties with cassandra substring in the name

[MaximBelov]

@VladyslavKurmaz
try

docker run -p 127.0.0.1:9042:9042 -i -t scylladb/scylla

base/server/src/main/resources/config.properties

scylla.path=localhost
scylla.keyspace=papka24
scylla.port=9042
scylla.enable=true

[VladyslavKurmaz]

@MaximBelov
With docker-compose use localhost is not a case.
As you can see scylla starts listening 9042 port, but server tries to connect to 127.0..0.1

scylla.path=scylla
scylla.keyspace=papka24
scylla.enable=true

Looks like server couldn't read local file with properties

[VladyslavKurmaz]

@MaximBelov
Looks like, server for some reasons couldn't read parameters from config.properties
Once I hardcode scylla docker-compose DNS name

     scyllaPath = "scylla";//Main.property.getProperty("scylla.path");

server starts working fine.

---

I run server using next command

java -jar /home/papka-24.jar

Can this cause an error during reading parameters from config.properties?

[VladyslavKurmaz]

I added simple output for one of the property and got next log:

com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: localhost/0:0:0:0:0:0:0:1:9042 (com.datastax.driver.core.exceptions.TransportException: [localhost/0:0:0:0:0:0:0:1:9042] Cannot connect), localhost/127.0.0.1:9042

INFO: Scanning for root resource and provider classes in the packages:
ua.papka24.server.api
server.domain: 95.85.56.80

I can assume that server tries to connect to the scylla before properties are read.

[MaximBelov]

1. Create postgress base papka24

2. Create user papka24

3. Replace in file server/src/main/resources/sql/CreateDB.sql
   GRANT SELECT ON ALL TABLES IN SCHEMA public TO papka24_ro;
   with
   GRANT SELECT ON ALL TABLES IN SCHEMA public TO papka24;

4. Import from CreateDB.sql

5. docker run -p 127.0.0.1:9042:9042 -i -t scylladb/scylla
   INFO 2017-06-27 21:47:48,896 [shard 0] storage_service - Starting listening for CQL clients on 172.17.0.2:9042...

6. server/src/main/resources/config.properties
   scylla.path=172.17.0.2
   Recompile jar-file
   gradle shadowJar;

7. Start your server
   example: java -jar papka-170624.jar

demo without error

[VladyslavKurmaz]

@MaximBelov
Thanks!.
Postgres db issue is fixed now.
...
I will raise scylla issue in separate ticket.
...
This issue can be closed.