Univention Bugzilla – Full Text Bug Listing |
Summary: | UMC system diagnostic module hangs for a long time (4.3) | ||
---|---|---|---|
Product: | UCS | Reporter: | Arvid Requate <requate> |
Component: | UMC - System diagnostic | Assignee: | Arvid Requate <requate> |
Status: | CLOSED FIXED | QA Contact: | Felix Botner <botner> |
Severity: | normal | ||
Priority: | P5 | CC: | best, damrose, gohmann, klaeser, voelker, walkenhorst |
Version: | UCS 4.2 | ||
Target Milestone: | UCS 4.3-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 4: Minor Usability: Impairs usability in secondary scenarios |
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.091 | 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: | |||
Bug Depends on: | 37032 | ||
Bug Blocks: | 48002 | ||
Attachments: | Screenshot_20170907_162957.png |
Description
Arvid Requate
2017-09-07 16:40:51 CEST
While I filed this bug, an error message popped up: Notification An unknown error with status code 502 occurred while connecting to the server, please try again later. I hit "RUN SYSTEM DIAGNOSTICS" again: * First time: Works * Second time: Works * Third time: Hangs Which UCS Version / errata level? > My environment consisted of a UCS 4.2-2 Master and Backup, both with Samba/AD
> and I observed this during QA for Bug #36748.
I guess errata level 159
It's diagnostic/plugins/01_ssh_connection.py that sometimes hangs: https://github.com/paramiko/paramiko/issues/515 https://stackoverflow.com/questions/35266753/paramiko-python-module-hangs-at-stdout-read This workaround seemed to fix it for me: 8a1ef5f166 | Workaround for Python paramiko hangs 4d9067fe2e | Advisory Fixing together with Bug 45904 and Bug 45584. OK - ssh check OK - YAML Just happened on a customer system running 4.3-2 errata257. Any workaround or further troubleshooting steps? Not sure if it is helpful but pstree -achls shows: =================================================== systemd splash ├─acpid ├─agetty --noclear tty1 linux ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ ├─apache2 -k start │ └─apache2 -k start ├─atd -f ├─blkmapd ├─cron -f ├─dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation ├─dockerd -H fd:// --storage-driver=overlay --live-restore --bip=172.17.42.1/16 │ ├─docker-containe -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --shim docker-containerd-shim --runtime docker-runc │ │ ├─{docker-containe} │ │ ├─{docker-containe} │ │ ├─{docker-containe} │ │ ├─{docker-containe} │ │ ├─{docker-containe} │ │ ├─{docker-containe} │ │ ├─{docker-containe} │ │ └─{docker-containe} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ ├─{dockerd} │ └─{dockerd} ├─inetd ├─irqbalance --foreground ├─lvmetad -f ├─master -w │ ├─pickup -l -t unix -u │ ├─qmgr -l -t unix -u │ └─tlsmgr -l -t unix -u ├─memcached -m 64 -s /var/run/univention-saml/memcached.socket -u samlcgi │ ├─{memcached} │ ├─{memcached} │ ├─{memcached} │ ├─{memcached} │ ├─{memcached} │ └─{memcached} ├─memcached -m 64 -p 11211 -u memcache -l 127.0.0.1 │ ├─{memcached} │ ├─{memcached} │ ├─{memcached} │ ├─{memcached} │ ├─{memcached} │ └─{memcached} ├─named -c /etc/bind/named.conf.samba4 -f -d 0 │ ├─{named} │ ├─{named} │ ├─{named} │ └─{named} ├─nmbd -D │ └─nmbd -D ├─nrpe -c /etc/nagios/nrpe.cfg -f ├─nscd │ ├─{nscd} │ ├─{nscd} │ ├─{nscd} │ ├─{nscd} │ ├─{nscd} │ ├─{nscd} │ └─{nscd} ├─ntpd -p /var/run/ntpd.pid -g -u 114:123 │ └─{ntpd} ├─python2.7 -W ignore /usr/lib/pymodules/python2.7/univention/s4connector/s4/main.py ├─rpc.gssd ├─rpc.idmapd ├─rpc.mountd --manage-gids --port 32767 ├─rpcbind -f -w ├─rsyslogd -n │ ├─{in:imklog} │ ├─{in:imuxsock} │ └─{rs:main Q:Reg} ├─runsvdir -P /etc/service log: ........................................................................................................................................................................................................................................................................................................................................................................................................... │ ├─runsv univention-directory-notifier │ │ └─univention-dire -o -d 1 -F │ └─runsv univention-directory-listener │ └─univention-dire -F -d 2 -b dc=domain,dc=com -m /usr/lib/univention-directory-listener/system -c /var/lib/univention-directory-listener -ZZ -x -D cn=admin,dc=domain,dc=com -y /etc/ldap.secret ├─samba -D │ ├─samba -D │ │ └─samba -D │ │ └─smbd -D --option=server role check:inhibit=yes --foreground │ │ ├─cleanupd -D --option=server role check:inhibit=yes --foreground │ │ ├─lpqd -D --option=server role check:inhibit=yes --foreground │ │ └─smbd-notifyd -D --option=server role check:inhibit=yes --foreground │ ├─samba -D │ ├─samba -D │ ├─samba -D │ │ └─samba -D │ ├─samba -D │ ├─samba -D │ ├─samba -D │ ├─samba -D │ │ └─samba -D │ │ └─winbindd -D --option=server role check:inhibit=yes --foreground │ │ └─winbindd -D --option=server role check:inhibit=yes --foreground │ ├─samba -D │ ├─samba -D │ └─samba -D ├─slapd -h ldapi:/// ldap://:7389/ ldaps://:7636/ │ ├─{slapd} │ ├─{slapd} │ ├─{slapd} │ ├─{slapd} │ └─{slapd} ├─sshd -D │ ├─sshd │ │ └─bash │ │ └─pstree -alhcs │ └─sshd │ └─sftp-server ├─stunnel4 /etc/stunnel/univention_saml.conf ├─systemd-journal ├─systemd-logind ├─systemd-udevd ├─univention-mana /usr/sbin/univention-management-console-server start │ └─univention-mana /usr/sbin/univention-management-console-module -m diagnostic -s /var/run/univention-management-console/29243-1538126911743.socket -d 2 -l en_US.UTF-8 │ ├─{univention-mana} │ ├─{univention-mana} │ └─{univention-mana} ├─univention-mana /usr/sbin/univention-management-console-web-server start │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ ├─{univention-mana} │ └─{univention-mana} └─univention-welc /usr/bin/univention-welcome-screen └─hexdump -n 96 /dev/input/event0 ================================================ Thus Bug has been fixed with <http://errata.software-univention.de/ucs/4.3/6.html> In this case the Bug should be cloned. I've done this: Bug #48002 |