Date   

DAOS Materials & API

Lombardi, Johann
 

Hi there,

 

Please note that the most up-to-date DAOS HLD is available here:

https://wiki.hpdd.intel.com/download/attachments/36966823/MS54_CORAL_NRE_DAOSM_HLD_v2.3_final.pdf?version=1&modificationDate=1460746910000&api=v2

 

Our intent is to refresh this document to reflect the latest developments and integrate it into the source code in the MarkDown format.

 

The source code (i.e. DAOS core, CaRT RPC layer, DAOS go binding, ...) is publicly available on github: https://github.com/daos-stack

 

As for the actual DAOS API, please check out those header files:

https://github.com/daos-stack/daos/blob/master/src/include/daos_api.h

https://github.com/daos-stack/daos/blob/master/src/include/daos_types.h

https://github.com/daos-stack/daos/blob/master/src/include/daos_array.h

 

Enjoy!

 

Cheers,

Johann

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


Is the Daos project still Active ?

Hemant Trivedi (Stellus) <hemant.t1@...>
 

Hello,

 

I saw a talk on DAOS few months ago by Mr. Kalyana Chadalavada .  I would like to explore the project and do a test installation,  however I do not see any recent activity on Github.  

 

I would greatly appreciate if you can give me some idea as to whether this is still in active development or the project has been archived.

 

Thank You

 

Hemant Trivedi


Re: Is the Daos project still Active ?

Olivier, Jeffrey V
 

Hi Hemant,

 

It is still under heavy development.   We are in the process of migrating to GitHub as our primary repository but as of now, we manually sync our internal repository periodically with the one in GitHub and it simply hasn’t been done for a month or so.

 

Thanks,

Jeff

 

From: daos@daos.groups.io [mailto:daos@daos.groups.io] On Behalf Of Hemant Trivedi (Stellus)
Sent: Wednesday, May 2, 2018 2:15 PM
To: daos@daos.groups.io
Subject: [daos] Is the Daos project still Active ?

 

Hello,

 

I saw a talk on DAOS few months ago by Mr. Kalyana Chadalavada .  I would like to explore the project and do a test installation,  however I do not see any recent activity on Github.  

 

I would greatly appreciate if you can give me some idea as to whether this is still in active development or the project has been archived.

 

Thank You

 

Hemant Trivedi


Re: Is the Daos project still Active ?

Olivier, Jeffrey V
 

Hi Hemant,

 

Our GitHub repo has been updated with the latest patches now.

 

Thanks,

Jeff

 

From: daos@daos.groups.io [mailto:daos@daos.groups.io] On Behalf Of Olivier, Jeffrey V
Sent: Wednesday, May 2, 2018 2:34 PM
To: daos@daos.groups.io
Cc: Olivier, Jeffrey V <jeffrey.v.olivier@...>
Subject: Re: [daos] Is the Daos project still Active ?

 

Hi Hemant,

 

It is still under heavy development.   We are in the process of migrating to GitHub as our primary repository but as of now, we manually sync our internal repository periodically with the one in GitHub and it simply hasn’t been done for a month or so.

 

Thanks,

Jeff

 

From: daos@daos.groups.io [mailto:daos@daos.groups.io] On Behalf Of Hemant Trivedi (Stellus)
Sent: Wednesday, May 2, 2018 2:15 PM
To: daos@daos.groups.io
Subject: [daos] Is the Daos project still Active ?

 

Hello,

 

I saw a talk on DAOS few months ago by Mr. Kalyana Chadalavada .  I would like to explore the project and do a test installation,  however I do not see any recent activity on Github.  

 

I would greatly appreciate if you can give me some idea as to whether this is still in active development or the project has been archived.

 

Thank You

 

Hemant Trivedi


DAOS User Group Meeting Announcement for SC18

Neitzel, Bryon S <bryon.s.neitzel@...>
 

Greetings, 

 

Please join us at the 2nd annual DAOS User Group meeting to be held at SC18 on Wednesday, November 14 from 4pm CST - 5:30pm.  This will be held at One Intel Station, located in Union Station Dallas, 400 South Houston Street.

 

We are in the process of developing the agenda, which so far includes a development and roadmap update, a middleware support discussion, deployment use cases and an open discussion.  We would welcome any other suggestions for topics to cover. If you would like to present a specific topic, please connect with us to be added to the agenda.

 

There will be an Intel sponsored happy hour from 5-7 that evening at the same location.  Feel free to stay after the meeting and join us for a drink and/or snack.

 

Please forward this invitation to anyone we may have missed, or anyone you think might want to attend.  This meeting is open to everyone.

 

We’re looking forward to seeing you there!

 

Best regards,

 

Bryon Neitzel

Director, Extreme Storage Architecture and Design Division (ESAD)

bryon.s.neitzel@...

 

Johann Lombardi 

Principal Engineer ESAD

johann.lombardi@...

 

 


DAOS User Group Meeting Announcement for SC18 - Updated Agenda

Neitzel, Bryon S <bryon.s.neitzel@...>
 

Greetings, 

 

Please join us at the 2nd annual DAOS User Group meeting to be held at SC18 on Wednesday, November 14 from 4pm CST - 5:30pm.  This will be held at One Intel Station (OIS) in the Station Master’s Lounge, located in Union Station Dallas, 400 South Houston Street.

 

 

Please find below the current agenda :

  • 4:00 Welcome/Opening Remarks, Bryon Neitzel, Intel
  • 4:05 DAOS Development Update, Johann Lombardi, Intel
  • 4:35 HDF5 DAOS VOL Plugin, Elena Pourmal, The HDF Group
  • 5:00 DAOS@Argonne, Kevin Harms, Argonne National Laboratory
  • 5:20 Open Discussion (feedback, next event, ...)

 

Future agenda updates will be posted here: http://daos.io/display/DC/DUG18

 

There will be an Intel sponsored happy hour from 5-7 that evening  in the Intel reCharge Lounge at the same facility.  Feel free to stay after the meeting and join us for a drink and/or snack.

 

Please forward this invitation to anyone we may have missed, or anyone you think might want to attend.  This meeting is open to everyone.

 

We’re looking forward to seeing you there!

 

Best regards,

 

Bryon Neitzel

Director, Extreme Storage Architecture and Design Division (ESAD)

bryon.s.neitzel@...

 

Johann Lombardi 

Principal Engineer ESAD

johann.lombardi@...

 


DUG'18 Presentations

Lombardi, Johann
 

Greetings,

 

Thank you for attending the DUG last week. I hope you enjoyed it and look forward to seeing you at the next event. The presentations have been posted to the DAOS wiki and can be accessed through this link - http://daos.io/display/DC/DUG18

 

Best regards,

Johann

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


Test #chat

Harms, Kevin
 

A new chat has been created:

Testing this chat feature.

View/Join This Chat


what's the RAS system in daos #chat

wuhao16@...
 

what RAS system is used in daos? I didn't find any document about it. 


Re: what's the RAS system in daos #chat

Lombardi, Johann
 

Hi there,

 

We use the SWIM protocol that is now integrated in CaRT (see https://github.com/daos-stack/cart/tree/master/src/swim). The implementation is based on the SSG software developed by Argonne. The integration with DAOS (i.e. automatic eviction when a server is reported as dead) is still in progress.

 

We have some internal documentation that hasn’t been released publicly yet.

Some useful links meanwhile:

https://www.mcs.anl.gov/research/projects/mochi/files/2016/11/ssnyder-mochi-ssg-jlesc.pdf

http://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf

https://press3.mcs.anl.gov//summerofcodes2015/files/2015/07/Snyder-swim.pdf

 

Cheers,
Johann

 

From: <daos@daos.groups.io> on behalf of "wuhao16@..." <wuhao16@...>
Reply-To: "daos@daos.groups.io" <daos@daos.groups.io>
Date: Thursday, 17 January 2019 at 08:39
To: "daos@daos.groups.io" <daos@daos.groups.io>
Subject: [daos] what's the RAS system in daos #chat

 

what RAS system is used in daos? I didn't find any document about it. 

 

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


Community chat on Gitter

Lombardi, Johann
 

Hi there,

 

I have created a public chat room on Gitter (search for daos/community) for DAOS users and developers to exchange.

Here is the full link:

https://gitter.im/daos-storage/community?utm_source=share-link&utm_medium=link&utm_campaign=share-link

 

Anyone is welcome to join.

 

Cheers,

Johann

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


Introduction of daos_agent to workflow

Quigley, David
 

Hello All,

 

I wanted to provide an update to the addition of DAOS Agent. As of this afternoon a pull request was merged to require the use of daos_agent. It modifies pool connect to pass a security credential obtained from daos_agent instead of the euid and egid provided by the application itself. This means everything from a sample DAOS deployment to the running of daos_test will require an instance of daos_agent to be running on any computer acting as a client.

 

Applications using the daos client library communicate with daos_agent via a UNIX domain socket. This socket exists under /var/run/daos_agent. On modern systems /var/run is not writable by normal users so to handle this several methods are described in doc/quickstart.md on how to resolve the problem. The easiest of them is to use the tempfiles.d support found in systemd enabled systems to make the necessary changes permanent. The steps below will allow daos_agent to be started as a regular user.

 

To tell systemd to create the necessary directories for DAOS:

- Copy the file utils/systemd/daosfiles.conf to /etc/tmpfiles.d (cp utils/systemd/daosfiles.conf /etc/tmpfiles.d)

- Modify the copied file to change the user and group fields (currently daos) to the user daos_agent will be run as

- Reboot the system and the directories will be created automatically on all subsequent reboots.

 

Once this is done daos_agent can be started from within the install directory generated by the DAOS build or in any installed location. The agent does not require elevated permissions so as long as the user starting the agent matches the user specified in the daosfiles.conf file used then it should have necessary access to the sockets directory.

 

If you choose to use a non-default directory that is fully under the control of your user via one of the other methods specified in doc/quickstart.md you must inform the client library where the new socket directory is. This is done by setting the environment variable DAOS_AGENT_DRPC_SOCK_ENV. This includes the full directory and the name of the socket which is agent.sock. This means if the directory daos_agent is using for its sockets is /tmp/agent the environment variable would be set to /tmp/agent/agent.sock.

 

 

 

 

 


Change to Non-default dRPC socket locations

Quigley, David
 

Hello Everyone,

 

With the merging of “DAOS-2268 dRPC: Change dRPC Environment Variable to only take directory” the method for specifying an alternate socket location for DAOS client dRPC connections has changed. Initially the DAOS_AGENT_DRPC_SOCK environment variable required the full path of the socket including the socket name. This provided an opportunity to make a mistake by omitting the agent.sock at the end of the socket name. Since the name of the socket is not changeable this put an undue burden on users. This patch changes the DAOS client library environment variable used to DAOS_AGENT_DRPC_DIR and only requires the directory be passed in. This means if –runtime_dir /tmp/daos_agent was passed to daos_agent the socket would be created under /tmp/daos_agent/agent.sock. To convey this to a DAOS client library program the user would now export DAOS_AGENT_DRPC_DIR /tmp/daos_agent . This is then internally turned into the socket path used by the agent. If you have any questions of problems please feel free to contact me.

 

Dave


DAOS Documentation

Lombardi, Johann
 

Hi there,

 

Please note initial versions of the DAOS admin guide [1] and internals documentation [2] are available online.

The next steps are:

  • integrating the admin guide into the source code in markdown format under doc/admin/.
  • filling the gaps in both documents.
  • exposing both documents via GitHub pages.

 

Best regards,

Johann

 

[1] https://wiki.hpdd.intel.com/display/DC/Operations+Manual

[2] https://github.com/daos-stack/daos/blob/master/src/README.md

 

 

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


changes in specifying environment variables for daos_server

Nabarro, Tom
 

Since the following commit on master;

 

commit 6869dec1e527e4f9204871d9d4d907aee23f71e5

Author: Tom Nabarro <tom.nabarro@...>

Date:   Fri May 10 22:27:55 2019 +0100

 

    DAOS-2409 control: stop passing I/O server env vars from shell (#452)

 

    Configuration parameters should be provided in the server config file

    which can be passed to daos_server with the "-o" option.

 

    Environment variable values set in the users shell will now not be

    passed into the daos_io_server's environment when forking.

 

    Signed-off-by: Tom Nabarro <tom.nabarro@...>

 

the following has changed:

-          a populated server configuration file is required when running daos_server and is either

o   supplied using "-o" daos_server commandline option or

o   found in default location <daos_install_dir>/etc/daos_server.yml

-          some environment variables can only be supplied to daos_io_server instances through the server config file

o   CRT_PHY_ADDR_STR, OFI_INTERFACE, OFI_PORT, D_LOG_MASK, D_LOG_FILE

-          other environment variables can be specified in config file as "key=value" strings in the per-server "env_vars" list

o   these environment variables will be applied to the daos_io_server environment overriding any specified in the environment used to launch daos_io_server (e.g. using "-x" orterun option)

-          whilst it is very highly recommended to use the server config file as a means to supply parameters, environment variables not applied through the config file but specified in the calling environment will still be present in the environment used to launch daos_io_server

 

further information:

-          daos/utils/config/daos_server.yml - commented configuration file detailing each parameter

-          daos/utils/config/examples/daos_server*.yml - example configuration files for common usage

 

Best regards,

Tom Nabarro BEng (hons)

Extreme Storage Architecture & Development

Intel Corporation

E: tom.nabarro@...

M: +44 (0)7786 260986

Skype: tom.nabarro

 

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


failed to create pool: -1023 #chat

Shengyu SY19 Zhang
 

Can someone help me to run the project, I would like to learn and join to the development work.
Currently I'm facing an issue mentioned in the tittle, code using the newest commit of master branch.

server:
orterun--allow-run-as-root -np 1 --host 192.168.88.11 --enable-recovery --report-uri uuu -v daos_server
client:
export OFI_INTERFACE=ib1
export CRT_PHY_ADDR_STR="ofi+sockets"
orterun --allow-run-as-root -v -np 1 --host 192.168.88.11 --ompi-server file:/root/daos/uuu dmg create --size=1G --nvme=1G

error:failed to create pool: -1023


Re: failed to create pool: -1023 #chat

Liu, Xuezhao
 

Hi,
-1023 is DER_PMIX, that commonly due to your ompi/pmix building/usage is incorrect.
You may check "which orterun" to see if the orterun path is the one built by DAOS package.
and for server loading cmd line, at least you need "--report-uri /root/daos/uuu" to allow the dmg client can hook with it (by --ompi-server option).


Re: [External] Re: [daos] failed to create pool: -1023 #chat

Shengyu SY19 Zhang
 

Hello,

 

Thank you for your help, since the ompi/pmix is depends projects of daos, I didn’t touch them, just follow quick-start in github, to build and run it.

I enter the path _build.external/ompi and pmix,  and then make && make install, all finished successfully.

For report-uri, since I’m running daos server in the /root/daos, I can see the uri file was created and can see the content, therefor just specify full path for the client, seems connection between client and server is OK (if I specify wrong, or nic not started, there is another error).

And also if I run: daosctl create-pool testpool, will get the same issue.

So I’m wondering where the problem is.

There are some information in the logs:

PMIx_Lookup group daos_server failed, rc: -46, value.type 0.
crt_pmix_attach group daos_server failed, rc: -1023.

 

 

Best Regards

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of xuezhao.liu@...
Sent: Thursday, June 20, 2019 4:08 PM
To: daos@daos.groups.io
Subject: [External] Re: [daos] failed to create pool: -1023 #chat

 

Hi,
-1023 is DER_PMIX, that commonly due to your ompi/pmix building/usage is incorrect.
You may check "which orterun" to see if the orterun path is the one built by DAOS package.
and for server loading cmd line, at least you need "--report-uri /root/daos/uuu" to allow the dmg client can hook with it (by --ompi-server option).


Re: [External] Re: [daos] failed to create pool: -1023 #chat

Lombardi, Johann
 

Hi,

 

First of all, please note that we are in the process of implementing our own wire-up protocol that will eventually allow us to start the DAOS server on each storage node independently. At that point, we won’t require opmi/pmix any longer and will be able to start the DAOS servers via systemd, kubernetes or any parallel launchers (e.g. pdsh, …). This feature will be available this summer.

 

Meanwhile, it would be great to see the output of the orterun … daos_server" command. I suspect that the backend storage hasn’t been formatted and the data plane not started yet. Could you please file a ticket on https://jira.hpdd.intel.com and attach the daos_server output? Thanks.

 

Cheers,

Johann

 

From: <daos@daos.groups.io> on behalf of Shengyu SY19 Zhang <zhangsy19@...>
Reply-To: "daos@daos.groups.io" <daos@daos.groups.io>
Date: Thursday 20 June 2019 at 10:35
To: "daos@daos.groups.io" <daos@daos.groups.io>
Subject: Re: [External] Re: [daos] failed to create pool: -1023 #chat

 

Hello,

 

Thank you for your help, since the ompi/pmix is depends projects of daos, I didn’t touch them, just follow quick-start in github, to build and run it.

I enter the path _build.external/ompi and pmix,  and then make && make install, all finished successfully.

For report-uri, since I’m running daos server in the /root/daos, I can see the uri file was created and can see the content, therefor just specify full path for the client, seems connection between client and server is OK (if I specify wrong, or nic not started, there is another error).

And also if I run: daosctl create-pool testpool, will get the same issue.

So I’m wondering where the problem is.

There are some information in the logs:

PMIx_Lookup group daos_server failed, rc: -46, value.type 0.
crt_pmix_attach group daos_server failed, rc: -1023.

 

 

Best Regards

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of xuezhao.liu@...
Sent: Thursday, June 20, 2019 4:08 PM
To: daos@daos.groups.io
Subject: [External] Re: [daos] failed to create pool: -1023 #chat

 

Hi,
-1023 is DER_PMIX, that commonly due to your ompi/pmix building/usage is incorrect.
You may check "which orterun" to see if the orterun path is the one built by DAOS package.
and for server loading cmd line, at least you need "--report-uri /root/daos/uuu" to allow the dmg client can hook with it (by --ompi-server option).

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


Re: [External] Re: [daos] failed to create pool: -1023 #chat

Shengyu SY19 Zhang
 

Hello Johann,

 

Since there is no nvdimm on my system, I’m using tempfs mountted to /mnt/daos as described in the document, and nvme is leaving unformatted, it is using via SPDK.

I can’t post file on the jira, I haven’t got a portal to register on it.

Here is the outpus of the server side :

 

2019/06/20 18:18:12 config.go:108: debug: DAOS config read from /usr/local/etc/daos_server.yml

2019/06/20 18:18:12 config.go:144: debug: Active config saved to /usr/local/etc/.daos_server.active.yml (read-only)

2019/06/20 18:18:12 config.go:353: debug: Switching control log level to DEBUG

2019/06/20 18:18:12 config.go:368: debug: daos_server logging to file /tmp/daos_control.log

Starting SPDK v18.07-pre / DPDK 18.02.0 initialization...

[ DPDK EAL parameters: spdk -c 0x1 --file-prefix=spdk1929786431 --base-virtaddr=0x200000000000 --proc-type=auto ]

EAL: Detected 20 lcore(s)

EAL: Auto-detected process type: PRIMARY

EAL: No free hugepages reported in hugepages-1048576kB

EAL: Multi-process socket /var/run/.spdk1929786431_unix

EAL: Probing VFIO support...

EAL: VFIO support initialized

EAL: PCI device 0000:03:00.0 on NUMA socket 0

EAL:   probe driver: 8086:953 spdk_nvme

EAL:   using IOMMU type 1 (Type 1)

EAL: PCI device 0000:05:00.0 on NUMA socket 0

EAL:   probe driver: 8086:953 spdk_nvme

no NVDIMMs found!

waiting for storage format on server 0

 

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of Lombardi, Johann
Sent: Thursday, June 20, 2019 6:01 PM
To: daos@daos.groups.io
Subject: Re: [External] Re: [daos] failed to create pool: -1023 #chat

 

Hi,

 

First of all, please note that we are in the process of implementing our own wire-up protocol that will eventually allow us to start the DAOS server on each storage node independently. At that point, we won’t require opmi/pmix any longer and will be able to start the DAOS servers via systemd, kubernetes or any parallel launchers (e.g. pdsh, …). This feature will be available this summer.

 

Meanwhile, it would be great to see the output of the “orterun … daos_server" command. I suspect that the backend storage hasn’t been formatted and the data plane not started yet. Could you please file a ticket on https://jira.hpdd.intel.com and attach the daos_server output? Thanks.

 

Cheers,

Johann

 

From: <daos@daos.groups.io> on behalf of Shengyu SY19 Zhang <zhangsy19@...>
Reply-To: "daos@daos.groups.io" <daos@daos.groups.io>
Date: Thursday 20 June 2019 at 10:35
To: "daos@daos.groups.io" <daos@daos.groups.io>
Subject: Re: [External] Re: [daos] failed to create pool: -1023 #chat

 

Hello,

 

Thank you for your help, since the ompi/pmix is depends projects of daos, I didnt touch them, just follow quick-start in github, to build and run it.

I enter the path _build.external/ompi and pmix,  and then make && make install, all finished successfully.

For report-uri, since Im running daos server in the /root/daos, I can see the uri file was created and can see the content, therefor just specify full path for the client, seems connection between client and server is OK (if I specify wrong, or nic not started, there is another error).

And also if I run: daosctl create-pool testpool, will get the same issue.

So Im wondering where the problem is.

There are some information in the logs:

PMIx_Lookup group daos_server failed, rc: -46, value.type 0.
crt_pmix_attach group daos_server failed, rc: -1023.

 

 

Best Regards

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of xuezhao.liu@...
Sent: Thursday, June 20, 2019 4:08 PM
To: daos@daos.groups.io
Subject: [External] Re: [daos] failed to create pool: -1023 #chat

 

Hi,
-1023 is DER_PMIX, that commonly due to your ompi/pmix building/usage is incorrect.
You may check "which orterun" to see if the orterun path is the one built by DAOS package.
and for server loading cmd line, at least you need "--report-uri /root/daos/uuu" to allow the dmg client can hook with it (by --ompi-server option).

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

1 - 20 of 1664