Bug 44716 - smbd_cleanupd_process_exited: got 0 cleanup events, expected at least 1
smbd_cleanupd_process_exited: got 0 cleanup events, expected at least 1
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.1
Other All
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-31 10:46 CEST by Dirk Ahrnke
Modified: 2019-01-03 07:20 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.011
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Ahrnke 2017-05-31 10:46:59 CEST
The report in https://help.univention.com/t/smbd-high-cpu-with-no-users/5857 looks like an occurence of https://bugzilla.samba.org/show_bug.cgi?id=12396

It should be checked whether the fix from upstream could be applied to the affected UCS packages.
Comment 1 Arvid Requate univentionstaff 2017-05-31 15:44:47 CEST
Yes that patch should apply, it's part of Samba 4.5.4 (errata4.1-4 is at samba 4.5.3 plus security patches). Since the patch only removes the log message I'm not sure that the load would be reduced significantly because it would probably not stop the loop the smbd apparently seems to be stuck in in the forum report. Anyway, I'll consider fixing this along with the next errata4.1-4 samba update.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:20:07 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.