snmp read community

[Toto Capuccino]

Hi Mark,

ok it works, resources.cfg was owned by apache...my mistake.
BTW can you give security advice about ownership and permissions from
/nagios dir to /etc and /cgi dir ?
If yes i thank you very much.

Regards.

2006/1/31, Marc Powell <marc at ena.com>:
>
>
>
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> > admin at lists.sourceforge.net] On Behalf Of Toto Capuccino
> > Sent: Tuesday, January 31, 2006 10:11 AM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] snmp read community
> >
> > Hi all,
> >
> > concerned by security, i tried to insert the snmp community name for
> read
> > access inside resources.cfg (with permissions 600 on it) in macro
> > $USER3$=myUnbre at kablepass
> > It didn't work at all, now all nagios is RED sending alerts. Although,
> It
> > is said in resource.cfg that USER3 is for storing some usernames and
> > passwords (hidden from the CGIs)
> > (hidden from the CGIs) maybe that's where the issue began
> >
>
>
> > But it's a nightmare everything's RED even the check_ping,
> > check_host_alive. Can you help please !!
>
> That should work. What's the status information (error) that you're
> seeing? The $USER3$ line in resource.cfg isn't commented out, is it? Is
> resource.cfg owned by the user nagios runs as? Did you include it as a
> resource_file in nagios.cfg?
>
> --
> Marc
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060131/35b95798/attachment.html>