TiesNetwork / ties.db

Ties.DB
GNU Lesser General Public License v3.0
60 stars 11 forks source link

Error? #16

Closed rpelaez closed 6 years ago

rpelaez commented 6 years ago

When I execute tiesdb it raises this exception: CompilerOracle: inline org/apache/cassandra/utils/vint/VIntCoding.encodeVInt (JI)[B Exception in thread "TiesServiceDaemon:TEST" java.lang.RuntimeException: Can't create TiesDB schema at network.tiesdb.schema.impl.ethereum.TiesSchemaFactoryImpl.createSchema(TiesSchemaFactoryImpl.java:42) at network.tiesdb.service.impl.elassandra.TiesServiceImpl.initTiesSchema(TiesServiceImpl.java:103) at network.tiesdb.service.impl.elassandra.TiesServiceImpl.initInternal(TiesServiceImpl.java:94) at network.tiesdb.service.impl.elassandra.TiesServiceDaemonImpl.run(TiesServiceDaemonImpl.java:53) at java.lang.Thread.run(Thread.java:748) Caused by: network.tiesdb.exception.TiesConfigurationException: Invalid contract address: contract binary missmatch at network.tiesdb.schema.impl.ethereum.impl.TiesSchemaEthereum.(TiesSchemaEthereum.java:50) at network.tiesdb.schema.impl.ethereum.TiesSchemaFactoryImpl.createSchema(TiesSchemaFactoryImpl.java:40) ... 4 more

rpelaez commented 6 years ago

The last line of log show this: 2018-08-12 13:56:09,436 INFO [elasticsearch[127.0.0.1][clusterService#updateTask][T#1]] CassandraGatewayService.java:81 clusterStateProcessed [127.0.0.1] cassandra ring block released

ya-enot commented 6 years ago

Could you please check settings at conf/tiesdb.yaml in the node installation directory. This error could be caused by improper configuration of your node. The configuration of "schema: !!SchemaEthereum" should be: endpointUrl: http://localhost:8545 contractAddress: 0x22D1B55eBb5BcD17084C3C9D690056875263fEc1

rpelaez commented 6 years ago

This is the config:

TiesDB config YAML

saveSettingsOnStop: true

config: TEST: !!ServiceTiesDB schema: !!SchemaEthereum endpointUrl: http://localhost:8545 contractAddress: 0x22D1B55eBb5BcD17084C3C9D690056875263fEc1 transports:

ya-enot commented 6 years ago

Please check that your local ethereum client (e.g. geth) serving the 8545 port is connected to Rinkeby network.

rpelaez commented 6 years ago

captura de pantalla 2018-08-13 a las 18 29 04

Yes it's in the 8545 port. How I can test the Server? There is a UI? Regards

ya-enot commented 6 years ago

Is your geth connected to Rinkeby network? We are working on creation of the db testing tools. You can use https://uiproto.tiesdb.com for schema management.

ya-enot commented 6 years ago

Your geth client should be synced up to at least 1683229 rinkeby block for succesfull launch. And should be kept syncing during operation.

rpelaez commented 6 years ago

OK! while I'm synchronizing I'm trying the UI, very nice work guys! Many thanks!

One question, how I can set a String field default value? captura de pantalla 2018-08-25 a las 19 41 30

ya-enot commented 6 years ago

It seems like a bug in geth operating in "fast" mode. You can run geth in "light" mode (it takes approx. 30 minutes for synchronization) or "full" mode, install it from an appropriate bundle, run it in docker or compile it from sources. For running geth in light mode use this command:

geth --rinkeby --datadir .rinkeby --cache 512 --rpc --rpcaddr 127.0.0.1 --syncmode "light"