there are no environmental variables used for this command, I have even removed the $USER2$ nagios rescource variable and used a full path to the command.
I think there has to be something preventing this being executed via nagios. This command / config works in other distributed enviroments within our business (Using Nagios Core) its only this location using XI where this issue occurs.
I am currently working back through all templates used to ensure that oscp has not been disabled, as a second check however I cant see this being the issue as it works in other environments.
I have checked all my configurations. And even created a test service that implements no templates.
The Obsess over service command is never fired (I have wrapped this with a perl script that I use to debug checks which logs no activity for this command)
I also tried switching the ocsp command to use a notify-by-email (Edited to email a set address) that is proven to work in this environment. The ocsp command is never executed.
It appears that although the nagios.cfg file had been updated, for some reason the Obsess_over_service parameter was not being read by nagios.
Process Info was showing obsess over service as disabled... once I clicked enable in the GUI it appeared to correct the issue. Not sure if this is a bug in xi reading the core config file?