Bug 2316947 - [8.0][SMB][CTDB] Log flooding in CTDB enabled SMB clusters
Summary: [8.0][SMB][CTDB] Log flooding in CTDB enabled SMB clusters
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: smb
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 8.1
Assignee: Anoop C S
QA Contact: Mohit Bisht
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2351689
TreeView+ depends on / blocked
 
Reported: 2024-10-07 13:07 UTC by Anoop C S
Modified: 2025-05-27 15:18 UTC (History)
4 users (show)

Fixed In Version: python-sambacc-0.1~528.g282b0b9-1.el9
Doc Type: Bug Fix
Doc Text:
.`ctdb` logs no longer flood the system logs Previously, the `ctdb` log level was erroneously set to DEBUG. As a result, the system logs were flooded with `ctdb` logs. With this fix, the debug level is set with the default values, as specified by the man pages, and no longer flood the system logs.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-9928 0 None None None 2024-10-07 13:07:36 UTC

Description Anoop C S 2024-10-07 13:07:19 UTC 
Description of problem:
systemd journal is flooded with logs from ctdbd as follows:

 ../../ctdb/server/ctdb_server.c:206 ctdb request 98 of type 8 length 48 from node 0 to 0
 ../../ctdb/server/ctdb_daemon.c:1037 client request 62 of type 7 length 64 from node 0 to 4026531841
 ../../ctdb/server/ctdb_server.c:206 ctdb request 167 of type 7 length 64 from node 0 to 0
 ../../ctdb/server/ctdb_server.c:206 ctdb request 167 of type 8 length 93 from node 0 to 0
 ../../ctdb/server/ctdb_daemon.c:1037 client request 63 of type 7 length 64 from node 0 to 4026531841
 ../../ctdb/server/ctdb_server.c:206 ctdb request 168 of type 7 length 64 from node 0 to 0
 ../../ctdb/server/ctdb_server.c:206 ctdb request 168 of type 8 length 48 from node 0 to 0
 ../../ctdb/server/ctdb_daemon.c:1037 client request 64 of type 7 length 71 from node 0 to 4026531841
 ../../ctdb/server/ctdb_server.c:206 ctdb request 169 of type 7 length 71 from node 0 to 0
 ../../ctdb/server/ctdb_server.c:206 ctdb request 169 of type 8 length 48 from node 0 to 0
 ../../ctdb/server/ctdb_daemon.c:1037 client request 65 of type 7 length 64 from node 0 to 4026531841
 ../../ctdb/server/ctdb_server.c:206 ctdb request 170 of type 7 length 64 from node 0 to 0
 ../../ctdb/server/ctdb_server.c:206 ctdb request 170 of type 8 length 80 from node 0 to 0
 ../../ctdb/server/ctdb_daemon.c:1037 client request 66 of type 7 length 64 from node 0 to 4026531841
 ../../ctdb/server/ctdb_server.c:206 ctdb request 171 of type 7 length 64 from node 0 to 0
 ../../ctdb/server/ctdb_server.c:206 ctdb request 171 of type 8 length 48 from node 0 to 0


Version-Release number of selected component (if applicable):
# ceph version
ceph version 19.2.0-2.el9cp (30adc55fde86858d2b57ac6b28f344920197c5fb) squid (stable)

How reproducible:
Always

Steps to Reproduce:
Deploy a CTDB enabled SMB cluster and watch systemd journal for ctdbd.

Actual results:
Flooding of log entries.

Expected results:
Minimal logging.
Note You need to log in before you can comment on or make changes to this bug.