Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Lumons117 opened this issue May 20, 2024 · 11 comments
Open
Assignees
Labels

Comments

@Lumons117
Copy link

Lumons117 commented May 20, 2024

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 9446WARNING ~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
Copy link
Collaborator

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

@Lumons117
Copy link
Author

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

@Lumons117
Copy link
Author

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
Copy link
Collaborator

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

@Lumons117
Copy link
Author

Lumons117 commented Jun 27, 2024

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

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
Copy link
Collaborator

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

@minminlittleshrimp
Copy link
Collaborator

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

@Lumons117
Copy link
Author

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

@minminlittleshrimp
Copy link
Collaborator

minminlittleshrimp commented Sep 6, 2024

Hello @Lumons117
Currently we found a small issue with dlt-control utility set log level mechanism, I will ask for an upstream later.
I will ping you to test with the fix.

@Lumons117
Copy link
Author

Hello @Lumons117 Currently we found a small issue with dlt-control utility set log level mechanism, I will ask for an upstream later. I will ping you to test with the fix.

OK, Thank yopu

@Lumons117
Copy link
Author

Hello @Lumons117 Currently we found a small issue with dlt-control utility set log level mechanism, I will ask for an upstream later. I will ping you to test with the fix.

Hello @minminlittleshrimp
Any progress for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants