Forum Discussion
Failed to set active
Hi;
When trying to apply a policy in ASM, I get failed to set active and this happens after I have mitigated a scan result group of XSS signatures.
Here is what I get in the logs
ASM subsystem error (asm_config_server.pl,F5::SetActive::Impl::set_active): Setting policy active failed: Failed on insert to DCC.ACCOUNT_WILDCARD_OBJECT_PARAMETERS (DBD::mysql::db do failed: Duplicate entry '0-9-10006452745544771164-2' for key 'PRIMARY')
My question is how can I pin point the attack signature that is causing this and fix it so I can apply the policy
Also, once I mitigate a volubility generated by a scanner, how can I un-mitigate it?
Kindly Wasfi
1 Reply
- Chris_Grant
Employee
Wasfi,
You will want to open a case with Support for this. This is a database error, and trying to fix it without guidance could make things far worse than they already are. You can reach support by calling 1-888-882-7525 or internationally 800 11 ASK 4 F5. Make sure you have your BigIP's serial number available as you will need it to open the case.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com