Re: [squid-users] squid SMP and SNMP

2015-03-19 Thread Eugene M. Zheganin 
Hi.

On 18.03.2015 19:02, Amos Jeffries wrote:
 Process kid3 (SMP coordinator) is attempting to respond.

 Since you configured:
   snmp_port 340${process_number}

 and the coordinator is process number 3 I think it will be using port
 3403 for that response.


Nobody is listening on these ports:

[root@taiga:local/squidquotas]# netstat -an | grep udp | grep
340  
udp46  0  0 *.3401 *.*   
udp46  0  0 *.3402 *.*   
[root@taiga:local/squidquotas]#

Eugene.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

[squid-users] squid SMP and SNMP

2015-03-18 Thread Eugene M. Zheganin 
Hi.

I'm gathering statistics from squid using SNMP. When I use single
process everything is fine, but when it comes to multiple workers - SNMP
doesn't work - I got timeout when trying to read data with snmpwalk.

I'm using the following tweak:

snmp_port 340${process_number}

both workers bind on ports 3401 and 3402 indeed, but then I got this
timeout.
Does anyone have a success story about squid SMP and SNMP ?

I wrote a message about this problem about a year or so, it was 3.3.x,
but situation didn't change.
Should I report this as a bug ?

Thanks.
Eugene.



___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] squid SMP and SNMP

2015-03-18 Thread Amos Jeffries 
On 18/03/2015 9:50 p.m., Eugene M. Zheganin wrote:
 Hi.
 
 I'm gathering statistics from squid using SNMP. When I use single
 process everything is fine, but when it comes to multiple workers - SNMP
 doesn't work - I got timeout when trying to read data with snmpwalk.
 
 I'm using the following tweak:
 
 snmp_port 340${process_number}
 
 both workers bind on ports 3401 and 3402 indeed, but then I got this
 timeout.
 Does anyone have a success story about squid SMP and SNMP ?


SNMP is on the list of SMP-aware features.

The worker receiving the SNMP request will contact other workers to
fetch the data for producing the SNMP response. This may take some time.


 
 I wrote a message about this problem about a year or so, it was 3.3.x,
 but situation didn't change.

Nothing has changed in SNMP or other mgr report generation code since then.

Amos

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] squid SMP and SNMP

2015-03-18 Thread Eugene M. Zheganin 
Hi.

On 18.03.2015 16:04, Amos Jeffries wrote:

 SNMP is on the list of SMP-aware features.

 The worker receiving the SNMP request will contact other workers to
 fetch the data for producing the SNMP response. This may take some time.

Yeah, but it seems like it doesn't happen. Plus, I'm getting the errors
in the cache.log on each attempt:

[root@taiga:etc/squid]# snmpwalk localhost:3402
1.3.6.1.4.1.3495.1.2.1.0 
Timeout: No Response from localhost:3402

and in the log:

2015/03/18 18:48:26 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:46682: (22) Invalid argument
2015/03/18 18:48:49 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:36623: (22) Invalid argument
2015/03/18 18:48:50 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:36623: (22) Invalid argument
2015/03/18 18:48:51 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:36623: (22) Invalid argument
2015/03/18 18:48:52 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:36623: (22) Invalid argument
2015/03/18 18:48:53 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:36623: (22) Invalid argument
2015/03/18 18:48:54 kid3| comm_udp_sendto: FD 34, (family=2)
127.0.0.1:36623: (22) Invalid argument

Thanks.
Eugene.

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] squid SMP and SNMP

2015-03-18 Thread Amos Jeffries 
On 19/03/2015 2:50 a.m., Eugene M. Zheganin wrote:
 Hi.
 
 On 18.03.2015 16:04, Amos Jeffries wrote:

 SNMP is on the list of SMP-aware features.

 The worker receiving the SNMP request will contact other workers to
 fetch the data for producing the SNMP response. This may take some time.

 Yeah, but it seems like it doesn't happen. Plus, I'm getting the errors
 in the cache.log on each attempt:
 
 [root@taiga:etc/squid]# snmpwalk localhost:3402
 1.3.6.1.4.1.3495.1.2.1.0 
 Timeout: No Response from localhost:3402
 
 and in the log:
 
 2015/03/18 18:48:26 kid3| comm_udp_sendto: FD 34, (family=2)
 127.0.0.1:46682: (22) Invalid argument

Process kid3 (SMP coordinator) is attempting to respond.

Since you configured:
  snmp_port 340${process_number}

and the coordinator is process number 3 I think it will be using port
3403 for that response.

Amos

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users