Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: RPC server errors in wine  (Read 454 times)

0 Members and 1 Guest are viewing this topic.

merockstar

  • Guest
RPC server errors in wine
« on: July 25, 2014, 03:49:59 AM »

since (painstakingly) upgrading to 14.04 I was able to get bitsharesx running in wine.

I'm currently downloading the blockchain, have connections to the network. but I'm getting "RPC server errors" at the botton of the gui in all kinds of different methods. when the server error pops up it kicks me back to the main screen.

is this client safe to use?

Offline toast

Re: RPC server errors in wine
« Reply #1 on: July 25, 2014, 04:06:10 AM »
It's always safe if you don't put any well-funded wallets in it

edit:  that means no, by the way
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #2 on: July 25, 2014, 04:28:04 AM »
It's always safe if you don't put any well-funded wallets in it

edit:  that means no, by the way

damn. foiled again.

38PTSWarrior

  • Guest
Re: RPC server errors in wine
« Reply #3 on: July 25, 2014, 04:35:47 AM »
I tried tu build but I made a mistake witgh cmake . There is a dot behind cmake, maybe you didn't see this merockstar. I tried to use wine, but it always had a different problem. After it was not loading blocks anymore, i took all my power together and boom, i build it.. on a single core atom netbook. But the git ubuntu build is also wrong somewhere. It says "make BitSharesXT, i tried, it wasn't possible. I tried make BitSharesX and it worked. Then here:

For the Qt Wallet, some extra steps are required:

sudo apt-get install npm qt5-default libqt5webkit5-dev
cd bitshares-toolkit
cmake -DINCLUDE_QT_WALLET=ON .

You have to make cd bitsharesx instead of bitshares-toolkit.


38PTSWarrior

  • Guest
Re: RPC server errors in wine
« Reply #4 on: July 25, 2014, 04:37:58 AM »
It's always safe if you don't put any well-funded wallets in it

edit:  that means no, by the way

damn. foiled again.

I also hope nothing happened..

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #5 on: July 25, 2014, 04:40:27 AM »
I tried tu build but I made a mistake witgh cmake . There is a dot behind cmake, maybe you didn't see this merockstar. I tried to use wine, but it always had a different problem. After it was not loading blocks anymore, i took all my power together and boom, i build it.. on a single core atom netbook. But the git ubuntu build is also wrong somewhere. It says "make BitSharesXT, i tried, it wasn't possible. I tried make BitSharesX and it worked. Then here:

For the Qt Wallet, some extra steps are required:

sudo apt-get install npm qt5-default libqt5webkit5-dev
cd bitshares-toolkit
cmake -DINCLUDE_QT_WALLET=ON .

You have to make cd bitsharesx instead of bitshares-toolkit.

good looking out. but I've caught all those nuances.

here's the problem i had this time:

Code: [Select]
[ 92%] Built target BitSharesX_automoc
[ 92%] Generating qrc_bitshares.cpp
make[2]: *** No rule to make target `programs/qt_wallet/htdocs/locale-zh-CN.json', needed by `programs/qt_wallet/qrc_htdocs.cpp'.  Stop.
make[1]: *** [programs/qt_wallet/CMakeFiles/BitSharesX.dir/all] Error 2
make: *** [all] Error 2


lineman wouldn't run when I tried to do it, so I tried using puppies ht_docs folder that he uploaded to dropbox. i think it has something to do with that.

edit: also, nope nothing happened. my btsx is still on bter.

edit: I reproduced the error I got with lineman:

npm install -g lineman went without a hitch

but npm install produced this:

Code: [Select]
> [email protected] postinstall /home/merockstar/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js

sh: 1: node: not found
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! weird error 127
npm ERR! not ok code 0
« Last Edit: July 25, 2014, 06:06:42 PM by merockstar »

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
Re: RPC server errors in wine
« Reply #6 on: July 25, 2014, 07:52:35 PM »
http://stackoverflow.com/questions/18130164/nodejs-vs-node-on-ubuntu-12-04

That might be pertinent.  node was renamed nodejs, seems like perhaps you have the older version node? 

I dunno, just my guess..
I speak for myself and only myself.

Offline toast

Re: RPC server errors in wine
« Reply #7 on: July 25, 2014, 07:54:45 PM »
symlink /usr/bin/node to /usr/bin/nodejs
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #8 on: July 25, 2014, 07:57:31 PM »
http://stackoverflow.com/questions/18130164/nodejs-vs-node-on-ubuntu-12-04

That might be pertinent.  node was renamed nodejs, seems like perhaps you have the older version node? 

I dunno, just my guess..

I took it from this thread: https://bitsharestalk.org/index.php?topic=5951.0

looking there it looks like i'm wgetting 10.29, which according to http://nodejs.org/ is current.

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #9 on: July 25, 2014, 07:59:24 PM »
symlink /usr/bin/node to /usr/bin/nodejs

Code: [Select]
[email protected]:~/bitsharesx/bitsharesx-build$ symlink /usr/bin/node /usr/bin/nodejs
No command 'symlink' found, did you mean:
 Command 'symlinks' from package 'symlinks' (main)
symlink: command not found


do I mean symlinks?

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
Re: RPC server errors in wine
« Reply #10 on: July 25, 2014, 08:02:41 PM »
symlink /usr/bin/node to /usr/bin/nodejs

Code: [Select]
[email protected]:~/bitsharesx/bitsharesx-build$ symlink /usr/bin/node /usr/bin/nodejs
No command 'symlink' found, did you mean:
 Command 'symlinks' from package 'symlinks' (main)
symlink: command not found


do I mean symlinks?

Yes,
ln -s dest source   
so ln -s nodejs node   (but with full paths)
I speak for myself and only myself.

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #11 on: July 25, 2014, 08:09:25 PM »
symlink /usr/bin/node to /usr/bin/nodejs

Code: [Select]
[email protected]:~/bitsharesx/bitsharesx-build$ symlink /usr/bin/node /usr/bin/nodejs
No command 'symlink' found, did you mean:
 Command 'symlinks' from package 'symlinks' (main)
symlink: command not found


do I mean symlinks?

Yes,
ln -s dest source   
so ln -s nodejs node   (but with full paths)

cool. that did something. recompiling now *fingers crossed*

edit, for reasons of my personal understanding: did that just make an executable whose sole purpose in life is to run the other executable with the same parameters?

https://www.youtube.com/watch?v=FFvXvfUF-Co
« Last Edit: July 25, 2014, 08:19:22 PM by merockstar »

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #12 on: July 25, 2014, 08:40:15 PM »
same error.

but, since I created that symlink, maybe puppies little tutorial will work now. https://bitsharestalk.org/index.php?topic=6008.msg80548#msg80548

gonna delete everything and start over following that.

edit wait, I never ran lineman again, i just recompiled, so maybe this did fix it! doh! trying again
« Last Edit: July 25, 2014, 08:46:30 PM by merockstar »

merockstar

  • Guest
Re: RPC server errors in wine
« Reply #13 on: July 25, 2014, 10:02:46 PM »
Finally! I'm so happy! Thanks so much guys!


merockstar

  • Guest
Re: RPC server errors in wine
« Reply #14 on: July 26, 2014, 06:00:06 AM »
one last question.

when an upgrade comes out, what's the easiest way to recompile?

should I just delete the entire bitshares directory and do everything I just did again (it will be easier with my symlink and dependencies all set up)? or is there some git command for upgrading the source so I can just do another cmake>make afterwards?

 

Google+