aquamo4k: The serial console isn't exposed via triton (yet?)

So for tenants, vnc gets them access without needing to contact an operator.

hi

danmcd, here you can view fmadm faulty also the steps that i follow in order to reproduce the problem

bahamat: thanks for clarification; i didn't know that even though I ran triton at home for a while :-)

psarria: So between `svcadm restart varpd` and `dladm show-overlay -f`, please utter

`fmadm acquit <UUID>` and see what happens after `show-overlay -f`?

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.

Today is a many-meetings-and-actual-work-too day or I'd reproduce the problem myself this instant.

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.

(I meant to say "attempt to reproduce...")

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?

danmcd, i see fmadm acquit no offer better results, the overlay remains degraded, pastebin.com/WEXdmQmT

it's like varpd doesn't re-read the overlay file with the restart

are you not using portolan?

no, i'm using only files as search plugin, i thought there was only direct and files

i'm reading there's svp as part of triton

yeah, that uses portolan

if you're using files, make sure you've got the syntax correct

IIRC files was there more to test the functionality originally, so unless something's changed, it's probably not as user-friendly

jbk, i'm searching docs for portolan, is it usable in smartos standalone or is it only for triton ?

psarria_: it requires triton

ok, thanks, i supposed it

if you are using files though, i have the vague recollection that a syntax error in the file could cause the degraded state

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.

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.

are you sure it's fixed though? i recall it being _extremely_ finicky

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.

like pull your hair out touchy

"it" ==> varpd support for files? That *is* a possibility.

yeah

(varpd files might need something like in.iked's `-c` option...)

since it was more of a dev thing, it wasn't anything i really spent time on trying to fix

once i figured out what my problem was

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

Oh, you mean you want to add that to the boot menu

Ok, yeah, that shouldn't be too hard. I think everything you need is in the loader.conf(5) man page.

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.

Or rather, from wherever your boot media is, the file you're looking for is boot/loader.conf or boot/loader.conf.tmpl

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)

bahamat, thank you very much

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 pastebin.com/u4Jhtnmw

it's like varpd doesn't reread the files when it is restarted the overlay remains degraded