Bug 37342
| Summary: | Several tdbbackup processes piling up (blocked by samba) | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Arvid Requate <requate> |
| Component: | Samba4 | Assignee: | Samba maintainers <samba-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | ||
| Version: | UCS 4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| What kind of report is it?: | Bug Report | What type of bug is this?: | 1: Cosmetic issue or missing function but workaround exists |
| Who will be affected by this bug?: | 2: Will only affect a 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: | |||
| Bug Depends on: | 37343 | ||
| Bug Blocks: | |||
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you. |
In an internal UCS@school environment the Samba server was in an unusable state, blocking S4 LDAP searches: ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"} There was only one Samba process left, which apparently had refused to die during a samba restart: 4924 ? S 0:01 /usr/sbin/samba -D The issue probably has caused several tdbbackup jobs piling up: 2397 ? Ss 0:04 /usr/sbin/cron 31430 ? S 0:00 \_ /USR/SBIN/CRON 31462 ? Ss 0:00 | \_ /bin/sh -c /usr/sbin/univention-samba4-backup 31470 ? S 0:00 | \_ /bin/bash /usr/sbin/univention-samba4-backup 31531 ? S 0:00 | \_ tdbbackup ./private/sam.ldb.d/DC=NAJJAR,DC=LOCAL.ldb 22854 ? S 0:00 \_ /USR/SBIN/CRON 22892 ? Ss 0:00 | \_ /bin/sh -c /usr/sbin/univention-samba4-backup 22900 ? S 0:00 | \_ /bin/bash /usr/sbin/univention-samba4-backup 22988 ? S 0:00 | \_ tdbbackup ./private/sam.ldb.d/DC=NAJJAR,DC=LOCAL.ldb 17992 ? S 0:00 \_ /USR/SBIN/CRON 18031 ? Ss 0:00 \_ /bin/sh -c /usr/sbin/univention-samba4-backup 18038 ? S 0:00 \_ /bin/bash /usr/sbin/univention-samba4-backup 18105 ? S 0:00 \_ tdbbackup ./private/sam.ldb.d/DC=NAJJAR,DC=LOCAL.ldb Cause and effect are a bit unclear, but judging from the PIDs I would guess that samba is the culprint. Anyway, The tdbbackup processes must not pile up like that.