Package: bash Version: 4.4-5 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I'm seeing symptoms on stretch that look a lot like a bug reported to Red Hat [1]. A bash process that is no longer associated with a TTY, but looks like it was once interactive, pegs the CPU at 100%. Since the server in question is headless, that suggests pretty strongly an orphaned SSH session. Apparently this was fixed in bash snapshots in 2017 [2], although I'm not sure how those relate to actual versions. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1589343 [2] http://git.savannah.gnu.org/cgit/bash.git/commit/lib/readline/search.c?id=8b6b8f6094f95c4282c84924d12ec411a64a1ca7 - -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-0.bpo.2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bash depends on: ii base-files 9.9+deb9u8 ii dash 0.5.8-2.4 ii debianutils 4.8.1.1 ii libc6 2.24-11+deb9u4 ii libtinfo5 6.0+20161126-1+deb9u2 Versions of packages bash recommends: ii bash-completion 1:2.1-4.3 Versions of packages bash suggests: pn bash-doc <none> - -- no debconf information -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlzBsWAACgkQ8gKXHaSn nixg8wv/dEdaihGdUV0oSm1J/tDpbjR1aC5C8w+gtPG4YUvkKpNX6SeIo9tHT4dT ZwzlslGVSwCbn3fNCLDsgODDD+tiOKHGTv2apMLei+SKyY5Tpm2+vF/UDkGO64SV rAOtVChgMnxq+wH5MJYj0D/otXWl1IAPYrMvyiG9q4zhfQ54w7Z63/mI6Vsipmoj n6G+TL5PnKtxIxj5N/wAst+SqGJgs4Tfh/KdsxE0YMUaCfQCFUrOgLvcZlNskNZW 44JynhGCb/Vhu9kcqdre6MPAcFTqnD6Q19WUQsZ1GnyBNSS6Ha6PVpIF3BV6II/h Kbjuv0JBE1f5s2B+p+Y7foCrx/lBwb8YmevAl/FtT2cUHZprjOkzpC66ongjFP5M 7CigsCisn8+OJIkH67rfNqlV57x33dR1u8N0uqAc7DN779+37XozqZ27ZkjnlgIR g8JhyIZ27OluYHgnQGxv/n4N6zOp3kSaTRRA/MwATkdS9L+CTosfaviUhPmnHyAS sRGvDQv3 =fSpQ -----END PGP SIGNATURE-----
