Hi all,
I’ve been trying to use this scrip to auto close Nagios tickets upon
recovery:
http://requesttracker.wikia.com/wiki/AutoCloseOnNagiosRecoveryMessages
The Script is launched, but there’s an error
[Sat Mar 5 02:40:02 2011] [error]: Scrip 12 Commit failed: Quantifier
follows nothing in regex; marked by ← HERE in m/* ← HERE * RECOVERY
(w+) - (.*) OK **/ at (eval 3695) line 13.
I’m not terribly good at Perl and especially its regexp, but I’ve got a
feeling it might be an escaping issue?
Has anyone encountered this problem - or am I maybe just using a very
old script?
We use Nagios2 so until we update to Nagios3 I can’t use the other
recommended script, so any help would be really appreciated.
Best regards,
Giuseppe
Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George’s, University Of London
Cranmer Terrace
London SW17 0RE
Email: gsollazz@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583
Hi all,
I’ve been trying to use this scrip to auto close Nagios tickets upon
recovery:
http://requesttracker.wikia.com/wiki/AutoCloseOnNagiosRecoveryMessages
The Script is launched, but there’s an error
[Sat Mar 5 02:40:02 2011] [error]: Scrip 12 Commit failed: Quantifier
follows nothing in regex; marked by ← HERE in m/* ← HERE * RECOVERY
(w+) - (.*) OK **/ at (eval 3695) line 13.
I’m not terribly good at Perl and especially its regexp, but I’ve got a
feeling it might be an escaping issue?
Has anyone encountered this problem - or am I maybe just using a very
old script?
I don’t know if the scrip is old or not, but you need to backslash
escape the asterisks at the beginning and end of that regex (but not the
one following the period in the middle).
m/** RECOVERY (w+) - (.*) OK **/
Thomas
Hi all,
I’ve been trying to use this scrip to auto close Nagios tickets upon
recovery:
http://requesttracker.wikia.com/wiki/AutoCloseOnNagiosRecoveryMessages
The Script is launched, but there’s an error
[Sat Mar 5 02:40:02 2011] [error]: Scrip 12 Commit failed: Quantifier
follows nothing in regex; marked by ← HERE in m/* ← HERE * RECOVERY
(w+) - (.*) OK **/ at (eval 3695) line 13.
I’m not terribly good at Perl and especially its regexp, but I’ve got a
feeling it might be an escaping issue?
Has anyone encountered this problem - or am I maybe just using a very
old script?
I don’t know if the scrip is old or not, but you need to backslash
escape the asterisks at the beginning and end of that regex (but not the
one following the period in the middle).
m/** RECOVERY (w+) - (.*) OK **/
There is also RT-Extension-Nagios-1.01 - Merge and resolve Nagios tickets - metacpan.org
Hi Kevin,
thanks for the advise - I’ll try this one although I’m wondering if it’s
stable enough?
Thomas, oops, something must have gone wrong in the copy&paste.
Thanks,
GiuseppeOn 15/04/11 17:25, Kevin Falcone wrote:
On Fri, Apr 15, 2011 at 11:32:22AM -0400, Thomas Sibley wrote:
On 04/15/2011 11:23 AM, Giuseppe Sollazzo wrote:
Hi all,
I’ve been trying to use this scrip to auto close Nagios tickets upon
recovery:
http://requesttracker.wikia.com/wiki/AutoCloseOnNagiosRecoveryMessages
The Script is launched, but there’s an error
[Sat Mar 5 02:40:02 2011] [error]: Scrip 12 Commit failed: Quantifier
follows nothing in regex; marked by<-- HERE in m/ ← HERE * RECOVERY
(w+) - (.) OK **/ at (eval 3695) line 13.
I’m not terribly good at Perl and especially its regexp, but I’ve got a
feeling it might be an escaping issue?
Has anyone encountered this problem - or am I maybe just using a very
old script?
I don’t know if the scrip is old or not, but you need to backslash
escape the asterisks at the beginning and end of that regex (but not the
one following the period in the middle).
m/** RECOVERY (w+) - (.*) OK **/
There is also RT-Extension-Nagios-1.01 - Merge and resolve Nagios tickets - metacpan.org
Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George’s, University Of London
Cranmer Terrace
London SW17 0RE
Email: gsollazz@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583
thanks for the advise - I’ll try this one although I’m wondering if
it’s stable enough?
I’m not sure why it would be unstable?
thanks for the advise - I’ll try this one although I’m wondering if
it’s stable enough?
I’m not sure why it would be unstable?
Release number “0.05” is generally not a hint of extreme stability 
Giuseppe
Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George’s, University Of London
Cranmer Terrace
London SW17 0RE
Email: gsollazz@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583
thanks for the advise - I’ll try this one although I’m wondering if
it’s stable enough?
I’m not sure why it would be unstable?
Release number “0.05” is generally not a hint of extreme stability
There are plenty of RT extensions that are stable with lower version
numbers than .05
-kevin
That’s good to know.
Thanks,
GiuseppeOn 20/04/11 17:11, Kevin Falcone wrote:
There are plenty of RT extensions that are stable with lower version
numbers than .05
-kevin
Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George’s, University Of London
Cranmer Terrace
London SW17 0RE
Email: gsollazz@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583