01:25:03 <Smithx10> I've got a CN that  allows me to ipmi in... type the username and pw but then just hangs witha. blinking cursor 
01:25:19 <Smithx10> its in "unknown" state in cnapi 
01:25:28 <Smithx10> Guessing I should NMI it?
01:26:20 <jbk> and can't ssh to it?
01:27:01 <Smithx10> jbk and danmcd  https://paste.ec/paste/Gy+EAJT-#xGi7Kr1iTRcG64TPxfkCpjM1TvImNCSij2ZjeLHXdWc
01:27:10 <bahamat> Smithx10: You can try sdc-oneachnode for some diagnostics.
01:27:13 <Smithx10> looks like LX might be at play here 
01:27:24 <Smithx10> I NMI'd it its dumping now
01:27:43 <bahamat> Though, IME, a CN that's in that situation is often having a problem with either the pool or it's completely out of memory and can't fork.
01:28:57 <Smithx10> adminui stated:  64.8 GB PROVISIONABLE 586.9 GB PROVISIONED. 115 GB RESERVED
01:29:37 <Smithx10> but I was running a Gitlab Stress Test.  and 3 of 6 nodes were on that 1 CN
01:30:19 <Smithx10> I am running the Gitaly Processes a GO gRPC  application that writes git repositories to disk 
01:32:45 <Smithx10> Dump is at 60% should have a core for someone shortly
01:46:29 <Smithx10> lol.... ever see this in ipmi?  https://paste.ec/paste/G5a5k9Ct#xG7ZK7CWtYACzRvsDDKmcdM6tWCBgKAqWtjkmQEp2A-
01:56:22 <Smithx10> Think I just made a boo boo
01:56:49 <Smithx10> I ctrl + r ipmi and hit enter enter after it came back up to ipmi in again.... and NMI'd it again 
01:57:05 <Smithx10> is it going to have  both dumps or am I sol?
01:57:41 <Smithx10> I do see this in dumpadm https://paste.ec/paste/JgtsR+gE#VY3dZ4inH+6b2RuhR0bz002t6OBmGdHOGuEqb+iRl8C
01:58:29 <Smithx10> :( 
01:58:48 <Smithx10> its only 8gbs so I think im SoL
02:02:35 <jbk> dump vol?
02:08:14 <chewyrobbo> Here's the 2factor instructions for SmartOS: https://docs.tritondatacenter.com/public-cloud/getting-started/2fainstances
19:45:24 <Smithx10> ran into this in haproxy in an lx container https://gist.github.com/Smithx10/a5e7a782bd5b51e4c2c6bd41f7e8eb10
20:26:56 <jbk> Smithx10: bug with openssl?
20:28:23 <Smithx10> not sure
20:28:48 <jbk> the stacks (from a quick glance) suggest some locking issue in libcrypto
20:29:05 <jbk> but that's just from a very quick glance
20:29:08 <jbk> so might be wrong
22:05:08 <Smithx10> jperkin:  Proxy 'http_in': unable to set SSL cipher list to 'PROFILE=SYSTEM' for bind '*:443' at [/opt/local/etc/haproxy.cfg:61].  setting a cert in haproxy is erroring with this,  any ideas?
22:08:52 <Smithx10> ahhh never mind :( ./doh