Bitcoin Forum
September 16, 2019, 01:33:14 PM *
News: Latest Bitcoin Core release: 0.18.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Is the --satoshi-port command line argument disabled?  (Read 108 times)
TierNolan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1002


View Profile
November 13, 2018, 01:50:30 AM
 #1

I have a node running on a non-standard port and am trying to get Armory to connect to it.  It connects if I use the standard port, but not if I use a non-standard port.

I think there may be some issue with passing the command line argument over to the database process, but that is just a guess.

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1568640794
Hero Member
*
Offline Offline

Posts: 1568640794

View Profile Personal Message (Offline)

Ignore
1568640794
Reply with quote  #2

1568640794
Report to moderator
1568640794
Hero Member
*
Offline Offline

Posts: 1568640794

View Profile Personal Message (Offline)

Ignore
1568640794
Reply with quote  #2

1568640794
Report to moderator
1568640794
Hero Member
*
Offline Offline

Posts: 1568640794

View Profile Personal Message (Offline)

Ignore
1568640794
Reply with quote  #2

1568640794
Report to moderator
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 2310
Merit: 1125

Armory Developer


View Profile
November 13, 2018, 08:07:35 AM
 #2

Post your logs.

TierNolan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1002


View Profile
November 14, 2018, 02:00:57 AM
Merited by bob123 (1)
 #3

Sorry about not including that info, I was mainly asking if it was a known issue.

The log files (included below) don't contain that much info though.  They look pretty much identical in both cases.

The only difference is BitcoinP2P.cpp reporting connected to bitcoind in the db log file when it actually works.

I had a look at the code, and I think the problem could be in cppForSwig/BlockDataManagerConfig.cpp.

The btcPort_ variable is set to the #define value NODE_PORT_MAINNET rather than some kind of command line controlled variable.  It is hard coded depending on main/test/regtest networks rather than allowing the port to be selected.

Standard Port

Bitcoind started (manually) with this line in bitcoin.conf.  (default port used)

Code:
# port=8500

Armory started from command line with this.

Code:
C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=G:\armory_data --dbdir=G:\armory_data/database_dir --debug

It successfully connects.

dbLog.txt  armorylog.txt


Alternative Port (8500)

Bitcoind started (manually) with this line in bitcoin.conf

Code:
port=8500

Armory started from command line with this.

Code:
C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=G:\armory_data --dbdir=G:\armory_data/database_dir --debug --satoshi-port=8500

The GUI stays in offline mode.

dbLog.txt armorylog.txt

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 2310
Merit: 1125

Armory Developer


View Profile
November 14, 2018, 08:31:39 PM
 #4

I wanted the logs to see if the client was forwarding the argument to the db to begin with.

A quick look at the db code shows this argument is ignored as a whole. I'm about to push the RC for 0.96.5, I'll add it in there.

TierNolan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1002


View Profile
November 14, 2018, 09:35:50 PM
 #5

A quick look at the db code shows this argument is ignored as a whole. I'm about to push the RC for 0.96.5, I'll add it in there.

Great.

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!