MAAPI_APPLY_TRANS is telling application communication failure""

Core Engine and APIs
1

Hi Team,

We have a similar code base running in bare-metal and in container env.
We are observing the below issue related to application communication failure in our container env.
My query is how to debug the MAAPI_APPLY_TRANS api further more to get root cause.

TRACE Connected (maapi) to ConfD
TRACE MAAPI_START_USER_SESSION → CONFD_OK
TRACE MAAPI_START_TRANS → CONFD_OK
TRACE MAAPI_EXISTS /ME/PmRecordList{0} → CONFD_OK
TRACE MAAPI_CREATE /ME/PmRecordList{0} → CONFD_OK
TRACE MAAPI_EXISTS /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml} → CONFD_OK
TRACE MAAPI_CREATE /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml} → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml}/fileDataType → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml}/fileFormat → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml}/fileLocation → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml}/fileSize → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml}/objectclass → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/PmRecord{PM202205180333+000024A20220518.0318+0000-0333+0000_-job0_ME-16e4544b-023a-436b-a77c-12a95733f6c3.xml}/objectinstance → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/lastModification → CONFD_OK
TRACE MAAPI_SET_ELEM2 /ME/PmRecordList{0}/numOfPmRecords → CONFD_OK
TRACE MAAPI_APPLY_TRANS DEBUG external error - application communication failure
→ CONFD_ERR
TRACE MAAPI_STOP_TRANS → CONFD_OK
TRACE MAAPI_END_USER_SESSION → CONFD_OK

Please help with your expertise.

Regards
Nishant Kumar

2

Hi,
See the ConfD developer log (trace log level is useful here) for info on which application is not responding.

3

Hi,
Thanks for the reply.
Can you please point out (ConfD developer log) points to which file name.

we are initializing the api as debug leveel 2.

confd_init(“DU”, debug_fd, debug_level);

with this debug level we are getting the above log in client/du side which i already shared .

Regards
Nishant Kumar

4

The developer log file is configured in confd.conf.
You should check your confd.conf for information on log configuration.

You should have something like this:

<developerLog>
<enabled>true</enabled>
<file>
<enabled>true</enabled>
<name>/var/confd/log/devel.log</name>
</file>
</developerLog>
<developerLogLevel>trace</developerLogLevel>

The ConfD init debug_level is for the debug messages printed by the library you use in your applications.

5

HI ,

I am seeing the below error in devel log when the mappi apply transation was failed.

3-Jun-2022::18:15:00.829 du-oam-server-7c6d4856cc-dbgqq confd[26]: devel-cdb subscriber DU closed unexpectedly (while delivering subscription notification)

But looks like this info is not enough to get the root cause.

Regards
Nishant Kumar

6

Hi Experts,

Can you please comment, how to debug this kind of issue further.

Regards
Nishant Kumar

7

hello,

The log line you provided seems to provide the direction:

3-Jun-2022::18:15:00.829 du-oam-server-7c6d4856cc-dbgqq confd[26]: devel-cdb subscriber DU closed unexpectedly (while delivering subscription notification)

You need to check your external CDB subscription app mentioned on the log line - and its logs - what it was doing, whether it crashed or did something unexpected while communicating with ConfD - e.g. it closed socket, or didn’t call cdb_sync_subscription_socket at the end of processing subscription etc.

8

Thanks team for your support.
I will check above prospective from application side.