Hi, If you are just using the daos_server_local.yml config file and do not need an NVMe, just change the nr_hugepages: 0. This takes care of the error and starts the server.

Hi Kedar, I assume that you are passing event = NULL to daos_kv_put() and only have one operation in flight, right? In the “normal” case (i.e. no membership change, no restart), the bulk of

Hi, Yes I am running the container by the following command : $ sudo docker run -it -d --privileged --cap-add=ALL --name server -v /dev:/dev <Image ID> The exact steps I am using for the entire

If NVMe is not required then try setting "nr_hugepages: 0" in the global section of the server configuration file. Regards, Tom

Hi, The dmg format command actually connects to the server to initiate the format. In your case, the server failed to start, so the “refused connection” is expected. I assume that you are

Hi Ping, The daos_agent is actually only needed on the client nodes (where the APP runs). Please find attached some configuration files that I use on a ethernet network with the tcp provider. I

Hi I was trying to set up a simple single DAOS server. I built a docker image using the following commands: - - $ git clone https://github.com/daos-stack/daos.git - $ cd daos - $ sudo docker build

Hello DAOS community, I have a rather strange observation when working with DAOS. The DAOS client system reports way higher latency than I anticipated and am wondering if someone knows whether

Hello DAOS community, I have a rather strange observation when working with DAOS. The DAOS client system reports way higher latency than I anticipated and am wondering if someone knows whether

Hi Johann, Thank you for all the help. The master definitely worked. And I was able to get a container running. Upon running: sudo docker exec server daos_server start -o

Hi Johann, I ran the servers (Test46, Test48) and client (Test60) on different nodes. They are all running in the foreground including daos_server, and daos_agent. On each node, I press ctrl-C to

Hi Ping, Right, no endpoint configuration on the client side, the agent fetches everything (except the access points and certificate) by connecting to the servers. Are you sure that you don’t

Well, the URL on master definitely works if you use “docker build https://github.com/daos-stack/daos.git#master -f utils/docker/Dockerfile.centos.7” Johann From:<daos@daos.groups.io> on

Ok, I’ve reproduced this. The issue is the dockerfile in 1.0.1 is doing a git clone rather than a COPY to get the code, so the dockerfile is fetching the wrong data. I guess the fix would be to

Hi, Sorry for the confusion. The structure of the docker files was modified some time ago and we updated the documentation (in the source code too) accordingly, but the online github I/O pages

Hi Ashley, I ran the following 3 commands: git clone --recurse-submodules -b v1.0.1 https://github.com/daos-stack/daos.git cd daos docker build

It looks like you’re trying to use 1.0.1? I’ve just checked that out locally and there’s no reference to patchelf at all in the source tree at that point, we use it now for checking that build

Hi Ashley, Thank you so much for the response. I was in the wrong directory it seems. Although when I try now, the build stops with the following error :- [...] at include/opa_user.h

Hi Johann, I ran the exact same command: docker build https://github.com/daos-stack/daos.git#master:utils/docker \ -f Dockerfile.centos.7 -t daos My major use case of connecting my Python API with the

For testing purpose, I run the servers and agents in the foreground. I press ctrl-c to stop servers and agents. Then, I start the servers one after the other and restart all agents on servers and