13:04:01 hi 13:04:20 I would like to ask how to set up cloud-init on SmartOS under the BHYVE brand with a custom ISO installation. I mean that I'm not using the official Joyent image. What I want to do is configure the network with cloud-init in a BHYVE VM. I have installed cloud-init, all related services are enabled, I also set up the serial console in the grub, etc. It seems to be working because under '/var/lib/cloud/instances' the VM UUID is created and I can see the IP 13:04:20 settings I specified in the metadata on the SmartOS host in the 'obj.pkl' file, but for some reason, it doesn't execute them. The datasource_list [ SmartOS ] is, of course, set. I checked the official Joyent image and applied the same settings that are in the '/etc/cloud' folder, and the kernel parameters in the grub are the same, yet it doesn't work for me. 13:04:21 Any ideas? 14:48:30 problem solved 15:02:15 unix - nice 23:45:16 I tried to rebuild my one LX zone today, using: 23:45:18 632a25ad-15dc-42f0-a23b-743b37f62cbb alpine-3 20240726 linux lx-dataset 2024-07-26 23:45:39 It's tres unhappy. I think the main problem is that dns is hosed. 23:45:57 e.g.: 23:45:58 cats:/var/log# host cats.h-net.org 23:45:58 netmgr/udp.c:1021:isc_nm_udpconnect(): fatal error: RUNTIME_CHECK(result == ISC_R_SUCCESS || result == ISC_R_NOTIMPLEMENTED) failed 23:46:01 Aborted (core dumped) 23:46:13 Can you ping it? 23:47:25 yes, and since ssh is running right now, I can ssh to it. 23:47:39 (In an earlier attempt, ssh wouldn't run.) 23:48:10 I mean, can you ping cats.h-net.org? 23:48:10 nginx won't start because it can't look up its syslog server to send logs to. 23:48:17 yes 23:48:24 by name? 23:48:28 yes 23:48:37 dns service in the environment is fine 23:48:50 but something about resolution on this machine is hosed 23:48:55 this guest 23:49:10 Can you ping it by name from inside the guest? 23:49:37 yes, but its name is in /etc/hosts 23:49:59 What if you take it out? 23:50:00 `dig` does similar things to `host` 23:50:09 oddly, `apk update` works 23:50:41 dig and host both set privileged flats on packets. They don't just do gethostbyname(). 23:50:41 yes, can ping from inside the guest by name even without its name in /etc/hosts 23:51:03 oh, and this is an alpine image 23:51:13 ah, there it is, I did say that 23:54:15 Do you have a dns server declaration in the nginx config? 23:54:35 no, haven't ever needed to 23:54:37 lemme see 23:57:41 doesn't help 23:58:16 but doc says that's for looking up upstream servers (in proxy, I think?) so maybe it doesn't use it to look up syslog servers to which it will send access log data.