Jason Antonacci: Clever Guy

Noticed git clone ssh://[...] was consistently hanging on my development VM and outbound SSH connections did too.  Enabling SSH debugging, the process hung on "sign_and_send_pubkey" until interrupted via CTRL+C: $ ssh -vvv remotehost.localdomain OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013 [...] debug1: Offering RSA public key: /home/cleverguy/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 535 debug2: input_userauth_pk_ok: fp 66:...:88 debug3: sign_and_send_pubkey: RSA 66:...:88 ^C $  Googling "ssh hangs debug3: sign_and_send_pubkey:" identified Red Hat Bugzilla – Bug 890522 . Which, while closed as a duplicate for Red Hat Bugzilla – Bug 907156 , was much more useful for resolving the immediate issue.  Specifically Comment #11 , from 2014, suggested command: $ sudo kill -9 $(pidof gnome-keyring-daemon) This immediately resolved the SSH authentication hang and

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error: Property "/general/LockCommand" does not exist on channel "xfce4-session". To fix this, additional configuration needed, but no hacks. First, verify xflock4 and xfconf-query are available. $ which xflock4 xfconf-query /bin/xflock4 /bin/xfconf-query Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar.  $ sudo yum install -y xlockmore-gtk i3lock Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings. $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type  string $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string Test by running xflock4 from the command line or through the GUI.

TL;DR EMC VNX IS your grandfather's SAN Per " Using EMC VNX Storage withVMware vSphereVersion 4.0 " published 2015-JAN, does not support vSphere " Multipathing Configuration for Software iSCSI Using Port Binding " (aka MPIO). Port binding is not new, Virtzilla's whitepaper was published in 2012, but EMC likes the old days. EMC recommends "implicit assignment", which relies on the ESXi TCP/IP stack determining the correct vmkernel port based on directly connected networks.  If it is still profitable, why improve it? Unfortunately, customers pay for, and expect, an Active/Active SAN and only get half. Now get off my lawn!