Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

object_database created outside witness_node_data_dir on fresh install #257

Closed
theoreticalbts opened this issue Aug 20, 2015 · 3 comments
Closed

Comments

@theoreticalbts
Copy link
Contributor

  • Install brand new witness_node
  • object_database is created in the wrong place
  • Subsequent run doesn't recognize it
@abitmore
Copy link
Contributor

https://bitsharestalk.org/index.php/topic,18751.msg243241.html#msg243241

the object_database and genesis.json file location (if it is provided in the config.ini and not the --genesis-json cmd line arg) are relative to the folder from which the witness_node binary is executed.

See also https://bitsharestalk.org/index.php/topic,18751.msg243253.html#msg243253

@abitmore
Copy link
Contributor

My steps for reproducing this issue:

  • build in /app/bts/bts2-pre1/
  • cd /app/bts/scripts/
  • gdb
  • (gdb) file /app/bts/bts2-pre1/pragrams/witness_node/witness_node
  • (gdb) set args --data-dir=/app/bts/witness_node_data_dir-pre1/
  • (gdb) run

A object_database folder is created under /app/bts/scripts/.

@vikramrajkumar
Copy link
Contributor

This issue was moved to bitshares/bitshares-core#69

pmconrad pushed a commit to pmconrad/graphene that referenced this issue May 24, 2017
…ransactions-memory-leak

Fix clear_expired_transactions memory leak cryptonomex#256
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants