xmr-node-proxy icon indicating copy to clipboard operation
xmr-node-proxy copied to clipboard

Issue whilst installing the cyptonote-utils package

Open MossFrog opened this issue 8 years ago • 8 comments
trafficstars

errorlog

I have uploaded the image, anyone have any suggestions? The output message appears to be ELIFECYCLE, ive tried updating npm and node.js to no avail.

MossFrog avatar Oct 27 '17 12:10 MossFrog

+1 on this. Having the same issue.

spanias avatar Nov 07 '17 14:11 spanias

What version of Ubuntu? This looks like a GCC compile bug. Keep in mind, this project is explicitly targeted at Ubuntu 16.04 LTS x64

Snipa22 avatar Nov 07 '17 16:11 Snipa22

Same error in x64 Debian9 (stretch) and not AES-NI (changed github str in packages.json)

Ales999 avatar Nov 07 '17 16:11 Ales999

Ubuntu 17.10 64bit

lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 17.10 Release: 17.10 Codename: artful uname -a 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I also removed AES-NI from packages.json

The problem is with the compilation of cryptonote-util: ../src/crypto/crypto.cpp: In function ‘std::size_t crypto::rs_comm_size(std::size_t)’: ../src/crypto/crypto.cpp:224:58: error: value-initialization of incomplete type ‘crypto::rs_comm:: []’ return sizeof(rs_comm) + pubs_count * sizeof(rs_comm().ab[0]);

I guess I must install another vm. :/

spanias avatar Nov 07 '17 17:11 spanias

Description: Ubuntu 17.10

This is not supported. Use Ubuntu 16.04 LTS. Using non-LTS for anything you plan on running traffic to is insane.

Snipa22 avatar Nov 07 '17 18:11 Snipa22

Yes, I got that much. 👍 Thank you Snipa.

Will try making a docker container out of this when I get some time. That should make deployment easier. :)

spanias avatar Nov 07 '17 19:11 spanias

EDIT: I'm an idiot, disregard the below error. I got ahead of myself and did not grant the user passwordless sudo (typo in config file). After fixing my sudoers file and re-running the setup, the proxy works!

praeluceo avatar Nov 17 '17 04:11 praeluceo

I'm having this exact problem. I've made sure my user has sudo privileges. Running a completely new DigitalOcean Ubuntu 16.04.4 LTS Droplet. I've tried the walk through several times and I'm still getting this error. Any suggestions?

EDIT: If anyone else comes across this issue, for some reason running through the digitalocean terminal instead of ssh solved the problem for me...

phubbard91 avatar Apr 30 '18 16:04 phubbard91