Hi Mike,
are you running an snmp daemon?
There pages like these that suggest that:
http://www.visolve.com/squid/whitepapers/monitoringsquid.php
cheers
alessandra
On 09/03/2010 03:30 PM, Mike Kenyon wrote:
> hrrmmm...quite possibly you need this too?:
>
> acl Safe_ports port 1025-65535
>
> I don't see anything else in the config file that may help us here.
>
>
> Cheers
> Mike
>
> On 3 September 2010 15:22, Alessandra Forti<[log in to unmask]> wrote:
>> You need to check that your squid is compiled with with --enable-snmp too.
>>
>> Said that (and I'm using the CERN rpm) my installation still isn't working
>> with similar options as Mike has.
>>
>> cheers
>> alessandra
>>
>> On 09/03/2010 03:00 PM, Mike Kenyon wrote:
>>> Hi Ewan,
>>>
>>> I think the relevant magic is
>>>
>>> acl HOST_MONITOR src 131.225.209.5/32 cmsdbsfrontier.cern.ch 127.0.0.1/32
>>>
>>> followed by
>>>
>>> acl snmppublic snmp_community public
>>> snmp_access allow snmppublic HOST_MONITOR
>>> snmp_access deny all
>>>
>>>
>>> Cheers
>>> Mike.
>>>
>>>
>>>
>>> On 3 September 2010 14:53, Ewan MacMahon<[log in to unmask]>
>>> wrote:
>>>>> -----Original Message-----
>>>>> From: Testbed Support for GridPP member institutes [mailto:TB-
>>>>>
>>>>> thanks, I didn't look at the squid docs. Just thought Dario referred
>>>> to
>>>>> the firewall and squid would handle it internally. It needs to be
>>>>> configured instead.
>>>>>
>>>> I'm guessing that this was part of the pre-canned configuration for
>>>> anyone using the ATLAS tarball squids, but if (like us) you set up
>>>> your own it probably doesn't have snmp enabled since no-one actually
>>>> seems to have asked for that.
>>>>
>>>> If someone could post the relevant bit from the configuration of an
>>>> SNMP enabled squid, that would be handy.
>>>>
>>>> Ewan
>>>>
|