Bug 48125 - System diagnostic module causes 502 on the webserver
System diagnostic module causes 502 on the webserver
Status: CLOSED DUPLICATE of bug 48002
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
UCS 4.3
Other Linux
: P5 normal (vote)
: UCS 4.4-1-errata
Assigned To: Jürn Brodersen
Florian Best
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-11-09 11:48 CET by Christina Scheinig
Modified: 2019-12-12 11:11 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
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.069
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018092721000521
Bug group (optional):
Max CVSS v3 score:


Attachments
test the diagnostic modules via console (1.02 KB, text/x-python)
2018-11-09 11:48 CET, Christina Scheinig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2018-11-09 11:48:43 CET
Created attachment 9731 [details]
test the diagnostic modules via console

Unfortunately debugging this issue is not a pleasure, because one module takes more then 10 minutes and then it is killed.
There is no hint in the logfile with debug level 4 for the umc modules, which module causes this problem.

Finally a script iterating over all plugin modules shows which one takes so much time.

And the customer may ignore the 502, because acknowledging the message, the  result is finally shown, but not the killed one. Maybe the customer gets the wrong security.
Comment 1 Florian Best univentionstaff 2019-11-28 10:14:10 CET
@Jürn: this is probably already fixed. What do you think?
Comment 2 Jürn Brodersen univentionstaff 2019-11-28 10:38:23 CET
(In reply to Florian Best from comment #1)
> @Jürn: this is probably already fixed. What do you think?

Yes this has been fixed in bug 48002 :)

The ticket was already added to bug 48002

*** This bug has been marked as a duplicate of bug 48002 ***
Comment 3 Florian Best univentionstaff 2019-12-12 11:11:00 CET
Yes!