Thanks for confirming those points. Yeah, I noticed that. However, the documentation suggested the above steps (https://daos-stack.github.io/admin/installation/#installing-daos-from-rpms). Using the

Hi Patrick, Supported platforms are CentOS7, OpenSUSE 15.1, and Ubuntu 20.04 Most of the testing has been on CentOS7 so far though. https://daos-stack.github.io/admin/installation/

Jeff, Currently, I'm finding many DAOS package dependencies are not in EPEL for CentOS 8. Previously (last fall), I pushed through this - finding the dependencies from other, scattered sources, which

Hi Patrick, I haven’t tried CentOS 8 but I’ve been using Fedora since version 27, now 32 and don’t recall issues encountered during the transition to python3 being the default. Can you

Yes that is the correct thing to do. The libabt* packages should not be part of the tarball. We have an internal ticket to have this rectified. It can be dropped. No. They are only needed if you

Steffen, I'll forward your questions to our packaging expert and have someone get back to you shortly. One thing I noticed is that you are using 7.8 and for the DAOS 1.0 branch we did all of our

That worked! Thanks Tom!

Sounds like maybe metadata is out of sync, can you try removing /mnt/daos0/*, starting the server and then (on a separate tty) reformatting with "dmg storage format --reformat"?

Thanks Tom, that led me to this: 07/30-08:21:08.63 elfs13o01 DAOS[74504/74524] bio INFO src/bio/bio_xstream.c:1049 bio_xsctxt_alloc() Initialize NVMe context, tgt_id:0,

Hello Richard "ERROR: DAOS I/O Server exited with error: /usr/bin/daos_io_server (instance 0) exited: exit status 1” indicates that there might be some useful information in the io_server log

Hi everyone, first, I really appreciate the availability of the RPMs for installing DAOS. This really simplifies setting up a working system. I've tried them and, in principle, succeeded to install

Richard, There's nothing obviously wrong - to me, anyway - with your config, and no useful errors in the output. You can check the logs in /tmp/daos*.log (There will be multiple files), they should

Hi all - I'm trying to set up a proof of concept daos cluster, and it is proving to be tricky. The systems have 4 SCM 128G DIMMs, and 4 U.2 NVMe drives installed. I have installed all the RPMs from

Good afternoon, Has anyone been running DAOS on CentOS 8? We tried this a while back, and had some significant issues related to 'python' referring to Python3 rather than Python2. Before we try

Hi Kevan, Yes I missed this in the latest fixes to update the DAOS & DFS drivers to the new IOR backend API changes. This PR fixes it: https://github.com/hpc/ior/pull/244 hopefully should

Apologies if this is old news, but the upstream ior master branch src/aiori-DAOS.c file does not compile cleanly, the signature apparently has changed for .get_file_size, the MPI_Comm parameter has

Hello All, We would like to announce that DAOS 1.0.1 is now generally available. One of the DAOS dependencies, log4j, has issued a security alert, so we have updated DAOS from log4j 2.11.1 to

Yes, each target has its own progress ULT to listen the request. Thanks Wangdi

Thanks WangDi. So each target on the Server is actually listening for RPC IO Requests. Thanks. Colin From: <daos@daos.groups.io> on behalf of "Wang, Di" <di.wang@...> Reply-To:

Hello, The endpoint is one target of the server, i.e. the client needs to specify both rank and target index (within that server). Thanks WangDi On 7/11/20, 3:30 PM, "daos@daos.groups.io