Bug 55045 - S4-BIND startup timeout with huge/many zones
S4-BIND startup timeout with huge/many zones
Status: NEW
Product: UCS
Classification: Unclassified
Component: DNS
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-07-29 15:23 CEST by Dirk Schnick
Modified: 2022-10-13 12:04 CEST (History)
2 users (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?: 2: Will only affect a 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.046
Enterprise Customer affected?: Yes
School Customer affected?: Yes
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 Schnick univentionstaff 2022-07-29 15:23:51 CEST
On some servers of a customer the bind9 is not willing to start after the update to UCS5. After boot a manual start via systemctl start bind9.service is working.

If the timeout of /usr/lib/univention-bind/samba4 

wait-for-startup)
                /usr/bin/timeout 30 /bin/sh -c \
                        "until rndc -p 953 status | grep --quiet 'server is up and running'; do sleep 1; done"
                ;;

is increased from 30 to 60 seconds the bind service is also starting during boot.
We have a UCR for backend-ldap please introduce this timeout UCR also for samba backend.
Comment 1 Philipp Hahn univentionstaff 2022-10-13 12:00:49 CEST
See Bug #54108 comment 6:
- For "dns/backend=ldap" there is UCRV "dns/timeout-start"