Squid 3.1 + mrtg

[Babu Chaliyath]

Hi List,
Struggling to get mrtg working with squid. No values shown in the mrtg graph.

My System as follows
OS Freebsd 7.2
Squid 3.1.0.14
Snmpwalk 5.4.2.1
mrtg 2.16.2


Squid snmp acls are working fine as I am getting results with following command
#snmpwalk -m /usr/local/etc/squid/mib.txt -v2c -Cc -c public
localhost:3401 .1.3.6.1.4.1.3495.1.1

But when I run mrtg
I am getting following errors

Unknown SNMP var cacheServerRequests
at /usr/local/bin/mrtg line 2202
Unknown SNMP var cacheServerRequests
at /usr/local/bin/mrtg line 2202
Unknown SNMP var cacheUptime
at /usr/local/bin/mrtg line 2202
Unknown SNMP var cacheSoftware
at /usr/local/bin/mrtg line 2202
Unknown SNMP var cacheVersionId

Btw I am using the mrtg configurator downloaded from Adrian Chadd's
squid blog. Available in <
http://www.xenion.com.au/static/squid-mrtg-1.0.tar.gz >

It would be great if any can help me out with some clues where I am going wrong.
Regards
Babs

[Amos Jeffries-2]

Babu Chaliyath wrote:

> Hi List,
> Struggling to get mrtg working with squid. No values shown in the mrtg graph.
>
> My System as follows
> OS Freebsd 7.2
> Squid 3.1.0.14
> Snmpwalk 5.4.2.1
> mrtg 2.16.2
>
>
> Squid snmp acls are working fine as I am getting results with following command
> #snmpwalk -m /usr/local/etc/squid/mib.txt -v2c -Cc -c public
> localhost:3401 .1.3.6.1.4.1.3495.1.1
>
> But when I run mrtg
> I am getting following errors
>
> Unknown SNMP var cacheServerRequests
> at /usr/local/bin/mrtg line 2202
> Unknown SNMP var cacheServerRequests
> at /usr/local/bin/mrtg line 2202
> Unknown SNMP var cacheUptime
> at /usr/local/bin/mrtg line 2202
> Unknown SNMP var cacheSoftware
> at /usr/local/bin/mrtg line 2202
> Unknown SNMP var cacheVersionId
>
> Btw I am using the mrtg configurator downloaded from Adrian Chadd's
> squid blog. Available in <
> http://www.xenion.com.au/static/squid-mrtg-1.0.tar.gz >
>
> It would be great if any can help me out with some clues where I am going wrong.
> Regards
> Babs

Make sure that the mib.txt you/mrtg are using came from the 3.1 source
code. There have been major changes to the MIB numbering in 3.1.

Amos
--
Please be using
   Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
   Current Beta Squid 3.1.0.14

[Henrik Nordstrom-5]

mån 2009-11-02 klockan 23:47 +1300 skrev Amos Jeffries:

> Make sure that the mib.txt you/mrtg are using came from the 3.1 source
> code. There have been major changes to the MIB numbering in 3.1.

Hmm.. what kind of changes?

MIB numbering should never change. Old numbers may cease to exists when
their data sources go away and new number appear as new info gets
published, but existing numbering should not change...

Regards
Henrik

[Babu Chaliyath]

> Make sure that the mib.txt you/mrtg are using came from the 3.1 source code.
> There have been major changes to the MIB numbering in 3.1.
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
>  Current Beta Squid 3.1.0.14
>

Hi, thanx for the reply

Yes I am using the mib.txt file which came with squid 3.1 only. I have
installed it from the ports.

Regards
Babs

[Amos Jeffries-2]

Henrik Nordstrom wrote:

> mån 2009-11-02 klockan 23:47 +1300 skrev Amos Jeffries:
>
>> Make sure that the mib.txt you/mrtg are using came from the 3.1 source
>> code. There have been major changes to the MIB numbering in 3.1.
>
> Hmm.. what kind of changes?
>
> MIB numbering should never change. Old numbers may cease to exists when
> their data sources go away and new number appear as new info gets
> published, but existing numbering should not change...

Converting IPv4 address fields to IPv6+IPv4 shared trees...

The client info table had cacheClientAddressType added as .1,
cacheClientAddress shuffled to .2
  ... which bumped all cacheClient* from .N to .N+1

The peering table had cachePeerIndex added as .1 and
cacheClientAddressType added as .2
   ... which bumped all cachePeer* from .N to .N+2

Amos
--
Please be using
   Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
   Current Beta Squid 3.1.0.14

[Babu Chaliyath]

>
> Converting IPv4 address fields to IPv6+IPv4 shared trees...
>
> The client info table had cacheClientAddressType added as .1,
> cacheClientAddress shuffled to .2
>  ... which bumped all cacheClient* from .N to .N+1
>
> The peering table had cachePeerIndex added as .1 and cacheClientAddressType
> added as .2
>  ... which bumped all cachePeer* from .N to .N+2
>
> Amos

Now thats all going above my head as far as mrtg setup for the squid
3.1 is concerned. Can U guys tell me where and what changes I need to
make it working?
Sorry for this but I couldnt get much idea from these.

Regards
Babs

[Henrik Nordstrom-5]

tis 2009-11-03 klockan 17:25 +1300 skrev Amos Jeffries:

> > MIB numbering should never change. Old numbers may cease to exists when
> > their data sources go away and new number appear as new info gets
> > published, but existing numbering should not change...
>
> Converting IPv4 address fields to IPv6+IPv4 shared trees...
>
> The client info table had cacheClientAddressType added as .1,
> cacheClientAddress shuffled to .2
>   ... which bumped all cacheClient* from .N to .N+1
>
> The peering table had cachePeerIndex added as .1 and
> cacheClientAddressType added as .2
>    ... which bumped all cachePeer* from .N to .N+2

Ugh.. that needs to be redone. The new field needs to be added after the
other ones.

It is not permissible to renumber existing MIB entries like this, or to
reuse a old MIB entry for other purpose.

I'll file a bug on that so it's not forgotten.

Regards
Henrik

[Amos Jeffries-2]

Babu Chaliyath wrote:

>> Converting IPv4 address fields to IPv6+IPv4 shared trees...
>>
>> The client info table had cacheClientAddressType added as .1,
>> cacheClientAddress shuffled to .2
>>  ... which bumped all cacheClient* from .N to .N+1
>>
>> The peering table had cachePeerIndex added as .1 and cacheClientAddressType
>> added as .2
>>  ... which bumped all cachePeer* from .N to .N+2
>>
>> Amos
>
> Now thats all going above my head as far as mrtg setup for the squid
> 3.1 is concerned. Can U guys tell me where and what changes I need to
> make it working?
> Sorry for this but I couldnt get much idea from these.
>
> Regards
> Babs

Um, I think the best way to go forward is for us to fix this ASAP.
Are you able to test patches if I do the code?

Amos
--
Please be using
   Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
   Current Beta Squid 3.1.0.14

[Babu Chaliyath]

Hey Thanx Henrik,

And Amos,
Yes Definitely I can test them for sure.
I here to do any help I can offer

Regards
Babs

On Mon, Nov 9, 2009 at 11:13 AM, Amos Jeffries <squid3@...> wrote:

> Babu Chaliyath wrote:
>>>
>>> Converting IPv4 address fields to IPv6+IPv4 shared trees...
>>>
>>> The client info table had cacheClientAddressType added as .1,
>>> cacheClientAddress shuffled to .2
>>>  ... which bumped all cacheClient* from .N to .N+1
>>>
>>> The peering table had cachePeerIndex added as .1 and
>>> cacheClientAddressType
>>> added as .2
>>>  ... which bumped all cachePeer* from .N to .N+2
>>>
>>> Amos
>>
>> Now thats all going above my head as far as mrtg setup for the squid
>> 3.1 is concerned. Can U guys tell me where and what changes I need to
>> make it working?
>> Sorry for this but I couldnt get much idea from these.
>>
>> Regards
>> Babs
>
> Um, I think the best way to go forward is for us to fix this ASAP.
> Are you able to test patches if I do the code?
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
>  Current Beta Squid 3.1.0.14
>