Nagios Exchange Nagios Exchange
  • Home
  • Directory
  • Library
  • Support
  • About

Advanced Search

Build precise queries to find exactly what you need

Search Logic

Select compatible versions

Press ESC to close

Sign In Sign Up
  • Home
  • Directory
  • Library
  • Support
  • About
Plugins4394Themes and Skins11Add-ons743Documentation283Graphics and Logos36View All Categories
LinuxSecuritySNMPFile SystemCloud
New Listings Recently Updated Listings Most Favored Listings Most Popular Listings Most Rated Listings Most Reviewed Listings
Random Project
Remote Access Count number of terminal server sessions
4.7 (6)
131.1K
RSS Feed
Newest Listings Updated Listings
Top Contributors
Julien DESMAREST (6)Yoann LAMY (6)Davide Lemma (4)deskwork_itunes142 (4)Claudio Kuenzler (2)
See More
Newest Contributors
RavuAlHemio (1)sowoii (1)Nitatemic (1)cjdepaul (1)ixs (1)
See More

Copyright © 2009-2025 Nagios Enterprises, LLC. All rights reserved.

Privacy PolicyTerms of UseTrademarks
Home > Martin
M

Martin

@Maddin

User Stats

Member Since: February 23, 2014

Favorites0

Views

Projects0

No Projects Found
check_fortigate.pl: fortigate,fortimail, fortianalyzer

Workaround for "Service check did not exit properly"

The problem is the ePN (Embedded Perlinterpreter for Nagios) If you enable Debugging in Nagios, you get the following error: --- HOST: somehost, SERVICE: CPU, CHECK TYPE: Active, OPTIONS: 0, SCHEDULED: Yes, RESCHEDULE: Yes, EXITED OK: No, RETURN CODE: 3, OUTPUT: **ePN failed to compile /some/dir/plugins/check_fortigate.pl: "String found where operator expected at (eval 17) line 94, near "case "cpu""" at /usr/lib/nagios3/p1.pl line 250. --- The workaround is to disable the ePN by inserting the following String an the second line in the check_fortigate.pl-script --- # nagios: -epn ---

Reviewed 12 years ago

No Favorites Found

Copyright © 2009-2025 Nagios Enterprises, LLC. All rights reserved.

Privacy PolicyTerms of UseTrademarks
Home Browse Submit Profile