Ubuntu-fr

TomHawk

[Résolu] Problème de configuration des mails dans Nagios/Postfix

Bonjour à tous !

Je suis un petit nouveau sur le forum. J'ai monté un Ubuntu avec Nagios pour superviser mon réseau d'entreprise (deux trois machines :-D ).
Je souhaite recevoir un email à chaque fois que la machine supervisée ne répond plus au ping (UP ou DOWN).

Seulement je n'y arrive pas... Je crois avoir tout bien configuré, mais j'ai du oublier quelque chose.

Pourriez-vous me venir en aide ?

Merci beaucoup par avance,

Bonne journée
Tom.

Dernière modification par TomHawk (Le 18/03/2014, à 17:09)

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Salut,

Oui on peut te venir en aide, mais d'abord il faut montrer ce que tu as configuré... Sinon on ne pourra pas faire grand chose...

(et sinon, Nagios c'est un choix définitif ? )

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Bonjour,

Merci de ta réponse !
Alors j'ai récupéré des fichiers...

J'espère qu'il y aura ce qu'il faut :

- Config de Nagios

##############################################################################
#
# NAGIOS.CFG - Sample Main Config File for Nagios 4.0.3
#
# Read the documentation for more information on this configuration
# file.  I've provided some comments here, but things may not be so
# clear without further explanation.
#
#
##############################################################################


# LOG FILE
# This is the main log file where service and host events are logged
# for historical purposes.  This should be the first option specified 
# in the config file!!!

log_file=/usr/local/nagios/var/nagios.log



# OBJECT CONFIGURATION FILE(S)
# These are the object configuration files in which you define hosts,
# host groups, contacts, contact groups, services, etc.
# You can split your object definitions across several config files
# if you wish (as shown below), or keep them all in a single config file.

# You can specify individual object config files as shown below:
cfg_file=/usr/local/nagios/etc/objects/commands.cfg
cfg_file=/usr/local/nagios/etc/objects/contacts.cfg
cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg
cfg_file=/usr/local/nagios/etc/objects/templates.cfg

# Definitions for monitoring the local (Linux) host
cfg_file=/usr/local/nagios/etc/objects/network.cfg

# Definitions for monitoring a Windows machine
#cfg_file=/usr/local/nagios/etc/objects/windows.cfg

# Definitions for monitoring a router/switch
#cfg_file=/usr/local/nagios/etc/objects/switch.cfg

# Definitions for monitoring a network printer
#cfg_file=/usr/local/nagios/etc/objects/printer.cfg


# You can also tell Nagios to process all config files (with a .cfg
# extension) in a particular directory by using the cfg_dir
# directive as shown below:

#cfg_dir=/usr/local/nagios/etc/servers
#cfg_dir=/usr/local/nagios/etc/printers
#cfg_dir=/usr/local/nagios/etc/switches
#cfg_dir=/usr/local/nagios/etc/routers




# OBJECT CACHE FILE
# This option determines where object definitions are cached when
# Nagios starts/restarts.  The CGIs read object definitions from 
# this cache file (rather than looking at the object config files
# directly) in order to prevent inconsistencies that can occur
# when the config files are modified after Nagios starts.

object_cache_file=/usr/local/nagios/var/objects.cache



# PRE-CACHED OBJECT FILE
# This options determines the location of the precached object file.
# If you run Nagios with the -p command line option, it will preprocess
# your object configuration file(s) and write the cached config to this
# file.  You can then start Nagios with the -u option to have it read
# object definitions from this precached file, rather than the standard
# object configuration files (see the cfg_file and cfg_dir options above).
# Using a precached object file can speed up the time needed to (re)start 
# the Nagios process if you've got a large and/or complex configuration.
# Read the documentation section on optimizing Nagios to find our more
# about how this feature works.

precached_object_file=/usr/local/nagios/var/objects.precache



# RESOURCE FILE
# This is an optional resource file that contains $USERx$ macro
# definitions. Multiple resource files can be specified by using
# multiple resource_file definitions.  The CGIs will not attempt to
# read the contents of resource files, so information that is
# considered to be sensitive (usernames, passwords, etc) can be
# defined as macros in this file and restrictive permissions (600)
# can be placed on this file.

resource_file=/usr/local/nagios/etc/resource.cfg



# STATUS FILE
# This is where the current status of all monitored services and
# hosts is stored.  Its contents are read and processed by the CGIs.
# The contents of the status file are deleted every time Nagios
#  restarts.

status_file=/usr/local/nagios/var/status.dat



# STATUS FILE UPDATE INTERVAL
# This option determines the frequency (in seconds) that
# Nagios will periodically dump program, host, and 
# service status data.

status_update_interval=10



# NAGIOS USER
# This determines the effective user that Nagios should run as.  
# You can either supply a username or a UID.

nagios_user=nagios



# NAGIOS GROUP
# This determines the effective group that Nagios should run as.  
# You can either supply a group name or a GID.

nagios_group=nagios



# EXTERNAL COMMAND OPTION
# This option allows you to specify whether or not Nagios should check
# for external commands (in the command file defined below).  By default
# Nagios will *not* check for external commands, just to be on the
# cautious side.  If you want to be able to use the CGI command interface
# you will have to enable this.
# Values: 0 = disable commands, 1 = enable commands

check_external_commands=1



# EXTERNAL COMMAND FILE
# This is the file that Nagios checks for external command requests.
# It is also where the command CGI will write commands that are submitted
# by users, so it must be writeable by the user that the web server
# is running as (usually 'nobody').  Permissions should be set at the 
# directory level instead of on the file, as the file is deleted every
# time its contents are processed.

command_file=/usr/local/nagios/var/rw/nagios.cmd



# QUERY HANDLER INTERFACE
# This is the socket that is created for the Query Handler interface

#query_socket=/usr/local/nagios/var/rw/nagios.qh



# LOCK FILE
# This is the lockfile that Nagios will use to store its PID number
# in when it is running in daemon mode.

lock_file=/usr/local/nagios/var/nagios.lock



# TEMP FILE
# This is a temporary file that is used as scratch space when Nagios
# updates the status log, cleans the comment file, etc.  This file
# is created, used, and deleted throughout the time that Nagios is
# running.

temp_file=/usr/local/nagios/var/nagios.tmp



# TEMP PATH
# This is path where Nagios can create temp files for service and
# host check results, etc.

temp_path=/tmp



# EVENT BROKER OPTIONS
# Controls what (if any) data gets sent to the event broker.
# Values:  0      = Broker nothing
#         -1      = Broker everything
#         <other> = See documentation

event_broker_options=-1



# EVENT BROKER MODULE(S)
# This directive is used to specify an event broker module that should
# by loaded by Nagios at startup.  Use multiple directives if you want
# to load more than one module.  Arguments that should be passed to
# the module at startup are seperated from the module path by a space.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# Do NOT overwrite modules while they are being used by Nagios or Nagios
# will crash in a fiery display of SEGFAULT glory.  This is a bug/limitation
# either in dlopen(), the kernel, and/or the filesystem.  And maybe Nagios...
#
# The correct/safe way of updating a module is by using one of these methods:
#    1. Shutdown Nagios, replace the module file, restart Nagios
#    2. Delete the original module file, move the new module file into place, restart Nagios
#
# Example:
#
#   broker_module=<modulepath> [moduleargs]

#broker_module=/somewhere/module1.o
#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0



# LOG ROTATION METHOD
# This is the log rotation method that Nagios should use to rotate
# the main log file. Values are as follows..
#	n	= None - don't rotate the log
#	h	= Hourly rotation (top of the hour)
#	d	= Daily rotation (midnight every day)
#	w	= Weekly rotation (midnight on Saturday evening)
#	m	= Monthly rotation (midnight last day of month)

log_rotation_method=d



# LOG ARCHIVE PATH
# This is the directory where archived (rotated) log files should be 
# placed (assuming you've chosen to do log rotation).

log_archive_path=/usr/local/nagios/var/archives



# LOGGING OPTIONS
# If you want messages logged to the syslog facility, as well as the
# Nagios log file set this option to 1.  If not, set it to 0.

use_syslog=1



# NOTIFICATION LOGGING OPTION
# If you don't want notifications to be logged, set this value to 0.
# If notifications should be logged, set the value to 1.

log_notifications=1



# SERVICE RETRY LOGGING OPTION
# If you don't want service check retries to be logged, set this value
# to 0.  If retries should be logged, set the value to 1.

log_service_retries=1



# HOST RETRY LOGGING OPTION
# If you don't want host check retries to be logged, set this value to
# 0.  If retries should be logged, set the value to 1.

log_host_retries=1



# EVENT HANDLER LOGGING OPTION
# If you don't want host and service event handlers to be logged, set
# this value to 0.  If event handlers should be logged, set the value
# to 1.

log_event_handlers=1



# INITIAL STATES LOGGING OPTION
# If you want Nagios to log all initial host and service states to
# the main log file (the first time the service or host is checked)
# you can enable this option by setting this value to 1.  If you
# are not using an external application that does long term state
# statistics reporting, you do not need to enable this option.  In
# this case, set the value to 0.

log_initial_states=0



# CURRENT STATES LOGGING OPTION
# If you don't want Nagios to log all current host and service states
# after log has been rotated to the main log file, you can disable this
# option by setting this value to 0. Default value is 1.

log_current_states=1



# EXTERNAL COMMANDS LOGGING OPTION
# If you don't want Nagios to log external commands, set this value
# to 0.  If external commands should be logged, set this value to 1.
# Note: This option does not include logging of passive service
# checks - see the option below for controlling whether or not
# passive checks are logged.

log_external_commands=1



# PASSIVE CHECKS LOGGING OPTION
# If you don't want Nagios to log passive host and service checks, set
# this value to 0.  If passive checks should be logged, set
# this value to 1.

log_passive_checks=1



# GLOBAL HOST AND SERVICE EVENT HANDLERS
# These options allow you to specify a host and service event handler
# command that is to be run for every host or service state change.
# The global event handler is executed immediately prior to the event
# handler that you have optionally specified in each host or
# service definition. The command argument is the short name of a
# command definition that you define in your host configuration file.
# Read the HTML docs for more information.

#global_host_event_handler=somecommand
#global_service_event_handler=somecommand



# SERVICE INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" service checks when it starts monitoring.  The
# default is to use smart delay calculation, which will try to
# space all service checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)!  This is not a
# good thing for production, but is useful when testing the
# parallelization functionality.
#	n	= None - don't use any delay between checks
#	d	= Use a "dumb" delay of 1 second between checks
#	s	= Use "smart" inter-check delay calculation
#       x.xx    = Use an inter-check delay of x.xx seconds

service_inter_check_delay_method=s



# MAXIMUM SERVICE CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all services should
# be completed.  Default is 30 minutes.

max_service_check_spread=30



# SERVICE CHECK INTERLEAVE FACTOR
# This variable determines how service checks are interleaved.
# Interleaving the service checks allows for a more even
# distribution of service checks and reduced load on remote
# hosts.  Setting this value to 1 is equivalent to how versions
# of Nagios previous to 0.0.5 did service checks.  Set this
# value to s (smart) for automatic calculation of the interleave
# factor unless you have a specific reason to change it.
#       s       = Use "smart" interleave factor calculation
#       x       = Use an interleave factor of x, where x is a
#                 number greater than or equal to 1.

service_interleave_factor=s



# HOST INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" host checks when it starts monitoring.  The
# default is to use smart delay calculation, which will try to
# space all host checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)!
#	n	= None - don't use any delay between checks
#	d	= Use a "dumb" delay of 1 second between checks
#	s	= Use "smart" inter-check delay calculation
#       x.xx    = Use an inter-check delay of x.xx seconds

host_inter_check_delay_method=s



# MAXIMUM HOST CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all hosts should
# be completed.  Default is 30 minutes.

max_host_check_spread=30



# MAXIMUM CONCURRENT SERVICE CHECKS
# This option allows you to specify the maximum number of 
# service checks that can be run in parallel at any given time.
# Specifying a value of 1 for this variable essentially prevents
# any service checks from being parallelized.  A value of 0
# will not restrict the number of concurrent checks that are
# being executed.

max_concurrent_checks=0



# HOST AND SERVICE CHECK REAPER FREQUENCY
# This is the frequency (in seconds!) that Nagios will process
# the results of host and service checks.

check_result_reaper_frequency=10




# MAX CHECK RESULT REAPER TIME
# This is the max amount of time (in seconds) that  a single
# check result reaper event will be allowed to run before 
# returning control back to Nagios so it can perform other
# duties.

max_check_result_reaper_time=30




# CHECK RESULT PATH
# This is directory where Nagios stores the results of host and
# service checks that have not yet been processed.
#
# Note: Make sure that only one instance of Nagios has access
# to this directory!  

check_result_path=/usr/local/nagios/var/spool/checkresults




# MAX CHECK RESULT FILE AGE
# This option determines the maximum age (in seconds) which check
# result files are considered to be valid.  Files older than this 
# threshold will be mercilessly deleted without further processing.

max_check_result_file_age=3600




# CACHED HOST CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous host check is considered current.
# Cached host states (from host checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to the host check logic.
# Too high of a value for this option may result in inaccurate host
# states being used by Nagios, while a lower value may result in a
# performance hit for host checks.  Use a value of 0 to disable host
# check caching.

cached_host_check_horizon=15



# CACHED SERVICE CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous service check is considered current.
# Cached service states (from service checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to predictive dependency checks.
# Use a value of 0 to disable service check caching.

cached_service_check_horizon=15



# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of hosts when it predicts that future dependency logic test
# may be needed.  These predictive checks can help ensure that your
# host dependency logic works well.
# Values:
#  0 = Disable predictive checks
#  1 = Enable predictive checks (default)

enable_predictive_host_dependency_checks=1



# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of service when it predicts that future dependency logic test
# may be needed.  These predictive checks can help ensure that your
# service dependency logic works well.
# Values:
#  0 = Disable predictive checks
#  1 = Enable predictive checks (default)

enable_predictive_service_dependency_checks=1



# SOFT STATE DEPENDENCIES
# This option determines whether or not Nagios will use soft state 
# information when checking host and service dependencies. Normally 
# Nagios will only use the latest hard host or service state when 
# checking dependencies. If you want it to use the latest state (regardless
# of whether its a soft or hard state type), enable this option. 
# Values:
#  0 = Don't use soft state dependencies (default) 
#  1 = Use soft state dependencies 

soft_state_dependencies=0



# TIME CHANGE ADJUSTMENT THRESHOLDS
# These options determine when Nagios will react to detected changes
# in system time (either forward or backwards).

#time_change_threshold=900



# AUTO-RESCHEDULING OPTION
# This option determines whether or not Nagios will attempt to
# automatically reschedule active host and service checks to
# "smooth" them out over time.  This can help balance the load on
# the monitoring server.  
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_reschedule_checks=0



# AUTO-RESCHEDULING INTERVAL
# This option determines how often (in seconds) Nagios will
# attempt to automatically reschedule checks.  This option only
# has an effect if the auto_reschedule_checks option is enabled.
# Default is 30 seconds.
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_interval=30



# AUTO-RESCHEDULING WINDOW
# This option determines the "window" of time (in seconds) that
# Nagios will look at when automatically rescheduling checks.
# Only host and service checks that occur in the next X seconds
# (determined by this variable) will be rescheduled. This option
# only has an effect if the auto_reschedule_checks option is
# enabled.  Default is 180 seconds (3 minutes).
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_window=180



# TIMEOUT VALUES
# These options control how much time Nagios will allow various
# types of commands to execute before killing them off.  Options
# are available for controlling maximum time allotted for
# service checks, host checks, event handlers, notifications, the
# ocsp command, and performance data commands.  All values are in
# seconds.

service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
notification_timeout=30
ocsp_timeout=5
perfdata_timeout=5



# RETAIN STATE INFORMATION
# This setting determines whether or not Nagios will save state
# information for services and hosts before it shuts down.  Upon
# startup Nagios will reload all saved service and host state
# information before starting to monitor.  This is useful for 
# maintaining long-term data on state statistics, etc, but will
# slow Nagios down a bit when it (re)starts.  Since its only
# a one-time penalty, I think its well worth the additional
# startup delay.

retain_state_information=1



# STATE RETENTION FILE
# This is the file that Nagios should use to store host and
# service state information before it shuts down.  The state 
# information in this file is also read immediately prior to
# starting to monitor the network when Nagios is restarted.
# This file is used only if the retain_state_information
# variable is set to 1.

state_retention_file=/usr/local/nagios/var/retention.dat



# RETENTION DATA UPDATE INTERVAL
# This setting determines how often (in minutes) that Nagios
# will automatically save retention data during normal operation.
# If you set this value to 0, Nagios will not save retention
# data at regular interval, but it will still save retention
# data before shutting down or restarting.  If you have disabled
# state retention, this option has no effect.

retention_update_interval=60



# USE RETAINED PROGRAM STATE
# This setting determines whether or not Nagios will set 
# program status variables based on the values saved in the
# retention file.  If you want to use retained program status
# information, set this value to 1.  If not, set this value
# to 0.

use_retained_program_state=1



# USE RETAINED SCHEDULING INFO
# This setting determines whether or not Nagios will retain
# the scheduling info (next check time) for hosts and services
# based on the values saved in the retention file.  If you
# If you want to use retained scheduling info, set this
# value to 1.  If not, set this value to 0.

use_retained_scheduling_info=1



# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
# The following variables are used to specify specific host and
# service attributes that should *not* be retained by Nagios during
# program restarts.
#
# The values of the masks are bitwise ANDs of values specified
# by the "MODATTR_" definitions found in include/common.h.  
# For example, if you do not want the current enabled/disabled state
# of flap detection and event handlers for hosts to be retained, you
# would use a value of 24 for the host attribute mask...
# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24

# This mask determines what host attributes are not retained
retained_host_attribute_mask=0

# This mask determines what service attributes are not retained
retained_service_attribute_mask=0

# These two masks determine what process attributes are not retained.
# There are two masks, because some process attributes have host and service
# options.  For example, you can disable active host checks, but leave active
# service checks enabled.
retained_process_host_attribute_mask=0
retained_process_service_attribute_mask=0

# These two masks determine what contact attributes are not retained.
# There are two masks, because some contact attributes have host and
# service options.  For example, you can disable host notifications for
# a contact, but leave service notifications enabled for them.
retained_contact_host_attribute_mask=0
retained_contact_service_attribute_mask=0



# INTERVAL LENGTH
# This is the seconds per unit interval as used in the
# host/contact/service configuration files.  Setting this to 60 means
# that each interval is one minute long (60 seconds).  Other settings
# have not been tested much, so your mileage is likely to vary...

interval_length=60



# CHECK FOR UPDATES
# This option determines whether Nagios will automatically check to
# see if new updates (releases) are available.  It is recommend that you
# enable this option to ensure that you stay on top of the latest critical
# patches to Nagios.  Nagios is critical to you - make sure you keep it in
# good shape.  Nagios will check once a day for new updates. Data collected
# by Nagios Enterprises from the update check is processed in accordance 
# with our privacy policy - see [url]http://api.nagios.org[/url] for details.

check_for_updates=1



# BARE UPDATE CHECK
# This option deterines what data Nagios will send to api.nagios.org when
# it checks for updates.  By default, Nagios will send information on the 
# current version of Nagios you have installed, as well as an indicator as
# to whether this was a new installation or not.  Nagios Enterprises uses
# this data to determine the number of users running specific version of 
# Nagios.  Enable this option if you do not want this information to be sent.

bare_update_check=0



# AGGRESSIVE HOST CHECKING OPTION
# If you don't want to turn on aggressive host checking features, set
# this value to 0 (the default).  Otherwise set this value to 1 to
# enable the aggressive check option.  Read the docs for more info
# on what aggressive host check is or check out the source code in
# base/checks.c

use_aggressive_host_checking=0



# SERVICE CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# service checks when it initially starts.  If this option is 
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in.  Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of service checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_service_checks=1



# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# service checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_service_checks=1



# HOST CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# host checks when it initially starts.  If this option is 
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in.  Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of host checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_host_checks=1



# PASSIVE HOST CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# host checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_host_checks=1



# NOTIFICATIONS OPTION
# This determines whether or not Nagios will sent out any host or
# service notifications when it is initially (re)started.
# Values: 1 = enable notifications, 0 = disable notifications

enable_notifications=1



# EVENT HANDLER USE OPTION
# This determines whether or not Nagios will run any host or
# service event handlers when it is initially (re)started.  Unless
# you're implementing redundant hosts, leave this option enabled.
# Values: 1 = enable event handlers, 0 = disable event handlers

enable_event_handlers=1



# PROCESS PERFORMANCE DATA OPTION
# This determines whether or not Nagios will process performance
# data returned from service and host checks.  If this option is
# enabled, host performance data will be processed using the
# host_perfdata_command (defined below) and service performance
# data will be processed using the service_perfdata_command (also
# defined below).  Read the HTML docs for more information on
# performance data.
# Values: 1 = process performance data, 0 = do not process performance data

process_performance_data=0



# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed.  These commands are executed only if the
# enable_performance_data option (above) is set to 1.  The command
# argument is the short name of a command definition that you 
# define in your host configuration file.  Read the HTML docs for
# more information on performance data.

#host_perfdata_command=process-host-perfdata
#service_perfdata_command=process-service-perfdata



# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
# enable_performance_data option (above) is set to 1.

#host_perfdata_file=/usr/local/nagios/var/host-perfdata
#service_perfdata_file=/usr/local/nagios/var/service-perfdata



# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
# These options determine what data is written (and how) to the
# performance data files.  The templates may contain macros, special
# characters (\t for tab, \r for carriage return, \n for newline)
# and plain text.  A newline is automatically added after each write
# to the performance data file.  Some examples of what you can do are
# shown below.

#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$



# HOST AND SERVICE PERFORMANCE DATA FILE MODES
# This option determines whether or not the host and service
# performance data files are opened in write ("w") or append ("a")
# mode. If you want to use named pipes, you should use the special
# pipe ("p") mode which avoid blocking at startup, otherwise you will
# likely want the defult append ("a") mode.

#host_perfdata_file_mode=a
#service_perfdata_file_mode=a



# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
# These options determine how often (in seconds) the host and service
# performance data files are processed using the commands defined
# below.  A value of 0 indicates the files should not be periodically
# processed.

#host_perfdata_file_processing_interval=0
#service_perfdata_file_processing_interval=0



# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
# These commands are used to periodically process the host and
# service performance data files.  The interval at which the
# processing occurs is determined by the options above.

#host_perfdata_file_processing_command=process-host-perfdata-file
#service_perfdata_file_processing_command=process-service-perfdata-file



# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
# These options determine wether the core will process empty perfdata
# results or not. This is needed for distributed monitoring, and intentionally
# turned on by default.
# If you don't require empty perfdata - saving some cpu cycles
# on unwanted macro calculation - you can turn that off. Be careful!
# Values: 1 = enable, 0 = disable

#host_perfdata_process_empty_results=1
#service_perfdata_process_empty_results=1


# OBSESS OVER SERVICE CHECKS OPTION
# This determines whether or not Nagios will obsess over service
# checks and run the ocsp_command defined below.  Unless you're
# planning on implementing distributed monitoring, do not enable
# this option.  Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over services, 0 = do not obsess (default)

obsess_over_services=0



# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
# This is the command that is run for every service check that is
# processed by Nagios.  This command is executed only if the
# obsess_over_services option (above) is set to 1.  The command 
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ocsp_command=somecommand



# OBSESS OVER HOST CHECKS OPTION
# This determines whether or not Nagios will obsess over host
# checks and run the ochp_command defined below.  Unless you're
# planning on implementing distributed monitoring, do not enable
# this option.  Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over hosts, 0 = do not obsess (default)

obsess_over_hosts=0



# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
# This is the command that is run for every host check that is
# processed by Nagios.  This command is executed only if the
# obsess_over_hosts option (above) is set to 1.  The command 
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ochp_command=somecommand



# TRANSLATE PASSIVE HOST CHECKS OPTION
# This determines whether or not Nagios will translate
# DOWN/UNREACHABLE passive host check results into their proper
# state for this instance of Nagios.  This option is useful
# if you have distributed or failover monitoring setup.  In
# these cases your other Nagios servers probably have a different
# "view" of the network, with regards to the parent/child relationship
# of hosts.  If a distributed monitoring server thinks a host
# is DOWN, it may actually be UNREACHABLE from the point of
# this Nagios instance.  Enabling this option will tell Nagios
# to translate any DOWN or UNREACHABLE host states it receives
# passively into the correct state from the view of this server.
# Values: 1 = perform translation, 0 = do not translate (default)

translate_passive_host_checks=0



# PASSIVE HOST CHECKS ARE SOFT OPTION
# This determines whether or not Nagios will treat passive host
# checks as being HARD or SOFT.  By default, a passive host check
# result will put a host into a HARD state type.  This can be changed
# by enabling this option.
# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT

passive_host_checks_are_soft=0



# ORPHANED HOST/SERVICE CHECK OPTIONS
# These options determine whether or not Nagios will periodically 
# check for orphaned host service checks.  Since service checks are
# not rescheduled until the results of their previous execution 
# instance are processed, there exists a possibility that some
# checks may never get rescheduled.  A similar situation exists for
# host checks, although the exact scheduling details differ a bit
# from service checks.  Orphaned checks seem to be a rare
# problem and should not happen under normal circumstances.
# If you have problems with service checks never getting
# rescheduled, make sure you have orphaned service checks enabled.
# Values: 1 = enable checks, 0 = disable checks

check_for_orphaned_services=1
check_for_orphaned_hosts=1



# SERVICE FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of service results.  Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_service_freshness=1



# SERVICE FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of service check results.  If you have
# disabled service freshness checking, this option has no effect.

service_freshness_check_interval=60



# SERVICE CHECK TIMEOUT STATE
# This setting determines the state Nagios will report when a
# service check times out - that is does not respond within
# service_check_timeout seconds.  This can be useful if a
# machine is running at too high a load and you do not want
# to consider a failed service check to be critical (the default).
# Valid settings are:
# c - Critical (default)
# u - Unknown
# w - Warning
# o - OK

service_check_timeout_state=c



# HOST FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of host results.  Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_host_freshness=0



# HOST FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of host check results.  If you have
# disabled host freshness checking, this option has no effect.

host_freshness_check_interval=60




# ADDITIONAL FRESHNESS THRESHOLD LATENCY
# This setting determines the number of seconds that Nagios
# will add to any host and service freshness thresholds that
# it calculates (those not explicitly specified by the user).

additional_freshness_latency=15




# FLAP DETECTION OPTION
# This option determines whether or not Nagios will try
# and detect hosts and services that are "flapping".  
# Flapping occurs when a host or service changes between
# states too frequently.  When Nagios detects that a 
# host or service is flapping, it will temporarily suppress
# notifications for that host/service until it stops
# flapping.  Flap detection is very experimental, so read
# the HTML documentation before enabling this feature!
# Values: 1 = enable flap detection
#         0 = disable flap detection (default)

enable_flap_detection=1



# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
# Read the HTML documentation on flap detection for
# an explanation of what this option does.  This option
# has no effect if flap detection is disabled.

low_service_flap_threshold=5.0
high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0



# DATE FORMAT OPTION
# This option determines how short dates are displayed. Valid options
# include:
#	us		(MM-DD-YYYY HH:MM:SS)
#	euro    	(DD-MM-YYYY HH:MM:SS)
#	iso8601		(YYYY-MM-DD HH:MM:SS)
#	strict-iso8601	(YYYY-MM-DDTHH:MM:SS)
#

date_format=us




# TIMEZONE OFFSET
# This option is used to override the default timezone that this
# instance of Nagios runs in.  If not specified, Nagios will use
# the system configured timezone.
#
# NOTE: In order to display the correct timezone in the CGIs, you
# will also need to alter the Apache directives for the CGI path 
# to include your timezone.  Example:
#
#   <Directory "/usr/local/nagios/sbin/">
#      SetEnv TZ "Australia/Brisbane"
#      ...
#   </Directory>

#use_timezone=US/Mountain
#use_timezone=Australia/Brisbane



# ILLEGAL OBJECT NAME CHARACTERS
# This option allows you to specify illegal characters that cannot
# be used in host names, service descriptions, or names of other
# object types.

illegal_object_name_chars=`~!$%^&*|'"<>?,()=



# ILLEGAL MACRO OUTPUT CHARACTERS
# This option allows you to specify illegal characters that are
# stripped from macros before being used in notifications, event
# handlers, etc.  This DOES NOT affect macros used in service or
# host check commands.
# The following macros are stripped of the characters you specify:
#	$HOSTOUTPUT$
#	$HOSTPERFDATA$
#	$HOSTACKAUTHOR$
#	$HOSTACKCOMMENT$
#	$SERVICEOUTPUT$
#	$SERVICEPERFDATA$
#	$SERVICEACKAUTHOR$
#	$SERVICEACKCOMMENT$

illegal_macro_output_chars=`~$&|'"<>



# REGULAR EXPRESSION MATCHING
# This option controls whether or not regular expression matching
# takes place in the object config files.  Regular expression
# matching is used to match host, hostgroup, service, and service
# group names/descriptions in some fields of various object types.
# Values: 1 = enable regexp matching, 0 = disable regexp matching

use_regexp_matching=0



# "TRUE" REGULAR EXPRESSION MATCHING
# This option controls whether or not "true" regular expression 
# matching takes place in the object config files.  This option
# only has an effect if regular expression matching is enabled
# (see above).  If this option is DISABLED, regular expression
# matching only occurs if a string contains wildcard characters
# (* and ?).  If the option is ENABLED, regexp matching occurs
# all the time (which can be annoying).
# Values: 1 = enable true matching, 0 = disable true matching

use_true_regexp_matching=0



# ADMINISTRATOR EMAIL/PAGER ADDRESSES
# The email and pager address of a global administrator (likely you).
# Nagios never uses these values itself, but you can access them by
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
# commands.

admin_email=nagios@localhost
admin_pager=pagenagios@localhost



# DAEMON CORE DUMP OPTION
# This option determines whether or not Nagios is allowed to create
# a core dump when it runs as a daemon.  Note that it is generally
# considered bad form to allow this, but it may be useful for
# debugging purposes.  Enabling this option doesn't guarantee that
# a core file will be produced, but that's just life...
# Values: 1 - Allow core dumps
#         0 - Do not allow core dumps (default)

daemon_dumps_core=0



# LARGE INSTALLATION TWEAKS OPTION
# This option determines whether or not Nagios will take some shortcuts
# which can save on memory and CPU usage in large Nagios installations.
# Read the documentation for more information on the benefits/tradeoffs
# of enabling this option.
# Values: 1 - Enabled tweaks
#         0 - Disable tweaks (default)

use_large_installation_tweaks=0



# ENABLE ENVIRONMENT MACROS
# This option determines whether or not Nagios will make all standard
# macros available as environment variables when host/service checks
# and system commands (event handlers, notifications, etc.) are
# executed.
# Enabling this is a very bad idea for anything but very small setups,
# as it means plugins, notification scripts and eventhandlers may run
# out of environment space. It will also cause a significant increase
# in CPU- and memory usage and drastically reduce the number of checks
# you can run.
# Values: 1 - Enable environment variable macros
#         0 - Disable environment variable macros (default)

enable_environment_macros=0



# CHILD PROCESS MEMORY OPTION
# This option determines whether or not Nagios will free memory in
# child processes (processed used to execute system commands and host/
# service checks).  If you specify a value here, it will override
# program defaults.
# Value: 1 - Free memory in child processes
#        0 - Do not free memory in child processes

#free_child_process_memory=1



# CHILD PROCESS FORKING BEHAVIOR
# This option determines how Nagios will fork child processes
# (used to execute system commands and host/service checks).  Normally
# child processes are fork()ed twice, which provides a very high level
# of isolation from problems.  Fork()ing once is probably enough and will
# save a great deal on CPU usage (in large installs), so you might
# want to consider using this.  If you specify a value here, it will
# program defaults.
# Value: 1 - Child processes fork() twice
#        0 - Child processes fork() just once

#child_processes_fork_twice=1



# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file.  OR values together to log multiple
# types of information.
# Values: 
#          -1 = Everything
#          0 = Nothing
#	   1 = Functions
#          2 = Configuration
#          4 = Process information
#	   8 = Scheduled events
#          16 = Host/service checks
#          32 = Notifications
#          64 = Event broker
#          128 = External commands
#          256 = Commands
#          512 = Scheduled downtime
#          1024 = Comments
#          2048 = Macros

debug_level=0



# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
#         1 = More detailed
#         2 = Very detailed

debug_verbosity=1



# DEBUG FILE
# This option determines where Nagios should write debugging information.

debug_file=/usr/local/nagios/var/nagios.debug



# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file.  If
# the file grows larger than this size, it will be renamed with a .old
# extension.  If a file already exists with a .old extension it will
# automatically be deleted.  This helps ensure your disk space usage doesn't
# get out of control when debugging Nagios.

max_debug_file_size=1000000



# Should we allow hostgroups to have no hosts, we default this to off since
# that was the old behavior

allow_empty_hostgroup_assignment=0



# Normally worker count is dynamically allocated based on 1.5 * number of cpu's
# with a minimum of 4 workers.  This value will override the defaults

#check_workers=3



# EXPERIMENTAL load controlling options
# To get current defaults based on your system issue a command to
# the query handler. Please note that this is an experimental feature
# and not meant for production use. Used incorrectly it can induce
# enormous latency.
# #core loadctl
#   jobs_max - The maximum amount of jobs to run at one time
#   jobs_min - The minimum amount of jobs to run at one time
#   jobs_limit - The maximum amount of jobs the current load lets us run
#   backoff_limit - The minimum backoff_change
#   backoff_change - # of jobs to remove from jobs_limit when backing off
#   rampup_limit - Minimum rampup_change
#   rampup_change - # of jobs to add to jobs_limit when ramping up
# NOTE: The backoff_limit and rampup_limit are NOT used by anything currently,
#       so if your system is under load nothing will actively modify the jobs
#       even if you have these options enabled, they are for external
#       connector information only.  However, if you change the jobs_max or
#       jobs_min manually here or through the query handler interface that
#       WILL affect your system
#loadctl_options=jobs_max=100;backoff_limit=10;rampup_change=5

- Config de Postfix :

# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

mydomain = *****.com
myhostname = *****.com
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = *****.com
mydestination = *****.com, nagios, localhost.localdomain, localhost
relayhost = 93.17.128.23
mynetworks = 127.0.0.1/32,10.1.1.0/24
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 10000
recipient_delimiter = +
inet_interfaces = loopback-only
inet_protocols = all

- Fichier de config "contacts.cfg"

###############################################################################
# CONTACTS.CFG - SAMPLE CONTACT/CONTACTGROUP DEFINITIONS
#
#
# NOTES: This config file provides you with some example contact and contact
#        group definitions that you can reference in host and service
#        definitions.
#       
#        You don't need to keep these definitions in a separate file from your
#        other object definitions.  This has been done just to make things
#        easier to understand.
#
###############################################################################



###############################################################################
###############################################################################
#
# CONTACTS
#
###############################################################################
###############################################################################

# Just one contact defined by default - the Nagios admin (that's you)
# This contact definition inherits a lot of default values from the 'generic-contact' 
# template which is defined elsewhere.

define contact{
        contact_name                    nagiosadmin		; Short name of user
	use				generic-contact		; Inherit default values from generic-contact template (defined above)
        alias                           Nagios Admin		; Full name of user

        email                           sysinfo@*****.com	; <<***** CHANGE THIS TO YOUR EMAIL ADDRESS ******
        }



###############################################################################
###############################################################################
#
# CONTACT GROUPS
#
###############################################################################
###############################################################################

# We only have one contact in this simple configuration file, so there is
# no need to create more than one contact group.

define contactgroup{
        contactgroup_name       admins
        alias                   Nagios Administrators
        members                 nagiosadmin
        }

S'il manque quelque chose, n'hésitez pas ;-)

Pour info également, je passe par un serveur SMTP externe pour l'envoi des emails (smtp.sfr.fr par exemple).

(sinon, non, je suis ouvert à toutes propositions, j'ai pris Nagios car un de mes amis me l'avait conseillé, mais si quelque chose de mieux existe... ).

Merci par avance !

Bonne journée.
Tom.

Dernière modification par TomHawk (Le 18/03/2014, à 09:49)

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

1/ Pour la configuration de Nagios, elle est éclatée dans plusieurs fichiers.
Ce qu'il nous faut, c'est le fichier qui contient la commande utilisée pour les notifications.

2/ As-tu déjà validé l'envoi d'e-mail sans Nagios ?

-----

sinon, non, je suis ouvert à toutes propositions, j'ai pris Nagios car un de mes amis me l'avait conseillé, mais si quelque chose de mieux existe...

Zabbix. Plus complet et plus homogène. Il y a des concepts à acquérir mais c'est assez simple une fois compris.
Et vu que je suis sympathique, je t'ai déjà prémâché le travail là :
http://boutique.ed-diamond.com/gnulinux … lm158.html

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Bonjour,

1/ Je ne sais pas de quel fichier tu parles... Je n'y connais pas grand chose à Nagios, j'ai essayé de suivre quelques tutos sur Internet mais ma connaissance est limitée sur cet outil .
2/ Non, je sais qu'il existe une commande Mail, mais pas essayé

Merci pour le lien ! Je vais me renseigner. Mais j'avais déjà jeté un oeil à Zabbix, trop complet pour l'utilisation que j'en ferais...

Merci par avance,

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Mais j'avais déjà jeté un oeil à Zabbix, trop complet pour l'utilisation que j'en ferais...

Ah ben si tu veux juste avoir une alerte par e-mail quand tu as un problème et que l'historique ne t'intéresse pas, c'est sûr que ça fait un peu gros...
Mais bon, tu as parlé de supervision d'un réseau d'entreprise (même s'il n'a que 3 machines), tu n'as pas parlé juste d'envoyer une alerte par-ci par-là.

1/ Je ne sais pas de quel fichier tu parles... Je n'y connais pas grand chose à Nagios, j'ai essayé de suivre quelques tutos

Lis de la documentation, alors. Tu ne pourras rien faire d'efficace si tu n'apprends pas un peu

2/ Non, je sais qu'il existe une commande Mail, mais pas essayé

Il faut commencer par valider que l'envoi d'e-mail tout court fonctionne, avant d'essayer de valider l'envoi d'e-mail par Nagios...

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Oui, mon souhait en toute simplicité, c'est d'avoir une map de mon réseau, avec les parents etc... Et lorsqu'un de ces périphériques ne répond plus aux pings, hop je reçois un petit mail
J'ai vSphere pour la maintenance générale .

Voici d'autres fichiers de configuration :

- Fichier resource.cfg :

###########################################################################
#
# RESOURCE.CFG - Sample Resource File for Nagios 4.0.3
#
#
# You can define $USERx$ macros in this file, which can in turn be used
# in command definitions in your host config file(s).  $USERx$ macros are
# useful for storing sensitive information such as usernames, passwords, 
# etc.  They are also handy for specifying the path to plugins and 
# event handlers - if you decide to move the plugins or event handlers to
# a different directory in the future, you can just update one or two
# $USERx$ macros, instead of modifying a lot of command definitions.
#
# The CGIs will not attempt to read the contents of resource files, so
# you can set restrictive permissions (600 or 660) on them.
#
# Nagios supports up to 32 $USERx$ macros ($USER1$ through $USER32$)
#
# Resource files may also be used to store configuration directives for
# external data sources like MySQL...
#
###########################################################################

# Sets $USER1$ to be the path to the plugins
$USER1$=/usr/local/nagios/libexec

# Sets $USER2$ to be the path to event handlers
#$USER2$=/usr/local/nagios/libexec/eventhandlers

# Store some usernames and passwords (hidden from the CGIs)
#$USER3$=someuser
#$USER4$=somepassword
$USERS5$=nagios@*****.com
$USER7$=93.17.128.5

- Fichier commands.cfg :

###############################################################################
# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS 4.0.3
#
#
# NOTES: This config file provides you with some example command definitions
#        that you can reference in host, service, and contact definitions.
#       
#        You don't need to keep commands in a separate file from your other
#        object definitions.  This has been done just to make things easier to
#        understand.
#
###############################################################################


################################################################################
#
# SAMPLE NOTIFICATION COMMANDS
#
# These are some example notification commands.  They may or may not work on
# your system without modification.  As an example, some systems will require 
# you to use "/usr/bin/mailx" instead of "/usr/bin/mail" in the commands below.
#
################################################################################


# 'notify-host-by-email' command definition
define command{
    command_name    notify-host-by-email
    command_line    /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
    }

# 'notify-service-by-email' command definition
define command{
    command_name    notify-service-by-email
    command_line    /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
    }





################################################################################
#
# SAMPLE HOST CHECK COMMANDS
#
################################################################################


# This command checks to see if a host is "alive" by pinging it
# The check must result in a 100% packet loss or 5 second (5000ms) round trip 
# average time to produce a critical error.
# Note: Five ICMP echo packets are sent (determined by the '-p 5' argument)

# 'check-host-alive' command definition
define command{
        command_name    check-host-alive
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 5
        }




################################################################################
#
# SAMPLE SERVICE CHECK COMMANDS
#
# These are some example service check commands.  They may or may not work on
# your system, as they must be modified for your plugins.  See the HTML 
# documentation on the plugins for examples of how to configure command definitions.
#
# NOTE:  The following 'check_local_...' functions are designed to monitor
#        various metrics on the host that Nagios is running on (i.e. this one).
################################################################################

# 'check_local_disk' command definition
define command{
        command_name    check_local_disk
        command_line    $USER1$/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
        }


# 'check_local_load' command definition
define command{
        command_name    check_local_load
        command_line    $USER1$/check_load -w $ARG1$ -c $ARG2$
        }


# 'check_local_procs' command definition
define command{
        command_name    check_local_procs
        command_line    $USER1$/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
        }


# 'check_local_users' command definition
define command{
        command_name    check_local_users
        command_line    $USER1$/check_users -w $ARG1$ -c $ARG2$
        }


# 'check_local_swap' command definition
define command{
	command_name	check_local_swap
	command_line	$USER1$/check_swap -w $ARG1$ -c $ARG2$
	}


# 'check_local_mrtgtraf' command definition
define command{
	command_name	check_local_mrtgtraf
	command_line	$USER1$/check_mrtgtraf -F $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -e $ARG5$
	}


################################################################################
# NOTE:  The following 'check_...' commands are used to monitor services on
#        both local and remote hosts.
################################################################################

# 'check_ftp' command definition
define command{
        command_name    check_ftp
        command_line    $USER1$/check_ftp -H $HOSTADDRESS$ $ARG1$
        }


# 'check_hpjd' command definition
define command{
        command_name    check_hpjd
        command_line    $USER1$/check_hpjd -H $HOSTADDRESS$ $ARG1$
        }


# 'check_snmp' command definition
define command{
        command_name    check_snmp
        command_line    $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
        }


# 'check_http' command definition
define command{
        command_name    check_http
        command_line    $USER1$/check_http -I $HOSTADDRESS$ $ARG1$
        }


# 'check_ssh' command definition
define command{
	command_name	check_ssh
	command_line	$USER1$/check_ssh $ARG1$ $HOSTADDRESS$
	}


# 'check_dhcp' command definition
define command{
	command_name	check_dhcp
	command_line	$USER1$/check_dhcp $ARG1$
	}


# 'check_ping' command definition
define command{
        command_name    check_ping
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5
        }


# 'check_pop' command definition
define command{
        command_name    check_pop
        command_line    $USER1$/check_pop -H $HOSTADDRESS$ $ARG1$
        }


# 'check_imap' command definition
define command{
        command_name    check_imap
        command_line    $USER1$/check_imap -H $HOSTADDRESS$ $ARG1$
        }


# 'check_smtp' command definition
define command{
        command_name    check_smtp
        command_line    $USER1$/check_smtp -H $HOSTADDRESS$ $ARG1$
        }


# 'check_tcp' command definition
define command{
	command_name	check_tcp
	command_line	$USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
	}


# 'check_udp' command definition
define command{
	command_name	check_udp
	command_line	$USER1$/check_udp -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
	}


# 'check_nt' command definition
define command{
	command_name	check_nt
	command_line	$USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -v $ARG1$ $ARG2$
	}



################################################################################
#
# SAMPLE PERFORMANCE DATA COMMANDS
#
# These are sample performance data commands that can be used to send performance
# data output to two text files (one for hosts, another for services).  If you
# plan on simply writing performance data out to a file, consider using the 
# host_perfdata_file and service_perfdata_file options in the main config file.
#
################################################################################


# 'process-host-perfdata' command definition
define command{
	command_name	process-host-perfdata
	command_line	/usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /usr/local/nagios/var/host-perfdata.out
	}


# 'process-service-perfdata' command definition
define command{
	command_name	process-service-perfdata
	command_line	/usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /usr/local/nagios/var/service-perfdata.out
	}

Par ailleurs, j'ai utilisé cette commande pour un envoi de mail lambda :

echo "Test message" | mail -s "test mail" bs***@*****.com

Seulement, je n'ai rien reçu

Voilà voilà !

Merci
Tom.

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Oui, mon souhait en toute simplicité, c'est d'avoir une map de mon réseau, avec les parents etc... Et lorsqu'un de ces périphériques ne répond plus aux pings, hop je reçois un petit mail

Uniquement les pings ?
Tu ne veux pas surveiller l'utilisation processeur, mémoire, disque dur, la présence et le fonctionnement des différents services, garder des historiques, des graphiques, faire de la maintenance préventive, tout ça ?
Si tu ne veux faire que des pings, oui tu peux te contenter de Nagios. Mais bon, les pings c'est comme ça qu'on faisait de la supervision au siècle dernier...

Par ailleurs, j'ai utilisé cette commande pour un envoi de mail lambda :

echo "Test message" | mail -s "test mail" bs***@*****.com

Seulement, je n'ai rien reçu

Donc avant de t'intéresser aux notifications de Nagios, il faut que tu te penches sur le fonctionnement des e-mails.

Que trouves-tu dans les logs de Postfix (/var/log/mail.log) à propos de ton test ?

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Uniquement les pings tout à fait. En fait, Nagios m'intéresse pour la map, et pour la simplicité. Quand un hôte lâche, je reçois un mail . Pour le reste, j'utilise comme je l'ai dit vSphere, qui regroupe mes serveurs virtuels.
Mais honnêtement, si tu as un outil qui ressemble à Nagios qui permet de faire des surveillances de ping et qui affiche une map, je suis preneur .

Alors dans mes logs, j'ai ceci : (je n'ai mis que la fin)

Mar 18 08:28:05 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 7957 exit status 1
Mar 18 08:28:05 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:29:05 nagios postfix/local[7963]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:29:06 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 7963 exit status 1
Mar 18 08:29:06 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:30:06 nagios postfix/local[7972]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:30:07 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 7972 exit status 1
Mar 18 08:30:07 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:31:07 nagios postfix/local[7973]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:31:08 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 7973 exit status 1
Mar 18 08:31:08 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:32:08 nagios postfix/local[8005]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:32:09 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8005 exit status 1
Mar 18 08:32:09 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:33:09 nagios postfix/local[8048]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:33:10 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8048 exit status 1
Mar 18 08:33:10 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:34:10 nagios postfix/local[8086]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:34:11 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8086 exit status 1
Mar 18 08:34:11 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:35:11 nagios postfix/local[8092]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:35:12 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8092 exit status 1
Mar 18 08:35:12 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:36:12 nagios postfix/local[8117]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:36:13 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8117 exit status 1
Mar 18 08:36:13 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:37:13 nagios postfix/local[8152]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:37:14 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8152 exit status 1
Mar 18 08:37:14 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:38:14 nagios postfix/local[8160]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:38:15 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8160 exit status 1
Mar 18 08:38:15 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:39:15 nagios postfix/local[8172]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:39:16 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8172 exit status 1
Mar 18 08:39:16 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:40:16 nagios postfix/local[8174]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:40:17 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8174 exit status 1
Mar 18 08:40:17 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:41:17 nagios postfix/local[8176]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:41:18 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8176 exit status 1
Mar 18 08:41:18 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:42:18 nagios postfix/local[8178]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:42:19 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8178 exit status 1
Mar 18 08:42:19 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:43:19 nagios postfix/local[8181]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:43:20 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8181 exit status 1
Mar 18 08:43:20 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:44:20 nagios postfix/local[8183]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:44:21 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8183 exit status 1
Mar 18 08:44:21 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:45:21 nagios postfix/local[8185]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:45:22 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8185 exit status 1
Mar 18 08:45:22 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:46:22 nagios postfix/local[8187]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:46:23 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8187 exit status 1
Mar 18 08:46:23 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:47:23 nagios postfix/local[8189]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:47:24 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8189 exit status 1
Mar 18 08:47:24 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:48:24 nagios postfix/local[8190]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:48:25 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8190 exit status 1
Mar 18 08:48:25 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:49:25 nagios postfix/local[8191]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:49:26 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8191 exit status 1
Mar 18 08:49:26 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:50:26 nagios postfix/local[8193]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:50:27 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8193 exit status 1
Mar 18 08:50:27 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:51:27 nagios postfix/local[8195]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:51:28 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8195 exit status 1
Mar 18 08:51:28 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:52:28 nagios postfix/local[8197]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:52:29 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8197 exit status 1
Mar 18 08:52:29 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:53:29 nagios postfix/local[8204]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:53:30 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8204 exit status 1
Mar 18 08:53:30 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:54:30 nagios postfix/local[8205]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:54:31 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8205 exit status 1
Mar 18 08:54:31 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:55:31 nagios postfix/local[8206]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:55:32 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8206 exit status 1
Mar 18 08:55:32 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:56:32 nagios postfix/local[8208]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:56:33 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8208 exit status 1
Mar 18 08:56:33 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:57:33 nagios postfix/local[8210]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:57:34 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8210 exit status 1
Mar 18 08:57:34 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:58:34 nagios postfix/local[8212]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:58:35 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8212 exit status 1
Mar 18 08:58:35 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 08:59:35 nagios postfix/local[8213]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 08:59:36 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8213 exit status 1
Mar 18 08:59:36 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:00:36 nagios postfix/local[8216]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:00:37 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8216 exit status 1
Mar 18 09:00:37 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:01:37 nagios postfix/local[8217]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:01:38 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8217 exit status 1
Mar 18 09:01:38 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:02:38 nagios postfix/local[8219]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:02:39 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8219 exit status 1
Mar 18 09:02:39 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:03:39 nagios postfix/local[8221]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:03:40 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8221 exit status 1
Mar 18 09:03:40 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:04:40 nagios postfix/local[8222]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:04:41 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8222 exit status 1
Mar 18 09:04:41 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:05:41 nagios postfix/local[8224]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:05:42 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8224 exit status 1
Mar 18 09:05:42 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:06:42 nagios postfix/local[8227]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:06:43 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8227 exit status 1
Mar 18 09:06:43 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:07:43 nagios postfix/local[8229]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:07:44 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8229 exit status 1
Mar 18 09:07:44 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:08:45 nagios postfix/local[8231]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:08:46 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8231 exit status 1
Mar 18 09:08:46 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:09:46 nagios postfix/local[8240]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:09:47 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8240 exit status 1
Mar 18 09:09:47 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:10:47 nagios postfix/local[8241]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:10:48 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8241 exit status 1
Mar 18 09:10:48 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:11:48 nagios postfix/local[8244]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:11:49 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8244 exit status 1
Mar 18 09:11:49 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:12:49 nagios postfix/local[8246]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:12:50 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8246 exit status 1
Mar 18 09:12:50 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:13:50 nagios postfix/local[8248]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:13:51 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8248 exit status 1
Mar 18 09:13:51 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:14:51 nagios postfix/local[8250]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:14:52 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8250 exit status 1
Mar 18 09:14:52 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:15:52 nagios postfix/local[8251]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:15:53 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8251 exit status 1
Mar 18 09:15:53 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:16:53 nagios postfix/local[8254]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:16:54 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8254 exit status 1
Mar 18 09:16:54 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:17:54 nagios postfix/local[8259]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:17:55 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8259 exit status 1
Mar 18 09:17:55 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:18:55 nagios postfix/local[8261]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:18:56 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8261 exit status 1
Mar 18 09:18:56 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:19:56 nagios postfix/local[8263]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:19:57 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8263 exit status 1
Mar 18 09:19:57 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:20:57 nagios postfix/local[8264]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:20:58 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8264 exit status 1
Mar 18 09:20:58 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:21:58 nagios postfix/local[8266]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:21:59 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8266 exit status 1
Mar 18 09:21:59 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:22:59 nagios postfix/local[8268]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:23:00 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8268 exit status 1
Mar 18 09:23:00 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:24:00 nagios postfix/local[8270]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:24:01 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8270 exit status 1
Mar 18 09:24:01 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:25:01 nagios postfix/local[8272]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:25:02 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8272 exit status 1
Mar 18 09:25:02 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:26:02 nagios postfix/local[8273]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:26:03 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8273 exit status 1
Mar 18 09:26:03 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:27:03 nagios postfix/local[8275]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:27:04 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8275 exit status 1
Mar 18 09:27:04 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:28:04 nagios postfix/local[8277]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:28:05 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8277 exit status 1
Mar 18 09:28:05 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:29:06 nagios postfix/local[8278]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:29:07 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8278 exit status 1
Mar 18 09:29:07 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:30:07 nagios postfix/local[8280]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:30:08 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8280 exit status 1
Mar 18 09:30:08 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:31:08 nagios postfix/local[8281]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:31:09 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8281 exit status 1
Mar 18 09:31:09 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:32:09 nagios postfix/local[8283]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:32:10 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8283 exit status 1
Mar 18 09:32:10 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:33:10 nagios postfix/local[8285]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:33:11 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8285 exit status 1
Mar 18 09:33:11 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:34:11 nagios postfix/local[8287]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:34:12 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8287 exit status 1
Mar 18 09:34:12 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:35:12 nagios postfix/local[8289]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:35:13 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8289 exit status 1
Mar 18 09:35:13 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:36:13 nagios postfix/local[8291]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:36:14 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8291 exit status 1
Mar 18 09:36:14 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:37:14 nagios postfix/local[8292]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:37:15 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8292 exit status 1
Mar 18 09:37:15 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:38:15 nagios postfix/local[8294]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:38:16 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8294 exit status 1
Mar 18 09:38:16 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:39:16 nagios postfix/local[8304]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:39:17 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8304 exit status 1
Mar 18 09:39:17 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:40:17 nagios postfix/local[8306]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:40:18 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8306 exit status 1
Mar 18 09:40:18 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:41:18 nagios postfix/local[8308]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:41:19 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8308 exit status 1
Mar 18 09:41:19 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:42:19 nagios postfix/local[8310]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:42:20 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8310 exit status 1
Mar 18 09:42:20 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:43:20 nagios postfix/local[8312]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:43:21 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8312 exit status 1
Mar 18 09:43:21 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:44:21 nagios postfix/local[8314]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:44:22 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8314 exit status 1
Mar 18 09:44:22 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:45:22 nagios postfix/local[8316]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:45:23 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8316 exit status 1
Mar 18 09:45:23 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:46:23 nagios postfix/local[8317]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:46:24 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8317 exit status 1
Mar 18 09:46:24 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:47:24 nagios postfix/local[8319]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:47:25 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8319 exit status 1
Mar 18 09:47:25 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:48:25 nagios postfix/local[8321]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:48:26 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8321 exit status 1
Mar 18 09:48:26 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:49:26 nagios postfix/local[8323]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:49:27 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8323 exit status 1
Mar 18 09:49:27 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:50:27 nagios postfix/local[8325]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:50:28 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8325 exit status 1
Mar 18 09:50:28 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:51:28 nagios postfix/local[8327]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:51:29 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8327 exit status 1
Mar 18 09:51:29 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:52:29 nagios postfix/local[8329]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:52:30 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8329 exit status 1
Mar 18 09:52:30 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:53:30 nagios postfix/local[8331]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:53:31 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8331 exit status 1
Mar 18 09:53:31 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:54:31 nagios postfix/local[8333]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:54:32 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8333 exit status 1
Mar 18 09:54:32 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:55:32 nagios postfix/local[8335]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:55:33 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8335 exit status 1
Mar 18 09:55:33 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:56:33 nagios postfix/local[8336]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:56:34 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8336 exit status 1
Mar 18 09:56:34 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:57:34 nagios postfix/local[8338]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:57:35 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8338 exit status 1
Mar 18 09:57:35 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:58:35 nagios postfix/local[8340]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:58:36 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8340 exit status 1
Mar 18 09:58:36 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 09:59:36 nagios postfix/local[8343]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 09:59:37 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8343 exit status 1
Mar 18 09:59:37 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:00:37 nagios postfix/local[8345]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:00:38 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8345 exit status 1
Mar 18 10:00:38 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:01:38 nagios postfix/local[8346]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:01:39 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8346 exit status 1
Mar 18 10:01:39 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:02:39 nagios postfix/local[8351]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:02:40 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8351 exit status 1
Mar 18 10:02:40 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:03:40 nagios postfix/local[8353]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:03:41 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8353 exit status 1
Mar 18 10:03:41 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:04:41 nagios postfix/local[8355]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:04:42 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8355 exit status 1
Mar 18 10:04:42 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:05:42 nagios postfix/local[8357]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:05:43 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8357 exit status 1
Mar 18 10:05:43 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:06:43 nagios postfix/local[8360]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:06:44 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8360 exit status 1
Mar 18 10:06:44 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:07:44 nagios postfix/local[8361]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:07:45 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8361 exit status 1
Mar 18 10:07:45 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:08:45 nagios postfix/local[8365]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:08:46 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8365 exit status 1
Mar 18 10:08:46 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:09:46 nagios postfix/local[8374]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:09:47 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8374 exit status 1
Mar 18 10:09:47 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:10:47 nagios postfix/local[8376]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:10:48 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8376 exit status 1
Mar 18 10:10:48 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:11:48 nagios postfix/local[8377]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:11:49 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8377 exit status 1
Mar 18 10:11:49 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:12:49 nagios postfix/local[8378]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:12:50 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8378 exit status 1
Mar 18 10:12:50 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:13:50 nagios postfix/local[8381]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:13:51 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8381 exit status 1
Mar 18 10:13:51 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:14:51 nagios postfix/local[8383]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:14:52 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8383 exit status 1
Mar 18 10:14:52 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:15:52 nagios postfix/local[8385]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:15:53 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8385 exit status 1
Mar 18 10:15:53 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:16:53 nagios postfix/local[8387]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:16:54 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8387 exit status 1
Mar 18 10:16:54 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:17:54 nagios postfix/local[8391]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:17:55 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8391 exit status 1
Mar 18 10:17:55 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:18:55 nagios postfix/local[8393]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:18:56 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8393 exit status 1
Mar 18 10:18:56 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:19:56 nagios postfix/local[8395]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:19:57 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8395 exit status 1
Mar 18 10:19:57 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:20:57 nagios postfix/local[8397]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:20:58 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8397 exit status 1
Mar 18 10:20:58 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:21:58 nagios postfix/local[8398]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:21:59 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8398 exit status 1
Mar 18 10:21:59 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:22:59 nagios postfix/local[8399]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:23:00 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8399 exit status 1
Mar 18 10:23:00 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:24:00 nagios postfix/local[8401]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:24:01 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8401 exit status 1
Mar 18 10:24:01 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:25:01 nagios postfix/local[8403]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:25:02 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8403 exit status 1
Mar 18 10:25:02 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:26:02 nagios postfix/local[8405]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:26:03 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8405 exit status 1
Mar 18 10:26:03 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:27:03 nagios postfix/local[8407]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:27:04 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8407 exit status 1
Mar 18 10:27:04 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:28:04 nagios postfix/local[8408]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:28:05 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8408 exit status 1
Mar 18 10:28:05 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:29:06 nagios postfix/local[8410]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:29:07 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8410 exit status 1
Mar 18 10:29:07 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:30:07 nagios postfix/local[8413]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:30:08 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8413 exit status 1
Mar 18 10:30:08 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:31:08 nagios postfix/local[8415]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:31:09 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8415 exit status 1
Mar 18 10:31:09 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:32:09 nagios postfix/local[8416]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:32:10 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8416 exit status 1
Mar 18 10:32:10 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:33:10 nagios postfix/local[8418]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:33:11 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8418 exit status 1
Mar 18 10:33:11 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:34:11 nagios postfix/local[8419]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:34:12 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8419 exit status 1
Mar 18 10:34:12 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:35:12 nagios postfix/local[8420]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:35:13 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8420 exit status 1
Mar 18 10:35:13 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:36:13 nagios postfix/local[8421]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:36:14 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8421 exit status 1
Mar 18 10:36:14 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:37:14 nagios postfix/local[8422]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:37:15 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8422 exit status 1
Mar 18 10:37:15 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:38:15 nagios postfix/local[8454]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:38:16 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8454 exit status 1
Mar 18 10:38:16 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:39:16 nagios postfix/local[8470]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:39:17 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8470 exit status 1
Mar 18 10:39:17 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:40:17 nagios postfix/local[8472]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:40:18 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8472 exit status 1
Mar 18 10:40:18 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:41:18 nagios postfix/local[8477]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:41:19 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8477 exit status 1
Mar 18 10:41:19 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:42:19 nagios postfix/local[8480]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:42:20 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8480 exit status 1
Mar 18 10:42:20 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:43:20 nagios postfix/local[8482]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:43:21 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8482 exit status 1
Mar 18 10:43:21 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:44:21 nagios postfix/local[8483]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:44:22 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8483 exit status 1
Mar 18 10:44:22 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:45:22 nagios postfix/local[8484]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:45:23 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8484 exit status 1
Mar 18 10:45:23 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:46:23 nagios postfix/local[8485]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:46:24 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8485 exit status 1
Mar 18 10:46:24 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:47:24 nagios postfix/local[8486]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:47:25 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8486 exit status 1
Mar 18 10:47:25 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:48:25 nagios postfix/local[8487]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:48:26 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8487 exit status 1
Mar 18 10:48:26 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:49:26 nagios postfix/local[8488]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:49:27 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8488 exit status 1
Mar 18 10:49:27 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:50:27 nagios postfix/local[8489]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:50:28 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8489 exit status 1
Mar 18 10:50:28 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:51:28 nagios postfix/local[8490]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:51:29 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8490 exit status 1
Mar 18 10:51:29 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:52:29 nagios postfix/local[8491]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:52:30 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8491 exit status 1
Mar 18 10:52:30 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:53:30 nagios postfix/local[8492]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:53:31 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8492 exit status 1
Mar 18 10:53:31 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:54:31 nagios postfix/local[8493]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:54:32 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8493 exit status 1
Mar 18 10:54:32 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:55:32 nagios postfix/local[8494]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:55:33 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8494 exit status 1
Mar 18 10:55:33 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:56:33 nagios postfix/local[8495]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:56:34 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8495 exit status 1
Mar 18 10:56:34 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:57:34 nagios postfix/local[8496]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:57:35 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8496 exit status 1
Mar 18 10:57:35 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:58:35 nagios postfix/local[8497]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:58:36 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8497 exit status 1
Mar 18 10:58:36 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 10:59:36 nagios postfix/local[8498]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 10:59:37 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8498 exit status 1
Mar 18 10:59:37 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:00:37 nagios postfix/local[8499]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:00:38 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8499 exit status 1
Mar 18 11:00:38 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:01:38 nagios postfix/local[8500]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:01:39 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8500 exit status 1
Mar 18 11:01:39 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:02:39 nagios postfix/local[8501]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:02:40 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8501 exit status 1
Mar 18 11:02:40 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:03:40 nagios postfix/local[8503]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:03:41 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8503 exit status 1
Mar 18 11:03:41 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:04:41 nagios postfix/local[8504]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:04:42 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8504 exit status 1
Mar 18 11:04:42 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:05:42 nagios postfix/local[8507]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:05:43 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8507 exit status 1
Mar 18 11:05:43 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:06:43 nagios postfix/local[8508]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:06:44 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8508 exit status 1
Mar 18 11:06:44 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:07:44 nagios postfix/local[8510]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:07:45 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8510 exit status 1
Mar 18 11:07:45 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:08:45 nagios postfix/local[8512]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:08:46 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8512 exit status 1
Mar 18 11:08:46 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:09:46 nagios postfix/local[8520]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:09:47 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8520 exit status 1
Mar 18 11:09:47 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:10:47 nagios postfix/local[8521]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:10:48 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8521 exit status 1
Mar 18 11:10:48 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:11:48 nagios postfix/local[8524]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:11:49 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8524 exit status 1
Mar 18 11:11:49 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:12:49 nagios postfix/local[8525]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:12:50 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8525 exit status 1
Mar 18 11:12:50 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:13:50 nagios postfix/local[8527]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:13:51 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8527 exit status 1
Mar 18 11:13:51 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:14:51 nagios postfix/local[8528]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:14:52 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8528 exit status 1
Mar 18 11:14:52 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:15:52 nagios postfix/local[8529]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:15:53 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8529 exit status 1
Mar 18 11:15:53 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:16:53 nagios postfix/local[8530]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:16:54 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8530 exit status 1
Mar 18 11:16:54 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:17:54 nagios postfix/local[8534]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:17:55 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8534 exit status 1
Mar 18 11:17:55 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:18:55 nagios postfix/local[8535]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:18:56 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8535 exit status 1
Mar 18 11:18:56 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:19:56 nagios postfix/local[8536]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:19:57 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8536 exit status 1
Mar 18 11:19:57 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:20:57 nagios postfix/local[8537]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:20:58 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8537 exit status 1
Mar 18 11:20:58 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:21:58 nagios postfix/local[8538]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:21:59 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8538 exit status 1
Mar 18 11:21:59 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:22:59 nagios postfix/local[8539]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:23:00 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8539 exit status 1
Mar 18 11:23:00 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:24:00 nagios postfix/local[8540]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:24:01 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8540 exit status 1
Mar 18 11:24:01 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:25:01 nagios postfix/local[8541]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:25:02 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8541 exit status 1
Mar 18 11:25:02 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:26:02 nagios postfix/local[8542]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:26:03 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8542 exit status 1
Mar 18 11:26:03 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:27:03 nagios postfix/local[8543]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:27:04 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8543 exit status 1
Mar 18 11:27:04 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:28:04 nagios postfix/local[8544]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:28:05 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8544 exit status 1
Mar 18 11:28:05 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:29:06 nagios postfix/local[8545]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:29:07 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8545 exit status 1
Mar 18 11:29:07 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:30:07 nagios postfix/local[8546]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:30:08 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8546 exit status 1
Mar 18 11:30:08 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:31:08 nagios postfix/local[8547]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:31:09 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8547 exit status 1
Mar 18 11:31:09 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:32:09 nagios postfix/local[8548]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:32:10 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8548 exit status 1
Mar 18 11:32:10 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:33:10 nagios postfix/local[8549]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:33:11 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8549 exit status 1
Mar 18 11:33:11 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:34:11 nagios postfix/local[8550]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:34:12 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8550 exit status 1
Mar 18 11:34:12 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:35:12 nagios postfix/local[8551]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:35:13 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8551 exit status 1
Mar 18 11:35:13 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:36:13 nagios postfix/local[8561]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:36:14 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8561 exit status 1
Mar 18 11:36:14 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:37:14 nagios postfix/local[8715]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:37:15 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8715 exit status 1
Mar 18 11:37:15 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:38:15 nagios postfix/local[8759]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:38:16 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8759 exit status 1
Mar 18 11:38:16 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:39:16 nagios postfix/local[8831]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:39:17 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8831 exit status 1
Mar 18 11:39:17 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:40:17 nagios postfix/local[8834]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:40:18 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8834 exit status 1
Mar 18 11:40:18 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:41:18 nagios postfix/local[8836]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:41:19 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8836 exit status 1
Mar 18 11:41:19 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:42:19 nagios postfix/local[8839]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:42:20 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8839 exit status 1
Mar 18 11:42:20 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:43:20 nagios postfix/local[8842]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:43:21 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8842 exit status 1
Mar 18 11:43:21 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:44:21 nagios postfix/local[8843]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:44:22 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8843 exit status 1
Mar 18 11:44:22 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:45:22 nagios postfix/local[8844]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:45:23 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8844 exit status 1
Mar 18 11:45:23 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:46:23 nagios postfix/local[8845]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:46:24 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8845 exit status 1
Mar 18 11:46:24 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:47:24 nagios postfix/local[8848]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:47:25 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8848 exit status 1
Mar 18 11:47:25 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:48:25 nagios postfix/local[8849]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:48:26 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8849 exit status 1
Mar 18 11:48:26 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:49:26 nagios postfix/local[8850]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:49:27 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8850 exit status 1
Mar 18 11:49:27 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:50:27 nagios postfix/local[8851]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:50:28 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8851 exit status 1
Mar 18 11:50:28 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:51:28 nagios postfix/local[8852]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:51:29 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8852 exit status 1
Mar 18 11:51:29 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Mar 18 11:52:29 nagios postfix/local[8854]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Mar 18 11:52:30 nagios postfix/master[5619]: warning: process /usr/lib/postfix/local pid 8854 exit status 1
Mar 18 11:52:30 nagios postfix/master[5619]: warning: /usr/lib/postfix/local: bad command startup -- throttling

On dirait un souci de taille de la boîte... Mais je ne me souviens pas avoir touché à ce paramètre...

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Mais je ne me souviens pas avoir touché à ce paramètre...

Alors pourquoi y a-t-il cette ligne dans la configuration que tu m'as montrée ?

mailbox_size_limit = 10000

Tu n'aurais pas bêtement suivi un tuto mal fichu ?

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Ca me dit quelque chose... On ne définit pas ce paramètres lors de la configuration de Postfix ?

Je vais refaire un

dpkg-reconfigure postfix

pour modifier ce paramètre... Mais je ne connais pas la valeur par défaut.

Par la suite, je vais refaire un envoi de mail et te montrer les logs...
J'ai bon ?

Merci
Tom

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Supprimer cette ligne dans le fichier, c'est tout...

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Voilà, j'ai supprimé la ligne, redémarré le service Postfix, et voici les logs :

Mar 18 12:46:20 nagios postfix/master[9117]: daemon started -- version 2.9.6, configuration /etc/postfix
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E83BB6A417: from=<nagios@*****.com>, size=669, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: 8F4316A41A: from=<root@*****.com>, size=427, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: A63DF6A418: from=<root@*****.com>, size=427, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: C91286A059: from=<root@*****.com>, size=427, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E46C06A419: from=<nagios@*****.com>, size=642, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/local[9123]: E83BB6A417: to=<sysinfo@*****.com>, relay=local, delay=87997, delays=87997/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: "sysinfo")
Mar 18 12:46:20 nagios postfix/local[9124]: 8F4316A41A: to=<bse@*****.com>, relay=local, delay=87805, delays=87805/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: "bse")
Mar 18 12:46:20 nagios postfix/local[9126]: A63DF6A418: to=<bse@*****.com>, relay=local, delay=87977, delays=87977/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "bse")
Mar 18 12:46:20 nagios postfix/local[9127]: E46C06A419: to=<sysinfo@*****.com>, relay=local, delay=87967, delays=87967/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: "sysinfo")
Mar 18 12:46:20 nagios postfix/local[9123]: C91286A059: to=<bse@*****.com>, relay=local, delay=88347, delays=88347/0.03/0/0.01, dsn=5.1.1, status=bounced (unknown user: "bse")
Mar 18 12:46:20 nagios postfix/cleanup[9131]: E764B6AB8C: message-id=<20140318114620.E764B6AB8C@*****.com>
Mar 18 12:46:20 nagios postfix/cleanup[9133]: E7B786ABA0: message-id=<20140318114620.E7B786ABA0@*****.com>
Mar 18 12:46:20 nagios postfix/bounce[9129]: E83BB6A417: sender non-delivery notification: E764B6AB8C
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E7B786ABA0: from=<>, size=2093, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E83BB6A417: removed
Mar 18 12:46:20 nagios postfix/bounce[9128]: A63DF6A418: sender non-delivery notification: E7B786ABA0
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E764B6AB8C: from=<>, size=2357, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/cleanup[9131]: E8A126ABA2: message-id=<20140318114620.E8A126ABA2@*****.com>
Mar 18 12:46:20 nagios postfix/cleanup[9133]: E8D246A417: message-id=<20140318114620.E8D246A417@*****.com>
Mar 18 12:46:20 nagios postfix/cleanup[9134]: E8B496A424: message-id=<20140318114620.E8B496A424@*****.com>
Mar 18 12:46:20 nagios postfix/qmgr[9121]: A63DF6A418: removed
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E8D246A417: from=<>, size=2330, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E8B496A424: from=<>, size=2093, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E8A126ABA2: from=<>, size=2093, nrcpt=1 (queue active)
Mar 18 12:46:20 nagios postfix/bounce[9130]: 8F4316A41A: sender non-delivery notification: E8A126ABA2
Mar 18 12:46:20 nagios postfix/bounce[9125]: C91286A059: sender non-delivery notification: E8B496A424
Mar 18 12:46:20 nagios postfix/bounce[9132]: E46C06A419: sender non-delivery notification: E8D246A417
Mar 18 12:46:20 nagios postfix/qmgr[9121]: 8F4316A41A: removed
Mar 18 12:46:20 nagios postfix/qmgr[9121]: C91286A059: removed
Mar 18 12:46:20 nagios postfix/qmgr[9121]: E46C06A419: removed
Mar 18 12:46:21 nagios postfix/local[9127]: E8B496A424: to=<root@*****.com>, relay=local, delay=0.07, delays=0.01/0/0/0.06, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
Mar 18 12:46:21 nagios postfix/qmgr[9121]: E8B496A424: removed
Mar 18 12:46:21 nagios postfix/local[9124]: E764B6AB8C: to=<nagios@*****.com>, relay=local, delay=0.07, delays=0.01/0/0/0.06, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
Mar 18 12:46:21 nagios postfix/qmgr[9121]: E764B6AB8C: removed
Mar 18 12:46:21 nagios postfix/local[9127]: E8A126ABA2: to=<root@*****.com>, relay=local, delay=0.08, delays=0.01/0.06/0/0.01, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
Mar 18 12:46:21 nagios postfix/qmgr[9121]: E8A126ABA2: removed
Mar 18 12:46:28 nagios postfix/local[9123]: E8D246A417: to=<nagios@*****.com>, relay=local, delay=8, delays=0.01/0/0/8, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
Mar 18 12:46:28 nagios postfix/qmgr[9121]: E8D246A417: removed
Mar 18 12:46:28 nagios postfix/local[9126]: E7B786ABA0: to=<root@*****.com>, relay=local, delay=8.1, delays=0.01/0/0/8, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
Mar 18 12:46:28 nagios postfix/qmgr[9121]: E7B786ABA0: removed
Mar 18 12:46:37 nagios postfix/pickup[9120]: 69D256A417: uid=0 from=<root>
Mar 18 12:46:37 nagios postfix/cleanup[9135]: 69D256A417: message-id=<20140318114637.69D256A417@*****.com>
Mar 18 12:46:37 nagios postfix/qmgr[9121]: 69D256A417: from=<root@*****.com>, size=427, nrcpt=1 (queue active)
Mar 18 12:46:37 nagios postfix/local[9124]: 69D256A417: to=<bse@*****.com>, relay=local, delay=0.01, delays=0.01/0/0/0, dsn=5.1.1, status=bounced (unknown user: "bse")
Mar 18 12:46:37 nagios postfix/cleanup[9134]: 6BD346A418: message-id=<20140318114637.6BD346A418@*****.com>
Mar 18 12:46:37 nagios postfix/bounce[9128]: 69D256A417: sender non-delivery notification: 6BD346A418
Mar 18 12:46:37 nagios postfix/qmgr[9121]: 6BD346A418: from=<>, size=2093, nrcpt=1 (queue active)
Mar 18 12:46:37 nagios postfix/qmgr[9121]: 69D256A417: removed
Mar 18 12:46:37 nagios postfix/local[9144]: 6BD346A418: to=<root@*****.com>, relay=local, delay=0.01, delays=0/0/0/0.01, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
Mar 18 12:46:37 nagios postfix/qmgr[9121]: 6BD346A418: removed

Merci
Tom.

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

On voit dans tes logs uniquement des e-mails à destination de l'ordinateur local (le domaine « *****.com » étant listé dans la configuration "mydestination"), qui sont parfois acceptés (remis à la commande procmail conformément à ce que tu as configuré dans Postfix) et parfois refusés (utilisateurs inexistants sur ton système).

Si tu veux que les e-mails à destination de « *****.com » partent ailleurs, il ne faut pas dire à Postfix que c'est lui la destination de ces mails, il faut supprimer ce domaine de la ligne "mydestination".

J'insiste à nouveau sur le fait qu'il faut apprendre à utiliser tout ça, administrer un système ça ne s'improvise pas.

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Je commence à y voir clair ! Merci beaucoup de ton aide.

Donc : j'ai reçu un email de "root@*****.com". Est-il possible de modifier le mot "root" quelque part ?
Si déjà les emails fonctionnent sans Nagios, on est sur la bonne voie. J'avais besoin d'un guide

Merci
Tom

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Est-il possible de modifier le mot "root" quelque part ?

C'est les mails que tu as envoyées avec la commande "mail" ? Tu as exécuté cette commande en tant que l'utilisateur root, c'est donc son nom qui apparaît en tant qu'expéditeur

Nagios utilise aussi la commande "mail", du coup il suffit de (re)trouver comment faire pour que ce soit une autre adresse qui soit mise en tant qu'expéditeur. La manipulation ne me revient pas à l'esprit...

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Je vais chercher, c'est parfait.

En plus, oui, je n'ai pas réfléchi je suis en "sudo -s" donc en root ^^.

Maintenant, comment tester une notification avec Nagios ? Il y avait une technique depuis l'interface mais depuis que j'ai mis à jour en version 4, je suis perdu

Merci
Tom

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Je ne sais plus. Ça fait des années que je n'ai plus utilisé Nagios, depuis que je connais un outil plus pro

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Ahah

Bon, les notifications fonctionnent.
Je vais maintenant faire appel à ta mémoire...

J'aimerais que dans Nagios, la fréquence de vérification du ping soit rapide...
Actuellement, j'ai cette ligne :

check_command               check_ping!100.0,20%!500.0,60%

Je n'ai trouvé aucune doc à ce sujet...

Merci !

tiramiseb

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

http://google.fr/?q=nagios+fr%C3%A9quen … rification

---

Sébastien Maccagnoni - https://www.maccagnoni.eu - https://www.domotego.com

TomHawk

Re : [Résolu] Problème de configuration des mails dans Nagios/Postfix

Merci Seb

Je te dis à bientôt... Merci de tes conseils !