Trying to get Ripple Server Deployed

[Tim Brown]

Hi

I've built the Ripple Client successfully

Now I've been referring to the wiki page 'Rippled Server Setup'. On this page, before we get to 'deployment process', there is a link to 'set up a public server' so I thought it would be a good idea to follow these steps first. I created the 'public' directory within the 'Ripple' directory, saved the rippled-example.cfg files as rippled.cfg in the public folder and changed only the ips and validators to the ones shown here: https://ripple.com/ripple.txt 

Then added to the rippled.cfg file

[ledger_history]
full

[node_db]
type=HyperLevelDB
path=db/hyperldb

Should the following also be added?:

# rippled --net

# watch -n .1 rippled server_info

When I got to:

'Add the init script to the automatic startup scripts so rippled will start automatically when the server starts', I just entered to following commands into terminal:

$ sudo apt-get install sysv-rc-conf
$ sysv-rc-conf rippled on

Was there anything else I should have done at this point?

I did the next instruction and then for

'Make a symlink to rippled.cfg::'

$ ln -s /etc/ripple/rippled.cfg .config/ripple/rippled.cfg

I get, ln: failed to create a symbolic link '.config/ripple/rippled.cfg': file exists

and the following command:
 
/etc/init.d/rippled start

yields only '/etc/init.d/rippled command not found.

Any help is much appreciated, I'm a first time Linux user. 

[Tim Brown]

Adding to my initial post, I've found that the symbolic link error was because I had previously tried to create the symbolic link, so I removed this, made the symbolic link again and I assume this has been done successfully.

Also I tried 'Rippled start' from the terminal as opposed to /etc/init.d/rippled start and at least now it tries to connect to the Rippled Server, but I still get an error:
connecting to: :5001
{
"error" : "internal",
"error_code" : 60,
"error_message" : "Internal error."
"error_what": "no response from server"

[Bryce a. Lynch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/10/14 05:04, Tim Brown wrote:
> Now I've been referring to the wiki page 'Rippled Server Setup'. On
> this page, before we get to 'deployment process', there is a link
> to 'set up a public server' so I thought it would be a good idea to
> follow these

I did a little digging and found a page with that title. How old is it?

> steps first. I created the 'public' directory within the 'Ripple'

When you say 'ripple directory', do you mean a checkout of the Ripple
web client or a checkout of rippled's source code?

> Then added to the rippled.cfg file
>
> [ledger_history] full
>
> [node_db] type=HyperLevelDB path=db/hyperldb
>
> Should the following also be added?:
>
> # rippled --net

That is a command for starting rippled so that it participates in the
network. That does not go in the config file.

> # _watch -n .1 rippled server_info

Nor does this. That is a command to pull your server's status report
every 0.1 seconds.

> 'Add the init script to the automatic startup scripts so rippled
> will start automatically when the server starts', I just entered to
> following commands into terminal:
>
> $ sudo apt-get install sysv-rc-conf $ sysv-rc-conf rippled on
>
>
> Was there anything else I should have done at this point?

Scrolled down to the section of the page called "rippled initscript"
and pasted that code into /etc/init.d/rippled. There is also a copy
of the initscript in rippled/doc/rippled.init, which is more up to date.

> I did the next instruction and then for
>
> 'Make a symlink to rippled.cfg::'
>
> $ ln -s /etc/ripple/rippled.cfg .config/ripple/rippled.cfg
>
> I get, ln: failed to create a symbolic link
> '.config/ripple/rippled.cfg': file exists

You got that bit backwards - it should have been

ls -s .config/ripple/rippled.cfg /etc/ripple/rippled.cfg

- --
Bryce

Integration Security Engineer, Ripple Labs
PGP: 0xA4364248 / A177 A590 2869 32AC E2E1 946A FAD8 98D6 A436 4248
"We see in order to move; we move in order to see."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJS+SQwAAoJEPrYmNakNkJIHb8P/RcOTD+AGNis/8sjXCQh75rv
VyGGvR4CW2aoVq6tIlip6TQ4I4hFl0yyzjKV1TR0WYJhyXzXMquWXdigPemgJl+T
S5nXJTFVYe0IKkatuwBvdVmzWYX6AdNknOC7pEjyQadIRarypR3UQTqygvCctxy8
9QAKRBR+v63wck3LXbJ9tGcxjRjqMhjuhtuYZEWAF3utmEgcjc8u1OVy9nlSgnMO
y9HVyy59eDeSEbpxV8uGYt+pohHxQ5xs2Pp3GKqU6XkctsPsgGaAcliudJmBP7/P
FPh76OrKNxSVtqqA7tme64J5162Zxg6/adX3Ih3xbuiXg+sHaPkN0F1y3TtmsKCr
HkIwej16lsSo56fNb1uvBjD9Gbyu9DrGxFvnBrX28PhgkbhX6OB0HYTxsXTVKzTq
+sgcFQU556HvgcCKJEQrs0HdyWOZat3pV5SbISqcJRsctKWJyUa5UpUNo/s/RHSH
mOu0VexpEAgCjEK9TNc5rHhRwFaeJnLmwVrIOovCyjSgU6vdvJhX3d67S44d2mF0
Y3oj0InEHhDK4Ctfvq5Y/RfdadpaBRF5oE+y6mg6Aqg+wMBbUKE5fWihmLJdJs7H
6oOfzMXhDNGmNawl+ye2Lj1tiUpBqGLTyk7JA5VQPzdnh9sl7m6z06pYOJtNL7s8
0ImlbwPVPVzk5la65/Pr
=3nDj
-----END PGP SIGNATURE-----

[Bryce a. Lynch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/10/14 05:31, Tim Brown wrote:
> Also I tried 'Rippled start' from the terminal as opposed to
> /etc/init.d/rippled start and at least now it tries to connect to
> the Rippled Server, but I still get an error: connecting to: :5001
> { "error" : "internal", "error_code" : 60, "error_message" :
> "Internal error." "error_what": "no response from server"

`rippled start` and `/etc/init.d/rippled start` are two different
commands.

The former means "take the first instance of rippled in your $PATH
variable and run it with the argument 'start'", which does not work.

The latter means "run the system initscript /etc/init.d/rippled with
the argument start", which does work. This is the one you want.

- --
Bryce

Integration Security Engineer, Ripple Labs
PGP: 0xA4364248 / A177 A590 2869 32AC E2E1 946A FAD8 98D6 A436 4248
"We see in order to move; we move in order to see."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJS+SbxAAoJEPrYmNakNkJIDAMP/1I4OjEZTQbY0eoT/GQarUpi
dYNMmg+iU/y9sWD02TChOBSN/50jU6NDgPzbZS3LLVMVYyMtyTlqjHpxDhQzoJoQ
l6eOKIVHGciMS85lPWYUJf8HuP/Ag9zD7d2ZKMHBNk9AJ11NoamGdBFHQxibyQ43
9bFUkZWqNBXLcj0ZQgIfKIp2BN6Oa0+Q8NgZLQT+/MRUDxfSCVRkAqRVKr3Paa8G
rezi+pEsk/ATHHHMimacIyIE4Uh82CTNh/JdSf1ftmJoucvqNTU0lbDqtMQzsJxZ
ouERPCX5NZqrHD6lC3emfHz+x1ukLRJSYKLLSAcjAwIGUNtmic3KCYKd0D2BtmYk
14/0vQ2X+hqCeWMywTFmbgYs0qPEmojRkmn32SGAHmiLihgIUlv1raLyG7Eb77ep
i2Hu//Afpk0t/2aNQMz4WGePeu2d4AUNX/NDv3Ut7RBLWqNxb1aSjWayBhUT0jkT
/9T9B5GgGcTP7NmFRTGfMnzosd7sbAx5OjxHJCq1t3IuTl/bwVS+vrRCwDjOotJ4
kHCCB1+fmjdjpkhzD4i+09X5/P906aGDmj49CSeOkr6TI2Y98V/hC7mOVVW1F7no
cJcCRyJbiXDB0RhT2sitkFfvkzodCR6uX33f7FoPpd0MmnhYDw0sBUg2WS9X1OWv
uyJAuJ0n1OF9myZAL9mg
=U9g+
-----END PGP SIGNATURE-----

[Tim Brown]

When I type in the command

'/etc/init.d/rippled start'

I get '/etc/init.d/rippled command not found'

When I say 'rippled directory', I mean the rippled folder that was created when I downloaded the source code for the ripple build. I'll try to be as clear as possible on what I've done to now so maybe you can figure out at which point I've gone wrong.

I followed the build instructions for Ubuntu and that was all fine.

Then I got to this page https://ripple.com/wiki/Rippled_Server_Setup

On this page, before 'deployment process' there is a link to https://ripple.com/wiki/Setup_a_public_server so I assumed these steps should be followed first. Now here it tells you to create a public directory. I already have a public directory on linux, so I assumed this meant create a public directory in the 'rippled' directory that I have from downloading the Rippled build. I followed the rest of the steps on that page and saved the rippled.cfg file that I edited with gedit (with the adjustments instructed on that page) to the new 'public' directory that I have created within my 'rippled' directory.

Then I went onto the previous page and followed the instructions under 'deployment process'. I followed all the instructions and as you said, I saved the init script to

/etc/init.d.


When I try to start ripple with the given command, I get the error stated at the start of the post.

Personally, I'm not sure where the instructions for the creation of a public folder come into the equation. It's probably that I'm new to Ubuntu
I'm having problems following the instructions, but can't quite figure out at which point I've gone wrong.

[Bryce a. Lynch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/10/14 14:05, Tim Brown wrote:
> When I type in the command '/etc/init.d/rippled start' I get
> '/etc/init.d/rippled command not found'

In your earlier e-mails, you did not say that you installed the
rippled initscript, either the one found in rippled/doc/ or the one on
the https://ripple.com/wiki/Rippled_Server_Setup page. It has to be
done manually; copying the rippled binary into /usr/local/sbin isn't
enough.

> When I say 'rippled directory', I mean the rippled folder that was
> created when I downloaded the source code for the ripple build.
> I'll try to be as clear as possible on what I've done to now so
> maybe you can figure out at which point I've gone wrong.

Thank you very much. It helps to orient in the discussion.

> On this page, before 'deployment process' there is a link to
> https://ripple.com/wiki/Setup_a_public_server so I assumed these
> steps

You do not necessarily have to set up a private server (though we
appreciate it if you do!). I would recommend starting with a basic
node first, getting used to it, and then growing it later.

> should be followed first. Now here it tells you to create a public
> directory. I already have a public directory on linux, so I assumed
> this meant create a public directory in the 'rippled' directory
> that I have from downloading the Rippled build. I followed the rest
> of the steps on that page and saved the rippled.cfg file that I
> edited with gedit (with the adjustments instructed on that page) to
> the new 'public' directory that I have created within my 'rippled'
> directory.

That page seems sufficiently out of date that the [node_db] bit has
been the default in rippled-example.cfg for several releases running.

I don't know if your use case (or current storage capacity) are
sufficient to maintain a full mirror of the public ledger. If that is
your goal, we thank you for it but it may be wise to start smaller and
build up to what you need.

> Then I went onto the previous page and followed the instructions
> under 'deployment process'. I followed all the instructions and as
> you said, I saved the init script to /etc/init.d.

When you ran sysv-rc-conf, did it report that it successfully
installed the initscript? Did you run that command under sudo,
because those directories are owned by the root user?

> When I try to start ripple with the given command, I get the error
> stated at the start of the post.

There are a couple of possible reasons: The initscript might not be in
/etc/init.d (say, if you were trying to create it in there while not
root), it's not executable, or rippled is not in /usr/local/sbin.

There is one other possibility: If you look at the initscript, it
contains the following line:

DAEMON_OPTS="--conf /etc/ripple/rippled.cfg"

That tells rippled where to find its configuration file; in this case,
in the directory /etc/ripple.

sudo mkdir -p /etc/ripple
sudo cp doc/rippled-example.cfg /etc/ripple/rippled.cfg

> Personally, I'm not sure where the instructions for the creation of
> a public folder come into the equation. It's probably that I'm new
> to
Ubuntu

That would pose a problem.

> I'm having problems following the instructions, but can't quite
> figure out at which point I've gone wrong.

We'll get it sorted out..

- --
Bryce

Integration Security Engineer, Ripple Labs
PGP: 0xA4364248 / A177 A590 2869 32AC E2E1 946A FAD8 98D6 A436 4248
"We see in order to move; we move in order to see."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJS+WHsAAoJEPrYmNakNkJIUkoP/3TTMTvcfvVJUDuTQJ21KTh6
Eds4O/DYv3rJLHWtOrSmNH4C1tKCAp2z/ledKCu98jiMf28J2TqbEFt/c2rSD4Zi
/ZFZyjUkLrsqU753qS7xg/Vh5AheAj6FTHwOUibBN9hJxM1rwWOyzm9NdQvhOMnH
nRg5byMpo/Kt2PUgiHSbdUzFNVoX8HYRNPs7fYM7KFKJp81SsZiS9G9RThsd1qpH
iePBb8V1V+cZSH+/Nzv4d398o4nAvNZzXvJ7RIPKwFne9hYBbBbjzMigrOxqemz8
k6pwVMTN5ezq1KCvXVnZ2EPLJ5G1ZLFfQZykB7OpC2u45dl8sZbr6TcVJj+vfACL
U8qYa+0jswI30Y8RSldbGLB/w5KSiePHqh2kkAVMIFpSB2RX8HqMwksl64H+BMAy
RBqXP/QmLcZ+TCJ5j4rA9QWS1puG0XJ64a8gse+B3P161VJcSXKcLdRpnLhMgVe/
kcViVPlXwLqG4pLhKVJmvHeFY0qCbxLKjzmtyg4QFY2W86Q/p/1TxItHW3LUgNBB
CFA92Pn1+LM0v4JbERoBAxTx57lC9C+mQ7qeZLez+rJ8T6B3wss3m4+2YpTpEo+O
CLerfSvCFidZFRZUzOdHlibe1y2PNat03ev4I8u6Fs5BH0J04HouRl91+u37Z8VD
aOSyHaBp+XtBpqR3Alvp
=lbqf
-----END PGP SIGNATURE-----

[Tim Brown]

You're correct I didn't install the rippled initscript. The only thing I did with it was copy and paste it to gedit and save it to

/etc/init.d.

I thought this was what was meant by 'place the attached rippled scrit in /etc/init.d' so I'm pretty sure I haven't installed that as I'm
not sure how to.

When I run 
sudo sysv-rc-conf rippled on
I don't get any confirmation that it ran the init script but I don't get any error message. It does say ''permission denied if I don't run as sudo
but when I do, I don't get any feedback.

Although, I think I'm nearly there, I will take your advice and start smaller, and come back to the server setup. I think with the detailed
information you have provided, when I come back to it I should be pretty close to getting it running. Also you asked about if it was really
a private server that I wanted to set up. I will send you an email with what I am trying to achieve and maybe you can see if I am on the right
lines in setting up what I have in mind.

Many Thanks for you prompt and detailed responses

Tim

[Bryce a. Lynch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/11/14 04:45, Tim Brown wrote:
> You're correct I didn't install the rippled initscript. The only
> thing I did with it was copy and paste it to gedit and save it to
> /etc/init.d.

That's part of the process. I would recommend using the sample
initscript in rippled/doc/rippled.init.

> When I run sudo sysv-rc-conf rippled on

That does not run the initscript, it only sets up symlinks in the
initscript directories. If it worked you should be able to do this
and get the following output:

ls -alF /etc/rc?.d/*rippled
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc0.d/K20rippled ->
../init.d/rippled*
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc1.d/K20rippled ->
../init.d/rippled*
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc2.d/S20rippled ->
../init.d/rippled*
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc3.d/S20rippled ->
../init.d/rippled*
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc4.d/S20rippled ->
../init.d/rippled*
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc5.d/S20rippled ->
../init.d/rippled*
lrwxrwxrwx 1 root root 17 Dec 19 15:53 /etc/rc6.d/K20rippled ->
../init.d/rippled*

> I don't get any confirmation that it ran the init script but I
> don't get any error message. It does say ''permission denied if I
> don't run as sudo but when I do, I don't get any feedback.

Installing the initscript and running it are two different things. If
you run the command `sudo /etc/init.d/rippled start`, that should
start rippled.

> Although, I think I'm nearly there, I will take your advice and
> start smaller, and come back to the server setup. I think with the
> detailed information you have provided, when I come back to it I
> should be pretty close to getting it running. Also you asked about
> if it was
really

Glad I could help.

- --
Bryce

Integration Security Engineer, Ripple Labs
PGP: 0xA4364248 / A177 A590 2869 32AC E2E1 946A FAD8 98D6 A436 4248
"We see in order to move; we move in order to see."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJS+noOAAoJEPrYmNakNkJIaQkP/3+Y1TidR0PlEWGt/Gw5wjZ6
SN6XceTInNrqO5j7J97RPpvKwvJ9UXUCSKUt7yObH0IELEHwgvtdJhjweM3yjub+
/g5b/otFnzYYGORwYDQRAD0xyQ+AwUJuc5UTzVdTpY4Fla/e/z5Tagt1tvatKu34
896UdR4YadBU3IxgMHOag0avp3pUYid+7Xpp8FinJPAJJP+A8llXiCggPxH5CfL2
75Yik6GZa6feuCHog9x1ZnbfUb3qyGDliET0eRaiUFF9GdbWYnSTDs/TzsxJcTjp
T7fTbcgjnHQwZcevTRAdJthbLJ5WUdHzig8mJeoReo1ISwYFJ0ZxOhKcxWcL3FMY
XLK4xC4LEdRk9fHbPm3o2bu4oczeqzXtQFjh3qEDaQ+WIGjzv0Fkg/Om7SvYeEuR
cEDQlYBvrrN94E1cFVA00nvT5BCeFl/SBVAqchKO0S3mbX84+b30DlHbOtXchV45
EyBnXo+kMtpUWZjoCpHxtWCI7aQAQqkRtM3CjN+KcW3KLmbgpC+3uqvrh5eoOFos
QwWMjpwLmubE1q42y7rSuGnAFYkdQFfr+PSqq8mmu6nljgUe97KN2B8DALAy1aqF
f/K39fhXIeq/CmU6YuEAnspSJVSgzaBthJ8K+BsxSud8PQ/+mK10FET/QXQqh0mt
honHQFqhD95o/0XwTZdz
=Ubd+
-----END PGP SIGNATURE-----

[Dmitry]

Hello,

Aside, if you have Ubuntu or other modern Linux with upstart system, it might be easier to "install" rippled as a service by a simple upstart script 

at

/etc/init/rippled.conf

like

==========================

description "Rippled as a service"

start on runlevel [2345]

stop on runlevel [016]

exec /usr/local/bin/rippled --net --conf /etc/rippled/rippled.cfg --fg

respawn

==========================