starting with new API.. questions and issues

[noglance]

new bin files was compiled for Debian fine: #1

but now there is one more issue.

I'm starting bytecoind and 2 walletd instances like this:
./bytecoind --priority-node-address=45.76.29.96:8080
and:
walletd --wallet-file=/path/.wallet --wallet-password=<password> --walletd-bind-address=<server_ip>:<port_to_connect_to_apr_rpc_from_other_server_to_query_transactions>

and it's not working as before..

new man:

_...Usage:
  walletd [options] --wallet-file=<file> | --export-blocks=<directory>
  walletd --help | -h
  walletd --version | -v

Options:
  --wallet-file=<file>                 Path to wallet file to open.
  --wallet-password=<password>         DEPRECATED. Password to decrypt wallet file. If not specified, will prompt user.
  --generate-wallet                    Create wallet file with new random keys. Must be used with --wallet-file option.
  --set-password=<password>            DEPRECATED. Reencrypt wallet file with the new password.
  --set-password                       Prompt user for new password and reencrypt wallet file.

  --allow-local-ip                     Allow local ip add to peer list, mostly in debug purposes.
  --export-blocks=<directory>          Export blockchain into specified directory as blocks.bin and blockindexes.bin, then exit. This overwrites existing files.
  --export-view-only=<file>            Export view-only version of wallet file with the same password, then exit.
  --hide-my-port                       DEPRECATED. Do not announce yourself as peer list candidate. Use --p2p-external-port=0 instead.
  --testnet                            Configure for testnet.
  --p2p-bind-address=<ip:port>         Interface and port for P2P network protocol [default: 0.0.0.0:8080].
  --p2p-external-port=<port>           External port for P2P network protocol, if port forwarding used with NAT [default: 8080].
  --walletd-bind-address=<ip:port>     Interface and port for walletd RPC [default: 127.0.0.1:8070].
  --bytecoind-bind-address=<ip:port>   Interface and port for bytecoind RPC [default: 0.0.0.0:8081].
  --bytecoind-remote-address=<ip:port> Connect to remote bytecoind and suppress running built-in bytecoind.
  --seed-node-address=<ip:port>        Specify list (one or more) of nodes to start connecting to.
  --priority-node-address=<ip:port>    Specify list (one or more) of nodes to connect to and attempt to keep the connection open.
  --exclusive-node-address=<ip:port>   Specify list (one or more) of nodes to connect to only. All other nodes including seed nodes will be ignored.

  --help, -h                           Show this screen.
  --version, -v                        Show version._

why --wallet-password DEPRECATED?

should walletd work in pair with bytecoind or it's standalone app? is it good practise to keep own bytecoind node?

there is new errors like:

terminate called after throwing an instance of 'platform::ExclusiveLock::FailedToLock'
  what():  ExclusiveLock fail at path=/root/.bytecoin/bytecoind.lock
Aborted

they rappers when you try to start second walletd process if no bytecoind lunched or if this is first walletd launch but bytecoind already running. looks like its available to use only one app with one db instance. is it true?

[SoraKohaku]

good to hear bcn make move in ruby installed. will try if travis work~

[bcndev]

@noglance You can not start more than one instance of bytecoind on a host and it's fully intentional. Don't do that.
walletd is really designed to be paired up with bytecoind. Currently, when run without explicit parameters of remote Bytecoin Node, Wallet Service starts an in-process bytecoind (built-in). This might change during stabilization period. Anyway, we recommend to set up a separate wholly owned Bytecoin Node for experienced users or even professional parties.
--wallet-password is set deprecated due to security reasons. Entering wallet file's password via stdin is considered better practice nowadays.

[noglance]

@bcndev I don't need to start second bytecoind but I'd like to start several walletd (two in my case) as I'd like to used one .wallet file for tests and second for production. Later I could split them in two servers but now I'd like to start them at one server with different ports for RPC connections as it was in first version of walletd

[noglance]

"This might change during stabilization period" ? "built-in" ... so I don't need to start walletd for RPC?

"--wallet-password is set deprecated due to security reasons. Entering wallet file's password via stdin"
I'm starting walletd as daemon service at server so I don't like to log in manually. It could be reloaded an start automatically in background. How this case server with RPC API should work, log in manually every time? Are you crazy?)) ?

[SoraKohaku]

this can run on ruby?will try forked~

…

On Feb 15, 2018 5:59 PM, "noglance" ***@***.***> wrote: "This might change during stabilization period" ? "built-in" ... so I don't need to start walletd for RPC? "--wallet-password is set deprecated due to security reasons. Entering wallet file's password via stdin" I'm starting walletd as daemon service at server so I don't like to log in manually. It could be reloaded an start automatically in background. How this case server with RPC API should work, log in manually every time? Are you crazy?)) ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK51tStCOPEqR18Oe7fvywJIOljmhzpFks5tU_HdgaJpZM4SBTW7> .

[bcndev]

@noglance

• Our Wiki has an example of running two walletd instances on the same host.
• There is no need to enter password manually only, just use echo "pwd" | walletd --walletfile=... in your scripts.

[SoraKohaku]

this updates code for wiki. nice update~did you move to travis compile guys?

…

On Thu, Feb 15, 2018 at 10:46 PM, Bytecoin Developers Team < ***@***.***> wrote: @noglance <https://github.com/noglance> - Our Wiki <https://github.com/bcndev/bytecoin/wiki/Running-Bytecoin-Services#handy-examples> has an example of running two walletd instances on the same host. - There is no need to enter password manually only, just use echo "pwd" | walletd --walletfile=... in your scripts. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK51teEE1msyHMvnF4wQUCHZPkOZ2AkJks5tVDVIgaJpZM4SBTW7> .

-- Nur1Labs©2013

______________________________ Site Info -> Here <http://nur1labs.com/> Easy Transaction MoneyBookers <https://www.moneybookers.com/app/?rid=17274145>

[kiahmed]

can you run this on testnet ? I dont see any command options for that ? Also any faucet for test coins ?

[SoraKohaku]

i think some improve in code. not try yet on vacation~

…

On Sun, Feb 18, 2018 at 3:34 AM, kiahmed ***@***.***> wrote: can you run this on testnet ? I dont see any command options for that ? Also any faucet for test coins ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK51tfwICg7GykYstqNGHc35zdv-fPicks5tVxu7gaJpZM4SBTW7> .

-- Nur1Labs©2013

______________________________ Site Info -> Here <http://nur1labs.com/> Easy Transaction MoneyBookers <https://www.moneybookers.com/app/?rid=17274145>

[noglance]

@bcndev

starting walletd:
Command line option --remote-bytecoind-address=127.0.0.1:8081 has no meaning (typo?)

starting bytecoind:
white screen about minute or more (strange. not very good without any hello world message)
and then:

oldest tip cd=200673536690758 bid=a850fbaea601097877f91520ae96df06452445cbbe1b4d5a35292d2141fc5332
tip cd=200673536690758 bid=a850fbaea601097877f91520ae96df06452445cbbe1b4d5a35292d2141fc5332
tip cd=200756713080016 bid=414e85bd3050589af563d96eddd50136e366d598f748d9a56b9beb3f8cfd8637
tip cd=204736355924710 bid=99262c4797a393444abf09f13029c4d49384eff94d9bfb1acf38853f28220da4
tip cd=207596065499703 bid=2dccbbc8dfe8db926e67dca56bff18a6585d6c4e1eedb3dbba57a151e3c97fb7
tip cd=207772642432244 bid=aa143a0018ab3eb4675aa7b330886dbd625b9505cebf9312bdfedbe37506d051
tip cd=208329916137463 bid=e4419558f1209c1336c7e557c6c230fff79e3bc2a30bb010a324a53d86fc3824
children counter=0 bid=2dccbbc8dfe8db926e67dca56bff18a6585d6c4e1eedb3dbba57a151e3c97fb7
children counter=2 bid=3ad840671ab1777477b457f752ad94628d0980a69945bdab42149f1369a3610c
children counter=0 bid=414e85bd3050589af563d96eddd50136e366d598f748d9a56b9beb3f8cfd8637
children counter=2 bid=595cb1c57a669a82beeb87ebf9a280b095feefef60d401cc9bf57088745c8ee2
children counter=2 bid=6294e55ccc6f5585f23c749702e6e4bc06cfa9f5e07bc6df37485e708897dfc2
children counter=0 bid=99262c4797a393444abf09f13029c4d49384eff94d9bfb1acf38853f28220da4
children counter=0 bid=a850fbaea601097877f91520ae96df06452445cbbe1b4d5a35292d2141fc5332
children counter=0 bid=aa143a0018ab3eb4675aa7b330886dbd625b9505cebf9312bdfedbe37506d051
children counter=0 bid=e4419558f1209c1336c7e557c6c230fff79e3bc2a30bb010a324a53d86fc3824
children counter=2 bid=ea9af3f5769a53da2cc0919450bd45378c6335180f8d9de8a202995f065800b5
children counter=2 bid=eec750dc19fcf33e15ff69b46140cba05ffc323fc6842fce635b5adb89c3bd8a
Starting multicore ring checker using 2/3 cpus

[noglance]

There is no need to enter password manually only, just use echo "pwd" | walletd --walletfile=... in your scripts.

strange practice.. and what for? may be it would be good to add this to wiki

[noglance]

and what it is in bytecoind log?

2018-Feb-17 17:43:05.220825 INFO [Node] jsonrpc request method not found - getBalance
2018-Feb-17 17:43:12.982195 INFO [Node] jsonrpc request method not found - getBalance
2018-Feb-17 17:43:46.085612 INFO [Node] jsonrpc request method not found - createAddress
2018-Feb-17 17:43:54.209739 INFO [Node] jsonrpc request method not found - createAddress
2018-Feb-17 17:43:57.329678 INFO [Node] jsonrpc request method not found - createAddress
2018-Feb-17 17:43:58.101704 INFO [Node] jsonrpc request method not found - createAddress
2018-Feb-17 17:44:01.557681 INFO [Node] jsonrpc request method not found - createAddress
2018-Feb-17 17:44:02.737639 INFO [Node] jsonrpc request method not found - createAddress
2018-Feb-17 17:44:44.109721 INFO [Node] jsonrpc request method not found - createAddress

[kiahmed]

@FndNur1Labs did you run on testnet or mainnet?

[SoraKohaku]

Tesnet many still unconfig yet. This good but need research future on.

…

On Feb 21, 2018 1:58 AM, "kiahmed" ***@***.***> wrote: @FndNur1Labs <https://github.com/fndnur1labs> did you run on testnet or mainnet? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK51tW8sN_5k--m_LP1cIOkx-FS5-X7-ks5tWxXkgaJpZM4SBTW7> .

[bcndev]

@noglance

• Option --remote-bytecoind-address is really incorrect, right version is --bytecoind-remote-address.
• getBalance is the old name of getting balance method. Use the new one.