On 17-07-30 22:20:59, viq wrote: > On 17-07-30 22:10:43, viq wrote: > > On 17-07-30 15:50:44, Ted Unangst wrote: > > > viq wrote: > > > > > > anybody know what's going on? > > > > > > > > > > From my running salt with trace logs, it seems that salt initialises > > > > > everything, opens it's IPC sockets, initiates it's AES auth/handshake > > > > > with master, and that's when things die. > > > > > > > > Would output of ktrace/kdump be useful here? FWIW it's 24MB, 240k lines, > > > > 4.2MB compressed > > > > > > not especially. i already know *what* it does. somebody has to read the > > > code > > > to figure out why. > > > > If you tell me what to write, I could create an issue upstream. Or you > > could skip the middleman and do it at > > https://github.com/saltstack/salt/issues and let them deal with reading > > the code ;) > > https://github.com/saltstack/salt/issues/42634
As per https://github.com/saltstack/salt/issues/42634#issuecomment-320029538 this is in ZeroMQ, and currently upstream's advice is we default to TCP transport for Salt on OpenBSD - which would require switching master such nodes are connected to, and all minions that are connected to same master. > > > anyway, i turned the check off for now. it's good to know it triggers, but > > > with clang and other changes now isn't the best time. > > > > Thank you.
