Bug 51402 - socket leak - UMC web logon (univention/management)
socket leak - UMC web logon (univention/management)
Status: CLOSED DUPLICATE of bug 50583
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Florian Best
UMC maintainers
:
Depends on:
Blocks: 51047
  Show dependency treegraph
 
Reported: 2020-06-02 16:54 CEST by Felix Botner
Modified: 2021-09-09 22:02 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.086
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

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2020-06-02 16:54:46 CEST
see Bug #51047

maybe related to Bug #51367, but the fix there did not help me, logon as Administrator leads to socket leaks as well (maybe related to the UMC udm module, could not reproduce this as normal user with umc modules)

-> lsof -p $(pidof -x univention-management-console-server)| grep 7389| wc -l
0

-> UMC Web Login (/univention/management/ - System and domain settings) 
   as Administrator; UMC Web Logout

-> lsof -p $(pidof -x univention-management-console-server)| grep 7389| wc -l
3

-> UMC Web Login (/univention/management/ - System and domain settings)
   as Administrator; UMC Web Logout

-> lsof -p $(pidof -x univention-management-console-server)| grep 7389| wc -l
4

-> UMC Web Login (/univention/management/ - System and domain settinfgs)
   as Administrator; UMC Web Logout
-> UMC Web Login (/univention/management/ - System and domain settinfgs)
   as Administrator; UMC Web Logout

-> lsof -p $(pidof -x univention-management-console-server)| grep 7389| wc -l
6

lsof -p $(pidof -x univention-management-console-server)| grep 7389
univentio 28469 root   13u  IPv4            4969851      0t0     TCP master.four.four:52650->master.four.four:7389 (ESTABLISHED)
univentio 28469 root   15u  IPv4            4969860      0t0     TCP master.four.four:52652->master.four.four:7389 (ESTABLISHED)
univentio 28469 root   16u  IPv4            4969892      0t0     TCP master.four.four:52666->master.four.four:7389 (ESTABLISHED)
univentio 28469 root   21u  IPv4            4971022      0t0     TCP master.four.four:52838->master.four.four:7389 (ESTABLISHED)
univentio 28469 root   26u  IPv4            4970458      0t0     TCP master.four.four:52750->master.four.four:7389 (ESTABLISHED)
univentio 28469 root   38u  IPv4            4971614      0t0     TCP master.four.four:52922->master.four.four:7389 (ESTABLISHED)

after a couple of minutes

lsof -p $(pidof -x univention-management-console-server)| grep 7389
univentio 28469 root   13u  IPv4            4969851      0t0     TCP master.four.four:52650->master.four.four:7389 (CLOSE_WAIT)
univentio 28469 root   15u  IPv4            4969860      0t0     TCP master.four.four:52652->master.four.four:7389 (CLOSE_WAIT)
univentio 28469 root   16u  IPv4            4969892      0t0     TCP master.four.four:52666->master.four.four:7389 (CLOSE_WAIT)
univentio 28469 root   21u  IPv4            4971022      0t0     TCP master.four.four:52838->master.four.four:7389 (CLOSE_WAIT)
univentio 28469 root   26u  IPv4            4970458      0t0     TCP master.four.four:52750->master.four.four:7389 (CLOSE_WAIT)
univentio 28469 root   38u  IPv4            4971614      0t0     TCP master.four.four:52922->master.four.four:7389 (CLOSE_WAIT)

after a couple of hours


lsof -p $(pidof -x univention-management-console-server)
univentio 28469 root   13u  sock                0,8      0t0 4969851 protocol: TCP
univentio 28469 root   15u  IPv4            4969860      0t0     TCP master.four.four:52652->master.four.four:7389 (CLOSE_WAIT)
univentio 28469 root   16u  sock                0,8      0t0 4969892 protocol: TCP
univentio 28469 root   21u  sock                0,8      0t0 4971022 protocol: TCP
univentio 28469 root   26u  sock                0,8      0t0 4970458 protocol: TCP
univentio 28469 root   38u  sock                0,8      0t0 4971614 protocol: TCP

ls -la /proc/$(pidof -x univention-management-console-server)/fd/
insgesamt 0
dr-x------ 2 root root  0 Mai 22 08:56 .
dr-xr-xr-x 9 root root  0 Mai 22 08:56 ..
lr-x------ 1 root root 64 Mai 22 08:56 0 -> /dev/null
lrwx------ 1 root root 64 Mai 22 08:56 1 -> /dev/null
lrwx------ 1 root root 64 Mai 22 08:56 13 -> socket:[4969851]
lrwx------ 1 root root 64 Mai 22 08:56 14 -> socket:[4969855]
lrwx------ 1 root root 64 Mai 22 08:56 15 -> socket:[4969860]
lrwx------ 1 root root 64 Mai 22 08:56 16 -> socket:[4969892]
lrwx------ 1 root root 64 Mai 22 08:56 2 -> /dev/null
lrwx------ 1 root root 64 Mai 22 08:56 21 -> socket:[4971022]
lrwx------ 1 root root 64 Mai 22 08:56 26 -> socket:[4970458]
lrwx------ 1 root root 64 Mai 22 08:56 3 -> /var/log/univention/management-console-server.log
lrwx------ 1 root root 64 Mai 22 08:57 38 -> socket:[4971614]
lr-x------ 1 root root 64 Mai 22 08:56 4 -> /dev/null
lrwx------ 1 root root 64 Mai 22 08:56 5 -> socket:[4969642]
lrwx------ 1 root root 64 Mai 22 08:56 6 -> /dev/null
lrwx------ 1 root root 64 Mai 22 08:56 7 -> /dev/null
Comment 2 Florian Best univentionstaff 2020-07-10 14:13:40 CEST
This is a sub-problem of Bug #50583. When the references are cleaned up the ldap connections automatically get cleaned up.
Comment 3 Florian Best univentionstaff 2020-08-03 13:15:57 CEST
This issue is resolved by fixing Bug #50583.

*** This bug has been marked as a duplicate of bug 50583 ***