A user had set up a trigger to put a virtual machine into Citrix Maintenance Mode when local storage D:\ was below X GB, but it was not working. Another user shared screenshots of their own working trigger configuration and suggested the user upgrade to the latest ControlUp version. They also proposed trying a script that drains and reboots the server instead of putting it into Maintenance Mode. The latest ControlUp version was already being used.
Read the entire ‘Troubleshooting a Trigger Not Working in ControlUp’ thread below:
Hello,
we have configured a trigger that puts the vm into citrix maintenance mode when the local storage D:\ is below x GB.
The trigger is not working. We cannot find the trigger in the incidents log.
Does anyone have any idea what the problem could be?
Can you please share a screenshot of the trigger configuration screen @member?
(and pls remember that ControlUp triggers work based on state changes. so, if you configure the trigger to fire when free space on D driver is below 5%, the agent waits to “see” that free space drops below 5% and then fire the incident)
here the screenshot
yes, I have already tried that
Hi @member, I did a quick test in our lab and all worked well, trigger settings:
I caused one D drive to go below 5GB:
Incident was created:
we use the latest 8.8 version in our lab
I suggest you upgrade to latest version, try again, and if this still fails, you can open a support ticket via support@controlup.com
Ok thank you. We are already on the latest version
@member – Try this as we do something similiar but we have a script that automatically drains and reboots the server instead of maintenance mode. However – here’s what ours looks like that does work and has worked for many years.
Continue reading and comment on the thread ‘Why isn’t the Citrix VM maintenance mode trigger activating when local storage falls below a certain capacity?’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers