Bug 33730 - Notifier and listener do not restart in correct order during ifdown
Summary: Notifier and listener do not restart in correct order during ifdown
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
Version: UCS 3.2
Hardware: Other Linux
: P4 normal
Target Milestone: UCS 3.2-x
Assignee: Listener maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-11 16:04 CET by Erik Damrose
Modified: 2017-08-08 07:11 CEST (History)
5 users (show)

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?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.006
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Troubleshooting
Customer ID:
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 Erik Damrose univentionstaff 2013-12-11 16:04:08 CET 
We ship restart scripts for notifier and listener in /etc/network/if-post-down.d/. The script names leads to them being executed in the order listener->notifier. The order should be fixed, so that the notifier is restarted ahead of the listener.

The problem is present in UCS 3.1-0e55+ and 3.2

The observed problem was, that at the end of appliance setup, both notifier and listener were restarted, but the listener could not immediately connect, which lead to a timeout of 2.5 minutes.

+++ This bug was initially created as a clone of Bug #30408 +++
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:40:44 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:11:17 CEST 
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.