afternoon all! i'm still poking DRP - maybe a little further along the road now. I've done a fairly vanilla install, bound DRP to the interface I want to use (usign --static-ip), but I'm still unable to get any of the files in the tftpboot dir which obviously means the boot fails. I've tried connecting with a tftp client but that also fails with 'transfer timed out'
any suggestion as to where i'm going wrong here?
palm has been vigorously applied to face
[greg] For packet, we add profiles that set the
kernel-console parameter
[greg] To handle this case.
[greg] You can set that globally or on a machine or a profile to a machine.
[greg] Checkout the parameter
kernel-console in the UX.
ok, will do. thanks!
[greg] @faq
[greg] in faq - 22.3
ah yes i see what you mean, i can see a key for 'galthaus@Gregs-MacBook-Pro.local' in the root-access-example profile ;)
[greg] The main thing to remember is that the parameter has to be set on the machine (globally, or specifically, or by profile assignment) when the task
ssh-access runs during the discover stage. That means for discovered things you have to have it globally set. Or set it after discovery and reboot.
thanks again!
the machine is currently sitting in the discover stage according to it's info
[greg] Check the jobs area to see if there is a failed job. The machine has probably been marked not runnable as well.
[lae] I'm getting this I guess after a recent update, did anything change regarding importing profiles from yaml?
[lae] kind of expected this to also work, but I guess it's not expecting stdin to be yaml anymore?
[lae@yuzu fireeye-content]$ drpcli profiles show global -F yaml > tmp.yml
[lae@yuzu fireeye-content]$ drpcli profiles update global - < tmp.yml
Error: Failed to generate changed profiles:global object: invalid character 'A' looking for beginning of value
[lae] I'm just reusing my existing workflow for updating the global profile, which seems to not support yaml anymore
[lae] (I just went ahead and exported/edited/reimported as json but that's more tedious than editing yaml and committing it to git)
@lae I have found some of the docs to be a little out of date and I had to fudge my way around it - editing profiles was oen of them
Running v3.6.0
[shane] @MattyBoy4444 - are you sure your DRP Endpoint is accessible from your Laptop/Management machine - no Firewalls or IPTables rules blocking access? You can also check the process to make sure it's running on the Endpoint as well (
ps -ef | grep dr-provision) ... also - any log output from the running instance if it is running ?
[shane] you need TCP Port 8092 access to the DRP Endpoint from the system you are running the Web Browser connection to the Portal