00:10:20 <bahamat> aquamo4k: The serial console isn't exposed via triton (yet?)
00:10:42 <bahamat> So for tenants, vnc gets them access without needing to contact an operator.
12:56:24 <psarria> hi
12:57:53 <psarria> danmcd, here you can view fmadm faulty also the steps that i follow in order to reproduce the problem
12:57:55 <psarria> https://pastebin.com/u4Jhtnmw
13:07:18 <aquamo4k> bahamat: thanks for clarification; i didn't know that even though I ran triton at home for a while :-)
15:11:15 <danmcd> psarria: So between `svcadm restart varpd` and `dladm show-overlay -f`, please utter
15:11:41 <danmcd> `fmadm acquit <UUID>` and see what happens after `show-overlay -f`?
15:12:18 <danmcd> I see that fmadm fault when I reboot my Triton head node and it times out SVP service on my test cloud.  Clearing that fault bring my fabrics online.
15:13:35 <danmcd> Today is a many-meetings-and-actual-work-too day or I'd reproduce the problem myself this instant.
15:14:03 <danmcd> As part of SmartOS testing this week, I can try and remember to run `dladm show-overlay...` as I update my test cloud to this week's SmartOS, however.
15:14:19 <danmcd> (I meant to say "attempt to reproduce...")
16:22:44 <xmerlin> Is it possible to add an image like memtest86 inside the SmartOS USB stick loader? If so, do you have any guide/documentation where I can find information?
16:25:53 <psarria_> danmcd, i see fmadm acquit no offer better results, the overlay remains degraded, https://pastebin.com/WEXdmQmT
16:29:29 <psarria_> it's like varpd doesn't re-read the overlay file with the restart
16:33:54 <jbk> are you not using portolan?
16:50:59 <psarria_> no, i'm using only files as search plugin, i thought there was only direct and files
16:51:39 <psarria_> i'm reading there's svp as part of triton
16:57:03 <jbk> yeah, that uses portolan
16:57:15 <jbk> if you're using files, make sure you've got the syntax correct
16:58:36 <jbk> IIRC files was there more to test the functionality originally, so unless something's changed, it's probably not as user-friendly
17:32:35 <psarria_> jbk, i'm searching docs for portolan, is it usable in smartos standalone or is it only for triton ?
18:30:45 <jbk> psarria_: it requires triton
18:31:17 <psarria_> ok, thanks, i supposed it
18:33:43 <jbk> if you are using files though, i have the vague recollection that a syntax error in the file could cause the degraded state
18:34:54 <bahamat> xmerlin: If you're wanting it to be part of the platform image, then you'd put it in the projects directory when doing the build, and update the manifest accordingly. If you just want a static binary you can drop it on the usb then just mount it and use it.
18:35:30 <danmcd> But his point is that a *fixed* file, a restarted varpd, AND a `fmadm clear` doesn't seem to help.  I know on #triton I get that fmadm error and when portolan comes up bits move.
18:36:00 <jbk> are you sure it's fixed though? i recall it being _extremely_ finicky
18:36:01 <danmcd> Something in his chain is off.  Once I do SmartOS release testing, I'll check to see if `dladm show-overlay` reports oddness, even if bits are moving.
18:36:06 <jbk> like pull your hair out touchy
18:36:21 <danmcd> "it" ==> varpd support for files?  That *is* a possibility.
18:36:25 <jbk> yeah
18:36:36 <danmcd> (varpd files might need something like in.iked's `-c` option...)
18:36:59 <jbk> since it was more of a dev thing, it wasn't anything i really spent time on trying to fix
18:37:24 <jbk> once i figured out what my problem was
18:39:14 <xmerlin> bahamat, I need an entry for memtest-pro in loader ...I've some strange issues on some supermicro server and I can detect these problems only using the parallel test of memtest-pro
18:39:36 <bahamat> Oh, you mean you want to add that to the boot menu
18:41:21 <bahamat> Ok, yeah, that shouldn't be too hard. I think everything you need is in the loader.conf(5) man page.
18:42:31 <bahamat> The loader.conf is in the boot directory on the USB. You may want to edit loader.conf.tmpl to make sure the entry doesn't vanish if you update your platform image.
18:43:35 <bahamat> Or rather, from wherever your boot media is, the file you're looking for is boot/loader.conf or boot/loader.conf.tmpl
18:44:52 <bahamat> E.g., for a usb, assuming you mount it at /mnt, that's /mnt/usbkey/boot/loader.conf, or for pool booting $BOOTPOOL/boot/loader.conf(.tmpl)
19:00:27 <xmerlin> bahamat, thank you very much
19:49:33 <psarria_> jbk, are you sure it's fixed though? i recall it being _extremely_ finicky <- yes, i'm sure the syntax of files are correct, in fact, i'm using the same syntax that the overlay uses for the start without problems, you can see it here https://pastebin.com/u4Jhtnmw
19:51:02 <psarria_> it's like varpd doesn't reread the files when it is restarted the overlay remains degraded