Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2316947

Summary: [8.0][SMB][CTDB] Log flooding in CTDB enabled SMB clusters
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Anoop C S <anoopcs>
Component: smbAssignee: Anoop C S <anoopcs>
smb sub component: ctdb QA Contact: Mohit Bisht <mobisht>
Status: CLOSED CURRENTRELEASE Docs Contact: Rivka Pollack <rpollack>
Severity: high    
Priority: unspecified CC: cephqe-warriors, rpollack, sprabhu, vdas
Version: 8.0Keywords: External
Target Milestone: ---   
Target Release: 8.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
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.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2025-07-23 15:51:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2351689    

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.