Support Center > Search Results > SecureKnowledge Details
"The object specified in 'Always send alerts to' field, has no active 'Logging & Status' blade" error after entering the "add-simple-gateway" command Technical Level
Symptoms
  • The users are unable to provision new gateways in their environment, using API or as part of autoprovisioning.
  • CPM shows these errors: 2021-01-24 11:39:56,769 CME_SERVICE DEBUG Executing add-simple-gateway management API command with body 2021-01-24 11:39:59,955 CME_SERVICE INFO The response body is: { "code": "generic_error", "message": "Validation failed with 4 blocking-errors", "blocking-errors": [ { "message": "The object specified in 'Always send alerts to' field, has no active 'Logging & Status' blade" }, { "message": "The object specified in 'Always send logs to' field, has no active 'Logging & Status' blade" }, { "message": "The object specified in 'Always send logs to' field, has no active 'Logging & Status' blade" }, { "message": "The object specified in 'Always send alerts to' field, has no active 'Logging & Status' blade" } ] }
  • # mgmt_cli add-simple-gateway command fails with the similar error message:
    code: "err_validation_failed"
    message: "Validation failed with 4 blocking-errors"
    blocking-errors:
    
    message: "The object specified in 'Always send alerts to' field, has no active 'Logging & Status' blade"
    message: "The object specified in 'Always send logs to' field, has no active 'Logging & Status' blade"
    message: "The object specified in 'Always send alerts to' field, has no active 'Logging & Status' blade"
    message: "The object specified in 'Always send logs to' field, has no active 'Logging & Status' blade"
    Executed command failed. Changes are discarded.
Cause
The user's environment contains a Multi-Domain Server and a Multi-Domain Log Server, and only the Multi-Domain Log Server is the log server.
The "add-simple-gateway" command tries to create a gateway using the current Domain Management Server as a log server, and fails because this Domain Management Server does not have the "Logging and Monitoring" blade enabled.
Solution
Note: To view this solution you need to Sign In .