2018-06-13 12:21:22 UTC - Sagar Gaur: hi to run the docker in windows 8 i just have to download docker tool box or docker software too..? ---- 2018-06-13 12:37:52 UTC - Sagar Gaur: @Ivan Kelly please could u help me out here...? ---- 2018-06-13 12:41:20 UTC - Ivan Kelly: I've never run docker on windows, so I don't know ---- 2018-06-13 15:15:22 UTC - Karthik Palanivelu: Hi, I created the broker and headless service within k8s like the broker.yaml and proxy.yaml within the codebase. Can you please help me on how to access the endpoint to post message to broker? ---- 2018-06-13 17:39:03 UTC - Karthik Palanivelu: Team, while starting proxy in k8s I am getting the below exception. Can you please help? ---- 2018-06-13 17:39:10 UTC - Karthik Palanivelu: @Karthik Palanivelu uploaded a file: <https://apache-pulsar.slack.com/files/U7VRE0Q1G/FB6TK1ERH/-.txt|Untitled> ---- 2018-06-13 18:32:13 UTC - Kevin Monchamp: @Kevin Monchamp has joined the channel ---- 2018-06-13 18:34:37 UTC - Sijie Guo: I think you need to set `brokerServiceURL` in proxy.conf in 2.0.0. @Karthikeyan Palanivelu ---- 2018-06-13 18:36:40 UTC - Sijie Guo: @Sagar Gaur
> hi to run the docker in windows 8 i just have to download docker tool box or docker software too..? you can find the docker documentation in docker website - <https://docs.docker.com/docker-for-windows/> ---- 2018-06-13 18:40:27 UTC - Matteo Merli: > I think you need to set `brokerServiceURL` in proxy.conf in 2.0.0. @Karthikeyan Palanivelu We have a fix for that coming in 2.0.1. That was one of the reason to kick out 2.0.1 early ---- 2018-06-13 18:54:35 UTC - Karthik Palanivelu: @Matteo Merli @Sijie Guo oh ok, brokerServiceURL is it ssl url or both? I am using TLS. ---- 2018-06-13 19:08:54 UTC - Sijie Guo: brokerServiceURL is the non ssl one, brokerServiceURLTLS is to set the tls one ---- 2018-06-13 20:05:20 UTC - Karthik Palanivelu: Thanks @Sijie Guo I used the hostIP as advertised address as hostname in client.conf; is it same in proxy.conf or is it `broker` as hostname due to k8s broker service? ---- 2018-06-13 20:07:41 UTC - Sijie Guo: you mean the brokerServiceURL(TLS)? It should be pointing to the DNS name of the brokers. in k8s, it should be the service name that you used for broker service. ---- 2018-06-13 20:34:58 UTC - Karthik Palanivelu: I am new to k8s and learning. In the broker.yaml headless service name is ‘broker’. Let me know if this is correct to use. ---- 2018-06-13 20:35:35 UTC - Sijie Guo: @Karthikeyan Palanivelu yes. so you service URL should be something like <pulsar://broker:6650> ---- 2018-06-13 20:36:26 UTC - Karthik Palanivelu: Thank you, let me try it. ---- 2018-06-13 22:11:14 UTC - Ivan Kelly: with 2.0.0, setting brokerServiceURL will break the binary protocol via proxy ---- 2018-06-14 02:53:08 UTC - Karthik Palanivelu: @Ivan Kelly Is it a breaking issue that I cannot proceed further or what is your recommendation? ---- 2018-06-14 07:03:40 UTC - dba: @dba has joined the channel ---- 2018-06-14 07:12:20 UTC - dba: Hi guys. Sorry for asking here, but I tried googling an answer and couldn't find one. I have two quick questions: The release of 2.0 is postfixed with "rc1", but it sounds like it is an actual release. Is it a temporary release candidate or the actual release? I see there are clients for Java, Python and C++, do you know if anyone is working on a C#/.NET client? (I know I could just use websockets :-)). ---- 2018-06-14 07:12:23 UTC - Victor Li: @Victor Li has joined the channel ---- 2018-06-14 07:15:21 UTC - Sijie Guo: @Ivan Kelly - I don’t think it will break binary protocol. if I understand the fix (<https://github.com/apache/incubator-pulsar/pull/1862>), it is impacting http protocol, if proxy sets binary protocol service url. #1862 fixes the problem. @Karthikeyan Palanivelu - I think you can set the <pulsar://broker:6650> service url to continue, although rest api through proxy might be a bit problematic. 2.0.1 is under way to be released within 1~2 days. ---- 2018-06-14 07:15:26 UTC - Victor Li: Build client-cpp with static linking failed with boost not compiling with -fPIC, does anyone know this issue? ---- 2018-06-14 07:15:48 UTC - Ali Ahmed: @dba 2.0rc1 is the official release +1 : dba ---- 2018-06-14 07:16:18 UTC - Ali Ahmed: @dba there is currently no .net client , but commits are welcome ---- 2018-06-14 07:16:34 UTC - Sijie Guo: > The release of 2.0 is postfixed with “rc1”, but it sounds like it is an actual release. Is it a temporary release candidate or the actual release? It is an actual release, the name of “rc1" is a bit confused because 2.0 is a big release, so the community decided to use rc1. 2.0.1 is under its way to be released in 1~2 days. ---- 2018-06-14 07:17:17 UTC - Ali Ahmed: @Victor Li do you have any logs ? what platform are you compiling on ? ---- 2018-06-14 07:17:21 UTC - dba: Thanks guys! :slightly_smiling_face: ---- 2018-06-14 07:18:09 UTC - Victor Li: Set STATIC_LINK to ON and run docker-build.sh ---- 2018-06-14 07:18:44 UTC - Victor Li: in the pulsar-client-cpp directory, build will fail. ---- 2018-06-14 07:20:49 UTC - Victor Li: This is the log: ```[ 39%] Linking CXX shared library libpulsar.so ... /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libboost_filesystem.a(operations.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libboost_filesystem.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status lib/CMakeFiles/pulsarShared.dir/build.make:2097: recipe for target 'lib/libpulsar.so.2.1.0-incubating-SNAPSHOT' failed``` ---- 2018-06-14 07:24:35 UTC - Victor Li: `libboost` not being compiled with -fPIC seems an old and well-known issue, however I don't want to compile the boost lib myself. Is there a workaround or a libboost version with a fix? @Ali Ahmed ---- 2018-06-14 07:26:29 UTC - Ali Ahmed: I don’t know @Matteo Merli will able to answer he should be online in the morning ---- 2018-06-14 07:27:08 UTC - Sanjeev Kulkarni: @Victor Li which os/gcc version are you compiling with ---- 2018-06-14 07:29:11 UTC - Victor Li: I was running `./docker-build.sh` which run toolchain in the docker image `apachepulsar/pulsar-build:ubuntu-16.04`. ---- 2018-06-14 07:30:09 UTC - Victor Li: and it has `libboost-all-dev` the newest version (1.58.0.1ubuntu1). ---- 2018-06-14 07:34:31 UTC - Sijie Guo: @Victor Li how do you set STATIC_LINK ? ---- 2018-06-14 07:35:28 UTC - Victor Li: in file `CMakeLists.txt`, change: ``` -option(LINK_STATIC "Link against static libraries" OFF) +option(LINK_STATIC "Link against static libraries" ON)``` ---- 2018-06-14 07:35:46 UTC - Sijie Guo: okay trying now ---- 2018-06-14 07:51:25 UTC - Fredrik: @Fredrik has joined the channel ---- 2018-06-14 07:59:18 UTC - Sijie Guo: @Victor Li I reproduced your problem. although I am not an cpp expert, have you try to add -fPIC to CMAKE_CXX_FLAGS ? ---- 2018-06-14 08:16:02 UTC - Sijie Guo: seems adding -fPIC doesn’t work. I think you might need boost 1.60.0+. but I am not sure which ubuntu version with have boost 1.60.0+ ----
