The log level of individual CTIDs cannot be modified through dlt control

[Lumons117]

Hi Team

When I was using dlt control to modify the log level, I found that there were a few log levels that could not be modified. The following logs appeared:

[ 1986.994499]~DLT~ 9446~ERROR ~Failed to send data to application in dlt_daemon_user_send_log_level: Resource temporarily unavailable[ 1986.994572]~DLT~ 9446~WARNING ~Can\'t send c urrent log level as response to dlt_daemon_process_user_message_register_context for (DIAG;MPOS)

May I ask what the reason is?

dlt version: v2.18.8

[minminlittleshrimp]

Hello @Lumons117 Have you tested yet with the latest version?

[Lumons117]

Hi @minminlittleshrimp
No, the current usage version is 2.18.8. Has this issue been resolved on 2.18.10？

[Lumons117]

Hello @minminlittleshrimp I tried upgrading the DLT version to v2.18.10, but still had the same issue. The problematic CTID was registered in lib, is this the reason why the level cannot be set for DLT daemons? If yes, can you provide a solution abort this?

[minminlittleshrimp]

Hello @Lumons117 Could you provide us some further information? E.g. the scenario when this issue occurs, reproduce steps... Thank you

[Lumons117]

Hello @minminlittleshrimp The problematic CTID was registered in lib，like this

When the app is launched, this CTID will not be registered immediately. It will only be registered the first time a function in lib is called.

One more point to clarify, This lib will be called by multiple apps, which means that this CTID will be registered under multiple APIDs, and none of them can modify the log level

[minminlittleshrimp]

Hello @Lumons117 Sorry for late response. Could you kindly let us know the reproducing steps?

[minminlittleshrimp]

What is the command that you used for triggering? is it dlt-control -l ... ?

[Lumons117]

What is the command that you used for triggering? is it dlt-control -l ... ?

Hello The command I used is dlt-control -l 3 -u