Please Help!! another error on starting nagios

[Israel Brewster]

I have noticed that double slash in a number of places throughout the  
nagios config files. In my experience, it has never caused any  
issues, either with the functioning of nagios, or with other things  
such as when I accidentally type it on the command line when trying  
to enter a command path. /bin//echo "test" works just as well as /bin/ 
echo "test"
-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service
5245 Airport Industrial Rd
Fairbanks, AK 99709
-----------------------------------------------


On Aug 2, 2006, at 5:00 AM, Simon J. Hernandez wrote:

> On Wed, 2 Aug 2006, Morris, Patrick wrote:
>
>>> -----Original Message-----
>>> From: nagios-users-bounces at lists.sourceforge.net
>>> [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf
>>> Of Arief Iqbal
>>> Sent: Wednesday, August 02, 2006 2:06 AM
>>> To: nagios milis
>>> Subject: [Nagios-users] Please Help!! another error on starting  
>>> nagios
>>>
>>> my problem when verify is clear, now the problem is there are
>>> several warning when i try to starting nagios, and it won't
>>> stop, the warning is:
>>>
>>> Nagios 2.5 starting... (PID=29468)
>>> sh: /usr/local/nagios//libexec/check_load: No such file or directory
>
> ...
>
>>> sh: /usr/local/nagios//libexec/check_ping: No such file or directory
>>> Warning: Attempting to execute the command
>>> "/usr/local/nagios//libexec/check_ping -H 192.168.87.100 -w
>>> 3000.0,80% -c 5000.0,100% -p 1" resulted in a return code of
>>> 127.  Make sure the script or binary you are trying to
>>> execute actually exists...
>>>
>>> Can somebody tell me why??? if you don't mind, you can give
>>> me the detail, 'cause i'm really newbie for using nagios
>>
>> Do those files exist?
>>
>> Did you install the plugins?
>
>
> Is there a good reasaon to have the "//" before libexec?
>
> I haven't been through this is a while, but normally "//" will keep an
> executable from executing.
>
> I am naturally wondering how those got in the command in the first  
> place,
> but if you can execute the command without the aditional "/" you  
> may be
> able to fix this easily, editing the appropriate .cfg file.
>
> Just my USD $0.02.
>
>
> Simon
>
> -- 
> Simon J. Hernandez    |    http://people.w3.org/simon/
>
> ---------------------------------------------------------------------- 
> ---
> 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 at 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


-------------------------------------------------------------------------
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 at 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