Re: Message looks serious?


Wang, Di
 

If 40 does not exist, it should not be able to connect to the pool at all, I.e. it should output sth like "failed to connect to pool: …”.

These logs seems suggesting the pool connection did happen.  Would you please collect the client side daos log? (by "export D_LOG_FILE=xxx “? It might tell us what really happened. Thanks.

Thanks
WangDi
From: <daos@daos.groups.io> on behalf of Colin Ngam <cngam@...>
Reply-To: "daos@daos.groups.io" <daos@daos.groups.io>
Date: Wednesday, May 13, 2020 at 10:08 AM
To: "daos@daos.groups.io" <daos@daos.groups.io>
Subject: [daos] Message looks serious?

Greetings,

 

Executing the command:

daos pool list-cont --pool a68b3845-fe78-481e-aa84-164e851d5f52 --svc 40

 

Note that 40 does not exist.

 

We did not get an error from the daos command.

 

In the log:

 

05/13-11:57:11.02 delphi-006 DAOS[26509/26552] pool WARN src/pool/srv_target.c:1020 ds_pool_tgt_map_update() Ignore update pool a68b3845 1 -> 1

05/13-11:57:11.02 delphi-006 DAOS[26509/26552] pool WARN src/pool/srv_target.c:1020 ds_pool_tgt_map_update() Ignore update pool a68b3845 1 -> 1

05/13-11:57:11.02 delphi-006 DAOS[26509/26552] pool WARN src/pool/srv_target.c:1020 ds_pool_tgt_map_update() Ignore update pool a68b3845 1 -> 1

 

My guess is that ds_pool_tgt_map_update() should not even be called?

 

Cheers,

 

Colin

 

Join daos@daos.groups.io to automatically receive all group messages.