viabtc_exchange_server: compile error on ubuntu16.04

accesshttp compile success， accessws compile error


../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_version':
openssl.c:(.text+0xe67): undefined reference to `SSLeay'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_set_engine_default':
openssl.c:(.text+0x11c0): undefined reference to `ENGINE_set_default'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_seed.part.5':
openssl.c:(.text+0x13d9): undefined reference to `RAND_file_name'
openssl.c:(.text+0x13ef): undefined reference to `RAND_load_file'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_seed':
openssl.c:(.text+0x1498): undefined reference to `RAND_load_file'
../libs/libcurl.a(libcurl_la-openssl.o): In function `ossl_connect_step1':
openssl.c:(.text+0x23f0): undefined reference to `BIO_f_ssl'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_init':
openssl.c:(.text+0x3447): undefined reference to `OPENSSL_load_builtin_modules'
../libs/libcurl.a(libcurl_la-openssl.o): In function `servercert':
openssl.c:(.text+0x3caa): undefined reference to `OCSP_response_status'
openssl.c:(.text+0x3cbd): undefined reference to `OCSP_response_status_str'
openssl.c:(.text+0x4b24): undefined reference to `OCSP_response_get1_basic'
openssl.c:(.text+0x4b5c): undefined reference to `OCSP_basic_verify'
openssl.c:(.text+0x4ba8): undefined reference to `OCSP_resp_count'
openssl.c:(.text+0x4bbe): undefined reference to `OCSP_resp_get0'
openssl.c:(.text+0x4be3): undefined reference to `OCSP_single_get0_status'
openssl.c:(.text+0x4c07): undefined reference to `OCSP_check_validity'
openssl.c:(.text+0x4c17): undefined reference to `OCSP_cert_status_str'
openssl.c:(.text+0x4e12): undefined reference to `OCSP_crl_reason_str'

About this issue

Original URL
State: open
Created 6 years ago
Comments: 19 (9 by maintainers)

Most upvoted comments

@ohld I’m using

Docker version 18.06.0-ce, build 0ffa825.
docker-compose version 1.22.0, build f46880fe
on ubuntu18.04.1

I have solve this error, by adding RUN ["chmod", "+x", "/docker-entrypoint.sh"] in each Dockfile which has an entrypoint.

some entrypoint.sh doesn’t have permission to exec in docker container. maybe you should solve this too.

everything works fine, except for one marketprice error:

# docker-compose up marketprice
Starting exchange_redis_master ... done
Starting exchange_kafka        ... done
Starting exchange_redis_replica_2 ... done
Starting exchange_redis_replica_1 ... done
Starting exchange_sentinel_1      ... done
Starting exchange_sentinel_2      ... done
Starting exchange_sentinel_3      ... done
Starting exchange_alertcenter     ... done
Starting exchange_marketprice     ... done
Attaching to exchange_marketprice
exchange_marketprice | @=marketprice
exchange_marketprice | === marketprice is starting
exchange_marketprice | === marketprice contains redis config: "192.168.18.31:26381"
exchange_marketprice | === marketprice: sentinel addr found: 192.168.18.31:26381
exchange_marketprice | === marketprice: sentinel is up
exchange_marketprice | === marketprice contains kafka config: "192.168.18.20:9092"
exchange_marketprice | === marketprice: kafka addr found: 192.168.18.20:9092
exchange_marketprice | === marketprice: is waiting for kafka on host=192.168.18.20, port=9092 ...
exchange_marketprice | === marketprice: is waiting for kafka on host=192.168.18.20, port=9092 ...
exchange_marketprice | === marketprice: is waiting for kafka on host=192.168.18.20, port=9092 ...
exchange_marketprice | === marketprice: is waiting for kafka on host=192.168.18.20, port=9092 ...
exchange_marketprice | === marketprice: kafka is up
exchange_marketprice | === marketprice: ready to exec
exchange_marketprice | process: marketprice version: 0.1.0, compile date: Aug  8 2018 13:02:43
exchange_marketprice | ./marketprice.exe: init message fail: -361: No such file or directory
exchange_marketprice | process: marketprice version: 0.1.0, compile date: Aug  8 2018 13:02:43
exchange_marketprice | === marketprice has died, exitting docker...
exchange_marketprice exited with code 100

Bringer-of-Light on Aug 8, 2018

@Bringer-of-Light Take a look at docker swarm: https://docs.docker.com/engine/swarm/ You can join all your machines in a swarm (read the tutorial on the docker site). There is a way to deploy all dockers from your docker-compose to your swarm so different containers will be on a different machines of a swarm: https://docs.docker.com/engine/swarm/stack-deploy/#create-the-example-application

All your swarm machines will be united into a single virtual local network so your containers could communicate with each other in a private network.

ohld on Aug 8, 2018