[Linux] "Connecting to network..." 127.0.0.1:8090 seems dead AKA "How to run it?" #608

gwpl · 2017-12-18T18:19:08Z

After successfully building it on Arch Linux, I get never ending "Connecting to network..." and error messages complaining about 127.0.0.1:8090, which seems dead when trying to connect manually with wscat or netcat.

Cross-linking:

I've posted already on Cardano Forum here
here I found another user who build it but "has to figure out how to run it"

I've poked around and find that most Linux users are really confused, while there should be clear instructions what has to be run if it's more than just "daedalus".
(btw. Some notes refer to scripts "connect-to-mainnset" etc (like here) that are in cardano-sl repository but not in package that is build...).

The text was updated successfully, but these errors were encountered:

h4ck3rm1k3 · 2017-12-18T19:26:26Z

8090 is where the cardano node lives
mdupont@debian-build-speed:~/experiments/cardano-sl$ lsof -i:8090
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
cardano-n 5183 mdupont 31u IPv4 2991379 0t0 TCP localhost:8090->localhost:41616 (ESTABLISHED)

see https://github.com/h4ck3rm1k3/cardano-sl
./.stack-work/install/x86_64-linux-nopie/lts-9.1/8.0.2/bin/cardano-node
--web
--no-ntp
--configuration-file ./lib/configuration.yaml
--configuration-key mainnet_full
--tlscert ./scripts/tls-files/server.crt
--tlskey ./scripts/tls-files/server.key
--tlsca ./scripts/tls-files/ca.crt
--log-config ./scripts/log-templates/log-config-qa.yaml
--topology "topology-mainnet"
--logs-prefix "state-wallet-mainnet/logs"
--db-path "state-wallet-mainnet/db"
--wallet-db-path 'state-wallet-mainnet/wallet-db'
--keyfile state-wallet-mainnet/secret.key

gwpl · 2017-12-18T19:38:40Z

(btw. I am using calling just cardano-node, as I've build it using following PKGBUILD on Archlinux: https://aur.archlinux.org/packages/cardano-sl )

$ git clone https://github.com/input-output-hk/cardano-sl.git
$ cd cardano-sl
$ cardano-node \
--web  \
--no-ntp  \
--configuration-file ./lib/configuration.yaml  \
--configuration-key mainnet_full  \
--tlscert ./scripts/tls-files/server.crt  \
--tlskey ./scripts/tls-files/server.key  \
--tlsca ./scripts/tls-files/ca.crt  \
--log-config ./scripts/log-templates/log-config-qa.yaml  \
--topology "topology-mainnet"	 \
--logs-prefix "state-wallet-mainnet/logs"  \
--db-path "state-wallet-mainnet/db"  \
--wallet-db-path 'state-wallet-mainnet/wallet-db'  \
--keyfile state-wallet-mainnet/secret.key

Result cardano-node: ConfigurationParseFailure "./lib/configuration.yaml"(...)the key memPoolLimit was not present :

[Attention] We are in DEV mode
Asserts are ON
[Attention] Software is built with wallet part
ConfigurationOptions {cfoFilePath = "./lib/configuration.yaml", cfoKey = "mainnet_full", cfoSystemStart = Nothing}
cardano-node: ConfigurationParseFailure "./lib/configuration.yaml" (AesonException "Error in $['mainnet_staging_short_epoch_wallet_win64'].core: When parsing the record coreConfiguration of type Pos.Core.Configuration.Core.CoreConfiguration the key memPoolLimit was not present.")

There seems only memPoolLimitTx is present:

$ grep -n memPool lib/configuration.yaml 
62:    memPoolLimitTx: 200 # mem pool will be limited to this many transactions
253:    memPoolLimitTx: 200 # mem pool will be limited to this many transactions

Therefore, is lib/configuration.yaml in current cardano-sl head (commit 1175f07a7c475ef52302d43c637491a7d6b115c4 ) incorrect?

Btw. Is it reference from where have you taken command line: https://github.com/input-output-hk/cardano-sl/blob/723d55b841560fc3067a58cfcaa6861286ccadaa/scripts/launch/connect-to-cluster/default.nix#L51

h4ck3rm1k3 · 2017-12-18T19:49:50Z

ok it looks like you might have a different config file. can you compare to https://github.com/h4ck3rm1k3/cardano-sl/blob/master/lib/configuration.yaml

h4ck3rm1k3 · 2017-12-18T19:50:17Z

Good find with the connect to cluster launch script.

gwpl · 2017-12-19T00:27:58Z

It is not this...

$ diff lib/configuration.yaml h4ck3rm1k3_configuration.yaml | wc -l 
0

h4ck3rm1k3 · 2017-12-19T00:54:36Z

Well can you build the latest version? or compare your configuration.yaml to the one that matches the binary version you built. I have not looked into the packaging you are using.

gwpl · 2017-12-19T11:38:15Z

The guestion may be, which branch, as I've noticed that

How to Build Cardano SL and Daedalus from Source Code

points to

Switch to the latest release branch, for example, cardano-sl-1.0

Therefore I understand to try cardano-sl-1.0 branch.
(Is that correct ? Or should I try different? Or maybe sync git to specific commit?)

h4ck3rm1k3 · 2017-12-19T12:42:49Z

I am building mine from master not 1.0, but yes, if that is the version you are using in arch then compare that version.

…

On Tue, Dec 19, 2017 at 6:38 AM, Grzegorz Wierzowiecki < ***@***.***> wrote: The guestion may be, which branch, as I've noticed that - How to Build Cardano SL and Daedalus from Source Code <https://github.com/input-output-hk/cardano-sl/blob/9844854414d3ca153cc44e13783d5f90e7725efb/docs/how-to/build-cardano-sl-and-daedalus-from-source-code.md> points to Switch to the latest release branch, for example, cardano-sl-1.0 Therefore I understand to try cardano-sl-1.0 branch. (Is that correct ? Or should I try different? Or maybe sync git to specific commit?) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#608 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACIV_coedI69s6rS7yXyDjU0fw06mZSks5tB6AogaJpZM4RF3-1> .

-- James Michael DuPont

gwpl · 2017-12-19T15:10:52Z

I can build from any branch, I can configure it, could you please provide me desired commit hash of git from where you've build , so I could perform fair comparison on build made from the same codebase?

h4ck3rm1k3 · 2017-12-19T22:38:43Z

ok here is what I have running but cannot get a transaction to show. d30dd9f9184a4395d83f7e61b9f2e15efb5a966d git@github.com:h4ck3rm1k3/cardano-sl.git on backend 0733ef6 git@github.com:input-output-hk/daedalus.git on middleware 7d8746f git@github.com:h4ck3rm1k3/daedalus.git for the front end.

…

On Tue, Dec 19, 2017 at 10:10 AM, Grzegorz Wierzowiecki < ***@***.***> wrote: I can build from any, just give me commit hash. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#608 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACIV_P-Jv60BVYL3PQcudHVWPxhB-mvks5tB9H-gaJpZM4RF3-1> .

-- James Michael DuPont

h4ck3rm1k3 · 2017-12-20T11:03:58Z

https://steemit.com/ada/@h4ck3rm1k3st33m/first-ada-recieved i got my first ada in my self compiled wallet and node

tanzeelrana · 2018-01-07T16:15:25Z

[nix-shell:~/daedalus]$ npm install
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/nodejs)
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/nodejs)
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/nodejs)
npm WARN package.json daedalus@0.8.0 No repository field.

daedalus@0.8.0 preinstall /home/tanzeel/daedalus
which electron || npm install electron@1.7.9

/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/nodejs)
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/nodejs)
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/nodejs)
npm WARN package.json daedalus@0.8.0 No repository field.
npm http GET https://registry.npmjs.org/electron/1.7.9
npm http 200 https://registry.npmjs.org/electron/1.7.9
npm http GET https://registry.npmjs.org/electron/-/electron-1.7.9.tgz
npm http 200 https://registry.npmjs.org/electron/-/electron-1.7.9.tgz
npm http GET https://registry.npmjs.org/types/node
npm http GET https://registry.npmjs.org/electron-download
npm http GET https://registry.npmjs.org/extract-zip
npm http 200 https://registry.npmjs.org/extract-zip
npm http 200 https://registry.npmjs.org/electron-download
npm http GET https://registry.npmjs.org/extract-zip/-/extract-zip-1.6.6.tgz
npm http GET https://registry.npmjs.org/electron-download/-/electron-download-3.3.0.tgz
npm http 404 https://registry.npmjs.org/types/node
npm ERR! TypeError: Cannot read property 'latest' of undefined
npm ERR! at next (/usr/share/npm/lib/cache.js:687:35)
npm ERR! at /usr/share/npm/lib/cache.js:675:5
npm ERR! at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR! at /usr/lib/nodejs/graceful-fs/polyfills.js:133:7
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com

npm ERR! System Linux 4.4.0-31-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "electron@1.7.9"
npm ERR! cwd /home/tanzeel/daedalus
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! type non_object_property_load
npm http 200 https://registry.npmjs.org/extract-zip/-/extract-zip-1.6.6.tgz
npm http 200 https://registry.npmjs.org/electron-download/-/electron-download-3.3.0.tgz
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/tanzeel/daedalus/npm-debug.log
npm ERR! not ok code 0
npm ERR! weird error 1
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! not ok code 0

tanzeelrana · 2018-01-07T16:17:10Z

My npm version is

[nix-shell:~/daedalus]$ npm -v
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/nodejs)
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/nodejs)
/usr/bin/nodejs: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/nodejs)
1.3.10

tanzeelrana · 2018-01-07T16:43:40Z

my node version

[nix-shell:~/daedalus]$ node -v
node: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libcrypto.so.1.0.0: no version information available (required by node)
node: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by node)
node: /nix/store/cr49q6vvyhfs48dg15ys3mghfzgc80i7-openssl-1.0.2l/lib/libssl.so.1.0.0: no version information available (required by node)
v0.10.25

SebastienGllmt · 2018-01-08T08:14:49Z

I made a video guide for how to setup the project (as of current state) on Linux. This will hopefully solve the problem. https://www.youtube.com/watch?v=ep6VcpSflc0

erikd · 2018-01-08T08:30:51Z

To give people a choice, here's a Makefile and scripts to build daedalus/cardano.

AmosHason · 2018-01-08T22:26:34Z

Replicated on Windows 7. I'm just trying to run Daedalus for the first time, for over a week. In the meantime it got fully synchronized (I understood it from the logs). I tried everything suggested on the FAQ and on the web, and I mean everything (except using another PC, which is not a fix).

tanzeelrana · 2018-01-09T05:42:49Z

@erikd

tanzeel@tanzeel-System-Product-Name:$ git clone https://github.com/erikd/cardano-linux-pkg.git
Cloning into 'cardano-linux-pkg'...
remote: Counting objects: 74, done.
remote: Compressing objects: 100% (46/46), done.
remote: Total 74 (delta 35), reused 63 (delta 24), pack-reused 0
Unpacking objects: 100% (74/74), done.
Checking connectivity... done.
tanzeel@tanzeel-System-Product-Name:$ cd
.cache/ Documents/ .local/ Public/
cardano-linux-pkg/ Downloads/ .mozilla/ Templates/
.config/ .gconf/ Music/ Videos/
Desktop/ .gnupg/ Pictures/
tanzeel@tanzeel-System-Product-Name:$ cd cardano-linux-pkg/
tanzeel@tanzeel-System-Product-Name:/cardano-linux-pkg$ make
mkdir -p stamp
scripts/git-sync-repo.sh https://github.com/input-output-hk/cardano-sl.git source/cardano-sl
Cloning into 'source/cardano-sl'...
remote: Counting objects: 148209, done.
remote: Compressing objects: 100% (81/81), done.
remote: Total 148209 (delta 23), reused 23 (delta 6), pack-reused 148119
Receiving objects: 100% (148209/148209), 79.54 MiB | 1.40 MiB/s, done.
Resolving deltas: 100% (107029/107029), done.
Checking connectivity... done.
touch stamp/cardano-source
scripts/ghc-version-check.sh
scripts/ghc-version-check.sh: line 3: ghc: command not found
Makefile:186: recipe for target 'stamp/cabal-update' failed
make: *** [stamp/cabal-update] Error 127
tanzeel@tanzeel-System-Product-Name:~/cardano-linux-pkg$

AmosHason · 2018-01-10T11:50:50Z

Please, it is a critical issue that must be solved immediately. Many ADA holders can't use their wallets. There is no alternative. How come it still isn't solved?

erikd · 2018-01-10T18:52:50Z

@tanzeelrana Your comment should be moved to an issue on my repo rather than here. However, the problem is that you do not have GHC installed. There is a comment at the top of the Makefile about required prerequisites.

tanzeelrana · 2018-01-11T01:59:39Z

@erikd definitely my comment should be moved to you repo. Is there a way to move a comment ?
and thanks for the pointer to prerequisites.

Cheers :)

erikd · 2018-01-11T02:02:37Z

@tanzeelrana I think "cut'n'paste" is the only method.

tanzeelrana · 2018-01-11T03:13:42Z

@SebastienGllmt

I followed all the instructions as u said but I keep failing at the following step

To build a script that will contain everything needed to connect to mainnet: $ nix-build release.nix -A connect.mainnetWallet -o connect-to-mainnet

the conenct to mainnet file is never generated :(

cleverca22 · 2018-01-11T06:48:37Z

@tanzeelrana the automated tests failed during the build

tanzeelrana · 2018-01-11T07:09:52Z

@cleverca22 I got it working the second time. Not sure why it was failing but its gone now.

dmitrystas · 2018-01-27T15:04:31Z

Windows 10 x64 Daedalus Version 1.0.3769

[2018-01-27 15:39:48:0611] [error] CardanoClientApi::syncProgress error: {
"stack": "Error: connect ECONNREFUSED 127.0.0.1:8090\n at Object.exports._errnoException (util.js:1026:11)\n at exports._exceptionWithHostPort (util.js:1049:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)",
"message": "connect ECONNREFUSED 127.0.0.1:8090",
"code": "ECONNREFUSED",
"errno": "ECONNREFUSED",
"syscall": "connect",
"address": "127.0.0.1",
"port": 8090
}

cleverca22 · 2018-01-27T19:34:14Z

@dmitrystas is cardano-node.exe running?, are there any errors in cardano-node.log ?

dmitrystas · 2018-01-27T20:03:49Z

The problem with the windows user name - %appdata% contains some non-latin characters (cyrillic)

To resolve this just create symlink for folder

mklink /J c:\Users\OriginalNonLatinName c:\Users\AnyLatinName

then after Daedalus install before 1-st run replace in C:\Program Files\Daedalus\daedalus.bat all %APPDATA% to c:\Users\AnyLatinName

domenkozar · 2018-02-23T13:45:32Z

Please follow #492 for official support for Linux

felipecaldas · 2018-04-17T12:04:29Z

the node is not running in Windows with

[*production*:INFO:ThreadId 3] [2018-04-17 12:03:29.63 UTC] [Attention] Software is built with wallet part
[*production*:INFO:ThreadId 3] [2018-04-17 12:03:29.63 UTC] using configurations: ConfigurationOptions {cfoFilePath = "lib/configuration.yaml", cfoKey = "default", cfoSystemStart = Nothing, cfoSeed = Nothing}
[node:ERROR:ThreadId 3] [2018-04-17 12:03:29.63 UTC] ConfigurationParseFailure "lib/configuration.yaml" (InvalidYaml (Just (YamlException "Yaml file not found: lib/configuration.yaml")))
cardano-node.exe: ConfigurationParseFailure "lib/configuration.yaml" (InvalidYaml (Just (YamlException "Yaml file not found: lib/configuration.yaml"))```

cleverca22 · 2018-04-17T14:46:19Z

you have to pass the node a --configuration-file path/to/configuration.yaml to tell it where to find the file

felipecaldas · 2018-04-17T21:28:23Z

The actual issue is that when I click on the Daedalus Windows shortcut link, the wallet opens but it stays at forever connecting. The error in the logs is CONNECTION RESET on 127.0.0.1:8090.

So makes me think the node is not running - but I have never had to run it explicitly. This started happening about two days ago.

felipecaldas · 2018-04-17T21:36:28Z

[2018-04-18 07:36:08:0576] [debug] Connection Lost. Reconnecting...
[2018-04-18 07:36:08:0982] [error] AdaApi::syncProgress error: {
"stack": "Error: connect ECONNREFUSED 127.0.0.1:8090\n at Object.exports._errnoException (util.js:1050:11)\n at exports._exceptionWithHostPort (util.js:1073:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)",
"message": "connect ECONNREFUSED 127.0.0.1:8090",
"code": "ECONNREFUSED",
"errno": "ECONNREFUSED",
"syscall": "connect",
"address": "127.0.0.1",
"port": 8090
}

humanoidcreature · 2018-04-28T18:28:28Z

This is sad.
I had the same "ECONNREFUSED" error in December. I managed to run the wallet with changing the paths in the Daedalus.bat, but recently updated the wallet to the new version and the problem is back, and the wallet won't start with the bat file anymore.
If I install the old version back again I am able to run the wallet again once since the update is out and after a restart, it will install it...
A lot of time passed since you know about this error. Is this hard to do something about it?

cleverca22 · 2018-05-01T23:29:15Z

@humanoidcreature are there any errors in the node.pub logfile?

rb2k · 2018-07-08T15:10:08Z

I had this issue for months and always hoped some new version would just fix whatever was broken.

For some reason, in the depths of my error messages, it complained about the server tls cert not being available. That seems to have lead to the node running, but the server that the Frontend connects to not actually listening on a port.

I reran build-certificates-unix.sh from within the Application bundle and now everything works.

h4ck3rm1k3 mentioned this issue Dec 20, 2017

Uncaught SyntaxError: Unexpected end of JSON input #611

Closed

dantrevino mentioned this issue Jan 2, 2018

Errors from wallet code #635

Closed

SebastienGllmt mentioned this issue Jan 7, 2018

Error: connect ECONNREFUSED 127.0.0.1:8090 #649

Closed

erikd mentioned this issue Jan 8, 2018

[MAC] Error: connect ECONNREFUSED 127.0.0.1:8090 #650

Closed

AmosHason mentioned this issue Jan 14, 2018

[build-certificates-win64.bat] Fix OPENSSL_MD replacement #664

Closed

domenkozar closed this as completed Feb 23, 2018

[Linux] "Connecting to network..." 127.0.0.1:8090 seems dead AKA "How to run it?" #608

[Linux] "Connecting to network..." 127.0.0.1:8090 seems dead AKA "How to run it?" #608

Comments

gwpl commented Dec 18, 2017

h4ck3rm1k3 commented Dec 18, 2017

gwpl commented Dec 18, 2017 • edited Loading

h4ck3rm1k3 commented Dec 18, 2017

h4ck3rm1k3 commented Dec 18, 2017 • edited Loading

gwpl commented Dec 19, 2017

h4ck3rm1k3 commented Dec 19, 2017

gwpl commented Dec 19, 2017

h4ck3rm1k3 commented Dec 19, 2017 via email

gwpl commented Dec 19, 2017 • edited Loading

h4ck3rm1k3 commented Dec 19, 2017 via email

h4ck3rm1k3 commented Dec 20, 2017

tanzeelrana commented Jan 7, 2018

tanzeelrana commented Jan 7, 2018

tanzeelrana commented Jan 7, 2018

SebastienGllmt commented Jan 8, 2018

erikd commented Jan 8, 2018

AmosHason commented Jan 8, 2018 • edited Loading

tanzeelrana commented Jan 9, 2018

AmosHason commented Jan 10, 2018

erikd commented Jan 10, 2018 • edited Loading

tanzeelrana commented Jan 11, 2018 • edited Loading

erikd commented Jan 11, 2018

tanzeelrana commented Jan 11, 2018 • edited Loading

cleverca22 commented Jan 11, 2018

tanzeelrana commented Jan 11, 2018

dmitrystas commented Jan 27, 2018

cleverca22 commented Jan 27, 2018

dmitrystas commented Jan 27, 2018

domenkozar commented Feb 23, 2018

felipecaldas commented Apr 17, 2018

cleverca22 commented Apr 17, 2018

felipecaldas commented Apr 17, 2018

felipecaldas commented Apr 17, 2018

humanoidcreature commented Apr 28, 2018

cleverca22 commented May 1, 2018

rb2k commented Jul 8, 2018

gwpl commented Dec 18, 2017 •

edited

Loading

h4ck3rm1k3 commented Dec 18, 2017 •

edited

Loading

gwpl commented Dec 19, 2017 •

edited

Loading

AmosHason commented Jan 8, 2018 •

edited

Loading

erikd commented Jan 10, 2018 •

edited

Loading

tanzeelrana commented Jan 11, 2018 •

edited

Loading

tanzeelrana commented Jan 11, 2018 •

edited

Loading