Bug 52313 – multiple ldap-backup instances result in process getting stuck

Bug 52313 - multiple ldap-backup instances result in process getting stuck


Summary:	multiple ldap-backup instances result in process getting stuck

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 minor (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-11-05 09:23 CET by Jan Luttermann
Modified:	2020-11-05 09:23 CET (History)
CC List:	0 users

See Also:
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?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Luttermann

2020-11-05 09:23:29 CET

Calling the backup service for ldap twice on the same day results in the process getting stuck. The backup service is controlled by cron and should only run once a day. But since the script can be called by administrative users it is possible that this behavior can occur.
The reason for this Bug is that if the zip files are already generated gzip will ask the user if the files shall be overridden. But since the output of gzip will be send to /dev/null this message is never shown. gzip will block the process until it is killed or the user gives input.
Possible solution:
set the needed flag on the gzip call so that it will override the found files.