shyawnkarim
commented
5 years ago Thanks for reaching out to us about this issue. I've gone ahead and filed a bug with Jira (#1714) to provide a more descriptive error output.
If you provide some additional information, I might be able to help troubleshoot this. How are you running this? Is this from a template? Are there any additional logs or is this the last one? Also, can you confirm network reachability of the BIG-IQ from that BIG-IP? curl -sk https://BIG_IQ_ADDR?
Hello , I used the following command on BIGIP for onboarding could you please to clarify the meaning of "ERROR signaled from other script. Exiting"?
[root@f5-test-bigip-instance-n2hdjpvpamhn:NO LICENSE:Standalone] licensing # /us r/bin/tmsh license path /config/licensing/node_modules/@f5devcentral/f5-cloud-li bs password inwinstack123 big-iq -host 140.110.157.120 big-iq-user api big-iq-pas sword NCHC@api license-pool-name BIGIP-Pool-01 cloud kvm 2019-10-31T10:17:21.036Z info: /config/licensing/node_modules/@f5devcentral/f5-cloud-libs/scripts/onboard.js called with /usr/bin/f5-rest-node /config/licensing/ node_modules/@f5devcentral/f5-cloud-libs/scripts/onboard.js --license-pool --password --big-iq-host 140.110.157.120 --big-iq-user api - -big-iq-password --license-pool-name BIGIP-Pool-01 --cloud kvm --host localhost --user admin --port 8443 2019-10-31T10:17:21.043Z info: Onboard starting. 2019-10-31T10:17:21.047Z info: Initializing device. 2019-10-31T10:17:21.056Z info: This is a BIG-IP 2019-10-31T10:17:21.057Z info: Waiting for device to be ready. 2019-10-31T10:17:21.142Z info: Waiting for device to be ready. 2019-10-31T10:17:21.190Z info: Device is ready. 2019-10-31T10:17:21.190Z info: Setting global settings. 2019-10-31T10:17:21.464Z info: Getting license from BIG-IQ license pool. 2019-10-31T10:17:22.041Z info: ERROR signaled from other script. Exiting