Catapult Server


#1

Building a catapult server is difficult.
Even if build it, it can not be executed.

Please tell me the correct procedure.
We want to summarize knowledge with this thread.

Beneficial information
・Build



・Execution

・Build START(Japanese)


#2

What error do you get?


#3

The challengers are failing across the board.
First of all, I hope the core team will release the recommended procedure.


#4

What do you mean?


#5

You need to provide appropriate instruction which people can follow.
People don’t even know which version of software to use.
I saw lots of complaints on twitter.


#6

Many Japanese engineers are challenging. And everyone failed to build.
This is due to a description of the procedure that is not very friendly.

Some people have succeeded in building, but no one has Run up the server yet.


#7

What are the procedure after building it?
Apparently several executable files have been generated but what should we do before execute them?
It’s lacking necessary information.


#8

you need nemesis block and you need network description inside peers, currently we’re not helping with that. TB will probably be releasing ready to use system, where you’ll be able to play with network.


#9

There is a report that RUN has succeeded.
For your reference


#10

#11

Congratulations! :slight_smile:


#12
  1. What platform are you building on? We have not needed to link lpthread explicitly for any of our platforms so far.
  2. You probably have figured this out already, but there is a publish build target that needs to be executed before building the tools.
  3. You can modify mijin-test.properties to create a custom nemesis block (the current one is just a placeholder). And, in fact, we have added the seed directory back into the repo (it was accidentally removed during the port from our public to private repository).
  4. You can run all our tests using ctest.

#13

#14

It with docker container.


#15

Catapult in Slackware Linux 14.2

http://isarq.com/index.php/2018/06/08/catapult-episodio-1/
http://isarq.com/index.php/2018/06/19/catapult-episodio-2/
http://isarq.com/index.php/2018/07/05/episodio-3-ejecucion-del-core-y-api-rest-de-nem-catapult-en-slackware-14-2/


#16

It is a reality the pride I feel when I see these Venezuelan compatriots, my friends, do this tremendous work !! and their great capaciades to innovate never cease to surprise me, it was an honor to have come to work with them, with the best!.
Es una realidad el orgullo que siento al ver a estos compatriotas Venezonalos, amigos mios hacer este tremendo trabajo!! y sus grandes capaciades para innovar nunca me dejan de sorpernder, fue todo un honor haber llegado a trabajar con ellos, con los mejores!!!

ISARQ… Sigan así!!!


#17

i encounter this problem when docker compose up…how to solve it?


#18

What operating system/version and which docker version are you running?

One thing to try to double check is to try a ./clean-data or ./clean-all and start from scratch to see if consistently get the same behavior


#19

running with windows 10 with latest docker

should i use linux OS instead?


#20

you have found any solution? i also encountered that error using windows 10