01:50:19 bahamat, the start will succeed, after some indeterminate time 01:50:32 so there is some timeout that will handle it, eventually 01:52:22 cutting from the status: 01:52:26 nginx: 01:52:29 Active: active (running) since Wed 2022-10-12 01:50:41 UTC; 4s ago 01:52:35 Process: 67771 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) 01:52:39 Process: 67772 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) 01:52:42 postgresql: 01:52:43 Active: active (exited) since Wed 2022-10-12 00:50:44 UTC; 57min ago 01:52:49 Process: 63727 ExecStart=/bin/true (code=exited, status=0/SUCCESS) 01:53:11 whops, missed main pid line: 01:53:16 nginx: Main PID: 67773 (nginx) 01:53:29 postgresql: Main PID: 63727 (code=exited, status=0/SUCCESS) 01:54:11 the difference must be nginx being 'stay running' and postgresql being 'fork a background process' 02:38:16 is there a defined process to handle postgres databases when doing native zone upgrade (with delegated dataset)? 09:51:56 since when is piadm (command) a thing? pretty useful stuff 09:52:29 by the way, any freebsd13 images floating around? failing that, is the freebsd12 one good? 10:03:57 is there any configuration i can add to silently drop connections to closed ports on the GZ? like net.inet.tcp.blackhole=2 on freebsd 11:30:28 wow, i get ** server can't find pkgsrc.smartos.org: SERVFAIL for pkgsrc.smartos.org on my local internet provider.. (major one) 11:31:03 And sometimes it does resolve ti, but in like one in 10 tries.. May be loca issue with provider NS or.. 11:33:52 8.8.8.8 answers promptly 11:34:51 also does 1.1.1.1 .. but local one.. 17:32:20 gonzosysadm[m]: I haven't had any issues with the freebsd 12 image though I also haven't used it very much. I did upgrading it to 12.3 without issue. 17:35:08 gonzosysadm[m]: The freebsd 12 image appears to work well, I haven't used it heavily but I was able to upgrade it to 12.3. 17:36:31 gonzosysadm[m]: sorry for the duplicate send, it looked like Thunderbird ate the first message. 21:39:47 bahamat: should dehydrated be installed on all headnodes in order to work on ha instances such as cmon? 21:40:37 It only needs to be on the primary headnode. It knows how to distribute the cert to each cmon instance. 21:41:25 Weird, I created a couple of HA cmon instances but they still have self-signed .triton certs. 21:42:21 depth=0 CN = *.triton 21:42:22 verify error:num=18:self signed certificate 21:42:25 https://github.com/TritonDataCenter/triton-dehydrated/blob/master/cns-hook-util#L305-L318 21:42:34 Ha 21:42:48 Thanks!