Erro Nagios

Boa tarde Senhores.

estou com um problema. Atualizei meu Nagios para versão 4.0.2 . Porém agora não consigo reiniciar o serviço dele apenas reiniciado o servidor. veja o erro. O que posso fazer para resolver isso ?


root@nagios:~# /etc/init.d/nagios restart
$Stopping nagios: Illegal option -d
/sbin/start-stop-daemon: signal value must be numeric or name of signal (KILL, INT, ...)
Try '/sbin/start-stop-daemon --help' for more information.

$Starting nagios: daemon: debug: config()
daemon: debug: config_load()
daemon: debug: config_load()
daemon: debug: handle_user_option(spec = nagios)

Olá,

Tente utilizar o seguinte comando:

/etc/init.d/nagios configtest

Analise a saída e se necessário, publique aqui no post para eu analisar.

Abss

Bom dia,

Segue a saída

/etc/init.d/nagios configtest
No directory, logging in with HOME=/

Nagios Core 4.0.2
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 11-25-2013
License: GPL

Website: http://www.nagios.org
Reading configuration data...
Warning: use_embedded_perl_implicitly is deprecated and will be removed.
Warning: enable_embedded_perl is deprecated and will be removed.
Warning: p1_file is deprecated and will be removed.
Warning: sleep_time is deprecated and will be removed.
Warning: external_command_buffer_slots is deprecated and will be removed. All commands are always processed upon arrival
Warning: command_check_interval is deprecated and will be removed. Commands are always handled on arrival
Read main config file okay...
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in host type objects (config file '/usr/local/nagios/etc/objects/templates.cfg', starting at line 61)
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in service type objects (config file '/usr/local/nagios/etc/objects/templates.cfg', starting at line 180)
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 18 services.
Checked 38 hosts.
Checked 2 host groups.
Checked 0 service groups.
Checked 4 contacts.
Checked 1 contact groups.
Checked 28 commands.
Checked 7 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 38 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 7 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
Object precache file created:
/usr/local/nagios/var/objects.precache

Este log mostra que as configurações estão ok. Tente reiniciar esta máquina, e verifique se o nagios vai iniciar normalmente e automaticamente.

Então cara, O nagios esta iniciado, o problema é que por exemplo, antes de atualizar para a versão 4.0.2 eu simplesmente podia reiniciar ele atraves do " /etc/init.d/nagios restart " hoje porém se dou esse comando eu tenho a seguinte saída :

root@nagios:/usr/local/nagios/etc/objects# /etc/init.d/nagios restart
$Stopping nagios: Illegal option -d
/sbin/start-stop-daemon: signal value must be numeric or name of signal (KILL, INT, ...)
Try '/sbin/start-stop-daemon --help' for more information.

$Starting nagios: daemon: debug: config()
daemon: debug: config_load()
daemon: debug: config_load()
daemon: debug: handle_user_option(spec = nagios)



Caso eu faça alguma alteração no arquivo do nagios eu tenho que reiniciar o serviço que no momento eu só consigo reiniciar se eu de um reboot no servidor. Creio que essa não seja a melhor maneira.