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

Add log level to configuration options (feature request) #3107

Closed
atx32 opened this issue Jun 20, 2023 · 4 comments
Closed

Add log level to configuration options (feature request) #3107

atx32 opened this issue Jun 20, 2023 · 4 comments

Comments

@atx32
Copy link

atx32 commented Jun 20, 2023

Describe the issue you are experiencing

The default log level for the Samba add-on appears to be set to 2, which can fill the log with entries that a user may not need. It would be nice to have the log level be part of the configuration so users can set it to what they want.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Samba share

What is the version of the add-on?

10.0.2

Steps to reproduce the issue

Start add-on with proper configuration and view log after several hours. Example content pasted in add-on log section.

System Health information

There are currently no repairs available

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

Could not find child 269 -- ignoring
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
Could not find child 271 -- ignoring
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
Could not find child 273 -- ignoring
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
Could not find child 275 -- ignoring
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
Could not find child 277 -- ignoring
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
query_name_response: Multiple (2) responses received for a query on subnet 192.168.4.42 for name WORKGROUP<1d>.
This response was from IP 192.168.4.141, reporting an IP address of 192.168.4.141.
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
Could not find child 279 -- ignoring

Additional information

No response

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 26, 2023
@atx32
Copy link
Author

atx32 commented Jul 26, 2023

I appreciate any consideration of this feature request.

@github-actions github-actions bot removed the stale label Jul 26, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Aug 25, 2023
@atx32 atx32 changed the title Add log level to configuration options Add log level to configuration options (feature request) Aug 26, 2023
@github-actions github-actions bot removed the stale label Aug 26, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants