Hi Danny,
in my further debugging, I recognized that something different is missing.
The whole stoy:
I wrote an event-handler which uses Expect to ssh to the faulty device. ssh is not executed if I define the perl file as event-handler, but the event-hander itself is executed.
If I write a bash script as event-handler, which embeddeds the perl event-handler everything works fine:
in my further debugging, I recognized that something different is missing.
The whole stoy:
I wrote an event-handler which uses Expect to ssh to the faulty device. ssh is not executed if I define the perl file as event-handler, but the event-hander itself is executed.
If I write a bash script as event-handler, which embeddeds the perl event-handler everything works fine:
#!/bin/bash
/usr/local/nagios/libexec/eventhandlers/stop_pbr_webcomm.pl $1 $2 $3
In this case I removed the HOME assignment in the startup script and reloaded nagios. Any Ideas?
Thorsten
-----Thorsten Kocher/Spirit21 schrieb: -----
/usr/local/nagios/libexec/eventhandlers/stop_pbr_webcomm.pl $1 $2 $3
In this case I removed the HOME assignment in the startup script and reloaded nagios. Any Ideas?
Thorsten
-----Thorsten Kocher/Spirit21 schrieb: -----
An: Daniel Meyer <[EMAIL PROTECTED]>
Von: Thorsten Kocher/Spirit21
Datum: 26.01.2007 08:56AM
Kopie: Thorsten Kocher/[EMAIL PROTECTED], nagios-users@lists.sourceforge.net
Thema: Antwort: Re: [Nagios-users] Antwort: Re: $HOME is not set in init scriptDanny,
you have the same start section as it is on my system.
If you look a little bit further in the file you find this section
prefix=/usr
exec_prefix=/usr
NagiosBin=/usr/bin/nagios
NagiosCfgFile=/etc/nagios/nagios.cfg
NagiosStatusFile=/var/log/nagios/status.dat
NagiosTempFile=/var/log/nagios/nagios.tmp
NagiosRetentionFile=/var/log/nagios/retention.dat
NagiosCommandFile=/var/log/nagios/rw/nagios.cmd
NagiosVarDir=/var/log/nagios
NagiosRunFile=/var/run/nagios.pid
NagiosLockDir=/var/lock/subsys
NagiosLockFile=nagios
NagiosCGIDir=/usr/lib/nagios/cgi
NagiosUser=nagios
NagiosGroup=nagios
# added by thorsten
HOME=/var/log/nagios
This solves the problem of the /home problem, so I before other people are running in the same problem it is better to add it in the distritbution.
I am using Nagios 2.5 rpm for RH ES 3, updated to 2.7 with an rpm build by my own.
ThorstenAn: [EMAIL PROTECTED]
Von: Daniel Meyer <[EMAIL PROTECTED]>
Datum: 26.01.2007 08:45AM
Kopie: nagios-users@lists.sourceforge.net
Thema: Re: [Nagios-users] Antwort: Re: $HOME is not set in init script
On Thu, 25 Jan 2007, [EMAIL PROTECTED] wrote:
> Daniel,
>
> nagios is started in /etc/init.d/nagios with "su - nagios -c nagios", so the process
> inherits the environment varialbes of the root user, which executes the su command.
> ($HOME is /root)
Which distribution are you using? My init-script (based on the one from
Dag Wieers Nagios-RPM) starts nagios this way:
case "$1" in
start)
echo "Starting network monitor: nagios"
$NagiosBin -v $NagiosCfgFile > /dev/null 2>&1;
if [ $? -eq 0 ]; then
su - $NagiosUser -c "/usr/bin/ndo2db -c
/etc/nagios/ndo2db.cfg"
su - $NagiosUser -c "touch
$NagiosVarDir/nagios.log $NagiosRetentionFile"
rm -f $NagiosCommandFile
touch $NagiosRunFile
chown $NagiosUser:$NagiosGroup $NagiosRunFile
$NagiosBin -d $NagiosCfgFile
Danny
--
Q: Gentoo is too hard to install = http://www.cyberdelia.de
and I feel like whining. = [EMAIL PROTECTED]
A: Please see /dev/null. =
(from the gentoo installer FAQ) = \o/
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null