Sorry, not asking to remove actual Threshold Profiles from DA admin views. I was referring to the Threshold Profile tab in the notification creation/editor under stage "3 Conditions". See it the above screenshot you provided?
We want to make sure NO threshold profile/folder is selected for that tab in notifications.We should not be touching Threshold Profiles under DA Administration pages.So you enabled Email on the same 1 notification entry? and email works but not script?Check the EMService.log around the time the script should run. It should print a message if it was able to run successfully or not.
Any ScriptHandlerImpl messages ( The script <scriptName> did not execute... OR The exit code of the executed script <scriptname>...) around EmailHandlerImpl message ( Sending e-mail ... ) that sends out the email for this event?
Or maybe a "Failed to execute script " with an exception?
It's a perl script, so is the first line #!/bin/perl ?Does the /path/perl you are using exist? If not, then the script will fail to run, maybe with same error.
If you run the perl script from command line, does it run? print something or throw an error?The file perms look fine. The PC runs are root?If you change the notification config to run one of the other scripts, does it throw the same error or work?For security, I would suggest doing 700 for perms on those, if PC runs as root. Only root should be able to read/execute them from web server, or commandline.
Yes, it's more restrictive. It's not gonna fix things, but make things more secure. It should not break the other notifications using the other scripts.
This returns syntax ok ?/bin/perl -c <scriptname>
Running out of ideas why not working... Is there a space at the start or end of the script name in the notification configuration dialog? remove any leading or trailing spaces, if any.
ksh ./nonworkingscript.pl not working may make sense since ksh is not the right script interpreter.What did you say was the first line of the script? complete line.I think java may be reading the first line to determine what to use to run the script, and it's not exactly and ONLY:#!/bin/perl
It may fail to run.
Did you try running from commandline (no ksh, no perl before it)
-> ./nonworkingscript.plWhat does that say?