Forum Discussion
Kishore_Kumar_2
Apr 21, 2016Cirrus
Eventd.xml file changes its enabled value from <enabled>1</enabled> to <enabled>0</enabled>
When there is a change that triggers a notification, the value of enabled changes from 1 to 0.
When I edit the enabled value to 1 and restart eventd daemon - It ...
- Apr 25, 2016
Hi Everyone,
Issue is resolved. When the API call is not been answered, the value of enabled is changed to 0. Once I correct them, Seems to be working fine.
Kishore_Kumar_2
Apr 25, 2016Cirrus
Hi Everyone,
Issue is resolved. When the API call is not been answered, the value of enabled is changed to 0. Once I correct them, Seems to be working fine.
- Apr 25, 2016The event notification system will attempt to send messages out. If the server component cannot reach the endpoint you specify and successfully send the SOAP message, it will disable itself after a certain number of attempts. In the CodeShare there are test client perl scripts that you can point to your endpoint to make sure it's functioning correctly.
- Kishore_Kumar_2Apr 27, 2016CirrusThanks Joe, I get it
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects