Re: [squid-users] SSL SESSION PARAMS poluting the cache log

2011-10-24 Thread Henrik Nordström
As said earlier this is printed only if you have set debug section 83 to
level 4 or higher.

grep debug_options /path/to/squid.conf


sön 2011-10-23 klockan 21:25 -0700 skrev Yucong Sun (叶雨飞):
 Hi, After a few version this still hasn't gone, my debug_options are
 default, which should be all,1 per manual. I'm compiling from the
 source on a ubuntu 10.04LTS
 
 
 Anyone else seeing this problem? 
 
 2011/8/29 Henrik Nordström hen...@henriknordstrom.net
 sön 2011-08-28 klockan 04:07 -0700 skrev Yucong Sun (叶雨飞):
  Hi,  after turning on https_port , I start to have these
 logs in
  cache.log , which is meaningless to have on a production
 server,
  anyway to turn it off?
 
  -BEGIN SSL SESSION PARAMETERS-
 
 
 What are your debug_options set to? This is only printed if
 you have
 enabled debug section 83 at level 4 or above.
 
 Regards
 Henrik
 
 
 




Re: [squid-users] SSL SESSION PARAMS poluting the cache log

2011-10-24 Thread 叶雨飞
As I said, there's no such setting in my config, I don't even have a
debug_options in the config.

2011/10/23 Henrik Nordström hen...@henriknordstrom.net:
 As said earlier this is printed only if you have set debug section 83 to
 level 4 or higher.

 grep debug_options /path/to/squid.conf


 sön 2011-10-23 klockan 21:25 -0700 skrev Yucong Sun (叶雨飞):
 Hi, After a few version this still hasn't gone, my debug_options are
 default, which should be all,1 per manual. I'm compiling from the
 source on a ubuntu 10.04LTS


 Anyone else seeing this problem?

 2011/8/29 Henrik Nordström hen...@henriknordstrom.net
         sön 2011-08-28 klockan 04:07 -0700 skrev Yucong Sun (叶雨飞):
          Hi,  after turning on https_port , I start to have these
         logs in
          cache.log , which is meaningless to have on a production
         server,
          anyway to turn it off?
         
          -BEGIN SSL SESSION PARAMETERS-


         What are your debug_options set to? This is only printed if
         you have
         enabled debug section 83 at level 4 or above.

         Regards
         Henrik








Re: [squid-users] 3.2.0.13: commBind: Cannot bind socket FD 18 to [::]: (13) Permission denied

2011-10-24 Thread Jean-Philippe Menil

Hi,

on wich os?

On debian, i have to create /var/run/squid and check the permission, to 
get it working.


Regards.

--
Jean-Philippe Menil - Pôle réseau Service IRTS
DSI Université de Nantes
jean-philippe.me...@univ-nantes.fr
Tel : 02.53.48.49.27 - Fax : 02.53.48.49.09



Re: [squid-users] SSL SESSION PARAMS poluting the cache log

2011-10-24 Thread Henrik Nordström
Which Squid versions have you tried, and is these standard Squid
versions or with any kind of patches applied?

sön 2011-10-23 klockan 23:28 -0700 skrev Yucong Sun (叶雨飞):
 As I said, there's no such setting in my config, I don't even have a
 debug_options in the config.
 
 2011/10/23 Henrik Nordström hen...@henriknordstrom.net:
  As said earlier this is printed only if you have set debug section 83 to
  level 4 or higher.
 
  grep debug_options /path/to/squid.conf
 
 
  sön 2011-10-23 klockan 21:25 -0700 skrev Yucong Sun (叶雨飞):
  Hi, After a few version this still hasn't gone, my debug_options are
  default, which should be all,1 per manual. I'm compiling from the
  source on a ubuntu 10.04LTS
 
 
  Anyone else seeing this problem?
 
  2011/8/29 Henrik Nordström hen...@henriknordstrom.net
  sön 2011-08-28 klockan 04:07 -0700 skrev Yucong Sun (叶雨飞):
   Hi,  after turning on https_port , I start to have these
  logs in
   cache.log , which is meaningless to have on a production
  server,
   anyway to turn it off?
  
   -BEGIN SSL SESSION PARAMETERS-
 
 
  What are your debug_options set to? This is only printed if
  you have
  enabled debug section 83 at level 4 or above.
 
  Regards
  Henrik
 
 
 
 
 
 




Re: [squid-users] SSL SESSION PARAMS poluting the cache log

2011-10-24 Thread 叶雨飞
# ./squid -v
Squid Cache: Version 3.1.15
configure options:  '--disable-maintainer-mode'
'--disable-dependency-tracking' '--disable-silent-rules'
'--enable-inline' '--enable-async-io=8'
'--enable-storeio=ufs,aufs,diskd' '--enable-removal-policies=lru,heap'
'--enable-cache-digests' '--enable-underscores'
'--enable-follow-x-forwarded-for' '--disable-translation'
'--with-filedescriptors=65536' '--with-default-user=proxy'
'--enable-ssl' '--enable-ltdl-convenience'
--with-squid=/tmp/squid-3.1.15/squid-3.1.15


2011/10/23 Henrik Nordström hen...@henriknordstrom.net:
 Which Squid versions have you tried, and is these standard Squid
 versions or with any kind of patches applied?

 sön 2011-10-23 klockan 23:28 -0700 skrev Yucong Sun (叶雨飞):
 As I said, there's no such setting in my config, I don't even have a
 debug_options in the config.

 2011/10/23 Henrik Nordström hen...@henriknordstrom.net:
  As said earlier this is printed only if you have set debug section 83 to
  level 4 or higher.
 
  grep debug_options /path/to/squid.conf
 
 
  sön 2011-10-23 klockan 21:25 -0700 skrev Yucong Sun (叶雨飞):
  Hi, After a few version this still hasn't gone, my debug_options are
  default, which should be all,1 per manual. I'm compiling from the
  source on a ubuntu 10.04LTS
 
 
  Anyone else seeing this problem?
 
  2011/8/29 Henrik Nordström hen...@henriknordstrom.net
          sön 2011-08-28 klockan 04:07 -0700 skrev Yucong Sun (叶雨飞):
           Hi,  after turning on https_port , I start to have these
          logs in
           cache.log , which is meaningless to have on a production
          server,
           anyway to turn it off?
          
           -BEGIN SSL SESSION PARAMETERS-
 
 
          What are your debug_options set to? This is only printed if
          you have
          enabled debug section 83 at level 4 or above.
 
          Regards
          Henrik
 
 
 
 
 
 





Re: [squid-users] 3.2.0.13: commBind: Cannot bind socket FD 18 to [::]: (13) Permission denied

2011-10-24 Thread David Touzeau
Le lundi 24 octobre 2011 à 08:46 +0200, Jean-Philippe Menil a écrit :
 Hi,
 
 on wich os?
 
 On debian, i have to create /var/run/squid and check the permission, to 
 get it working.
 
 Regards.
 


Debian 6 

Your tips seems to fix the issue...

THanks



Re: [squid-users] failed http redirection

2011-10-24 Thread Matus UHLAR - fantomas

On 23.10.11 07:41, Ivan Matala wrote:

iptables -t nat -A PREROUTING -i tun0 -p tcp -m tcp --match multiport
--dports 80 -j DNAT --to-destination 118.67.78.136:80

what im trying to do is, im trying to redirect all http requests to a
foreign proxy, but it fails


foreign? are you sure that the foreign proxy is willing to behave as 
intercepting proxy?

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
   One OS to rule them all, One OS to find them, 
One OS to bring them all and into darkness bind them 


[squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread David Touzeau
Dear

I encounter many times this issue.

Cannot bind socket FD 21 to [::]:x: (98) Address already in use

Perhaps it is a misunderstand of the SMP working process.
I have 2 processors.
Is each worker try to bind the same Port/IP ?




Oct 24 09:35:31 prxysquid-squid squid[3586]: Starting Squid Cache
version 3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...
Oct 24 09:35:31 prxysquid squid[3586]: Process ID 3586
Oct 24 09:35:31 prxysquid squid[3586]: Process Roles: worker
Oct 24 09:35:31 prxysquid squid[3586]: With 1024 file descriptors
available
Oct 24 09:35:31 prxysquid squid[3586]: Initializing IP Cache...
Oct 24 09:35:31 prxysquid squid[3586]: DNS Socket created at [::], FD 8
Oct 24 09:35:31 prxysquid squid[3586]: DNS Socket created at 0.0.0.0, FD
9
Oct 24 09:35:31 prxysquid squid[3586]: Adding nameserver 192.168.1.1
from squid.conf
Oct 24 09:35:31 prxysquid squid[3586]: Logfile: opening log
daemon:/var/log/squid/access.log
Oct 24 09:35:31 prxysquid squid[3586]: Logfile Daemon: opening
log /var/log/squid/access.log
Oct 24 09:35:31 prxysquid squid[3586]: Logfile: opening log
daemon:/var/log/squid/sarg.log
Oct 24 09:35:31 prxysquid squid[3586]: Logfile Daemon: opening
log /var/log/squid/sarg.log
Oct 24 09:35:32 prxysquid squid[3586]: Unlinkd pipe opened on FD 17
Oct 24 09:35:32 prxysquid squid[3586]: Local cache digest enabled;
rebuild/rewrite every 3600/3600 sec
Oct 24 09:35:32 prxysquid squid[3586]: Logfile: opening log
stdio:/var/log/squid/store.log
Oct 24 09:35:32 prxysquid squid[3586]: Swap maxSize 2048000 + 8192 KB,
estimated 158168 objects
Oct 24 09:35:32 prxysquid squid[3586]: Target number of buckets: 7908
Oct 24 09:35:32 prxysquid squid[3586]: Using 8192 Store buckets
Oct 24 09:35:32 prxysquid squid[3586]: Max Mem  size: 8192 KB
Oct 24 09:35:32 prxysquid squid[3586]: Max Swap size: 2048000 KB
Oct 24 09:35:32 prxysquid squid[3586]: Version 1 of swap file with LFS
support detected... 
Oct 24 09:35:32 prxysquid squid[3586]: Rebuilding storage
in /var/cache/squid (DIRTY)
Oct 24 09:35:32 prxysquid squid[3586]: Using Least Load store dir
selection
Oct 24 09:35:32 prxysquid squid[3586]: Set Current Directory
to /var/squid/cache
Oct 24 09:35:32 prxysquid squid[3586]: Loaded Icons.
Oct 24 09:35:32 prxysquid squid[3586]: commBind: Cannot bind socket FD
21 to [::]:22381: (98) Address already in use
Oct 24 09:35:32 prxysquid squid[3586]: HTCP Disabled.
Oct 24 09:35:32 prxysquid squid[3586]: Squid plugin modules loaded: 0
Oct 24 09:35:32 prxysquid squid[3586]: Adaptation support is on
Oct 24 09:35:32 prxysquid squid[3586]: Ready to serve requests.
Oct 24 09:35:32 prxysquid squid[3586]: Stop receiving ICP on [::]:3130
Oct 24 09:35:32 prxysquid squid[3586]: assertion failed: icp_v2.cc:778:
Comm::IsConnOpen(icpOutgoingConn)
Oct 24 09:35:32 prxysquid squid[3480]: Squid Parent: (squid-1) process
3586 exited due to signal 11 with status 0
Oct 24 09:35:32 prxysquid squid[3480]: Squid Parent: (squid-1) process
3586 will not be restarted due to repeated, frequent failures
Oct 24 09:35:32 prxysquid squid[3480]: Exiting due to repeated, frequent
failures
Oct 24 09:35:32 prxysquid kernel: [145331.125748] squid[3586]: segfault
at 40 ip 081b842c sp bfbab6b0 error 4 in squid[8048000+3d8000]





Re: [squid-users] 3.2.0.13: FATAL: dying from an unhandled exception: theGroupBSize 0

2011-10-24 Thread David Touzeau
Le lundi 24 octobre 2011 à 11:49 +1300, Amos Jeffries a écrit :
 On 23/10/11 23:49, David Touzeau wrote:
  Dear
 
  I'm using the 3.2.0.13-20111022-r11381
 
  When set
 
  worker 2
 
  In squid.conf
 
  Has i have 2 CPUs
 
  Squid did not want to start with the following error
 
  terminate called after throwing an instance of 'TextException'
  what():  theGroupBSize  0
  Aborted
 
 http://bugs.squid-cache.org/show_bug.cgi?id=3383
 
 
  When you have a dedicated server for squid with multiple CPU, is it
  mandatory to set worker has the total CPUs installed on the computer ?
 
 
 No. It is completely optional.
 
 You may have more, or less. More is probably not very useful though, as 
 each worker still has the old Squid behaviour of scaling itself up to 
 consume the max cycles of a single CPU to meet traffic load.
 
 workers and SMP support in Squid-3.2 is just a way to simplify the 
 multi-instance configuration and management.
 
 Amos


You means a way to simplify the multi-instance configuration 
So each Squid instance must run on a dedicated IP+port ?



Re: [squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread Fred B
Hi David,

Please remove icp_port 

 Oct 24 09:35:32 prxysquid squid[3586]: assertion failed:
 icp_v2.cc:778:
 Comm::IsConnOpen(icpOutgoingConn)  - maybe ICP Bug with workers ?


- David Touzeau da...@touzeau.eu a écrit :

 Dear
 
 I encounter many times this issue.
 
 Cannot bind socket FD 21 to [::]:x: (98) Address already in use
 
 Perhaps it is a misunderstand of the SMP working process.
 I have 2 processors.
 Is each worker try to bind the same Port/IP ?
 
 
 
 
 Oct 24 09:35:31 prxysquid-squid squid[3586]: Starting Squid Cache
 version 3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...
 Oct 24 09:35:31 prxysquid squid[3586]: Process ID 3586
 Oct 24 09:35:31 prxysquid squid[3586]: Process Roles: worker
 Oct 24 09:35:31 prxysquid squid[3586]: With 1024 file descriptors
 available
 Oct 24 09:35:31 prxysquid squid[3586]: Initializing IP Cache...
 Oct 24 09:35:31 prxysquid squid[3586]: DNS Socket created at [::], FD
 8
 Oct 24 09:35:31 prxysquid squid[3586]: DNS Socket created at 0.0.0.0,
 FD
 9
 Oct 24 09:35:31 prxysquid squid[3586]: Adding nameserver 192.168.1.1
 from squid.conf
 Oct 24 09:35:31 prxysquid squid[3586]: Logfile: opening log
 daemon:/var/log/squid/access.log
 Oct 24 09:35:31 prxysquid squid[3586]: Logfile Daemon: opening
 log /var/log/squid/access.log
 Oct 24 09:35:31 prxysquid squid[3586]: Logfile: opening log
 daemon:/var/log/squid/sarg.log
 Oct 24 09:35:31 prxysquid squid[3586]: Logfile Daemon: opening
 log /var/log/squid/sarg.log
 Oct 24 09:35:32 prxysquid squid[3586]: Unlinkd pipe opened on FD 17
 Oct 24 09:35:32 prxysquid squid[3586]: Local cache digest enabled;
 rebuild/rewrite every 3600/3600 sec
 Oct 24 09:35:32 prxysquid squid[3586]: Logfile: opening log
 stdio:/var/log/squid/store.log
 Oct 24 09:35:32 prxysquid squid[3586]: Swap maxSize 2048000 + 8192
 KB,
 estimated 158168 objects
 Oct 24 09:35:32 prxysquid squid[3586]: Target number of buckets: 7908
 Oct 24 09:35:32 prxysquid squid[3586]: Using 8192 Store buckets
 Oct 24 09:35:32 prxysquid squid[3586]: Max Mem  size: 8192 KB
 Oct 24 09:35:32 prxysquid squid[3586]: Max Swap size: 2048000 KB
 Oct 24 09:35:32 prxysquid squid[3586]: Version 1 of swap file with
 LFS
 support detected... 
 Oct 24 09:35:32 prxysquid squid[3586]: Rebuilding storage
 in /var/cache/squid (DIRTY)
 Oct 24 09:35:32 prxysquid squid[3586]: Using Least Load store dir
 selection
 Oct 24 09:35:32 prxysquid squid[3586]: Set Current Directory
 to /var/squid/cache
 Oct 24 09:35:32 prxysquid squid[3586]: Loaded Icons.
 Oct 24 09:35:32 prxysquid squid[3586]: commBind: Cannot bind socket
 FD
 21 to [::]:22381: (98) Address already in use
 Oct 24 09:35:32 prxysquid squid[3586]: HTCP Disabled.
 Oct 24 09:35:32 prxysquid squid[3586]: Squid plugin modules loaded: 0
 Oct 24 09:35:32 prxysquid squid[3586]: Adaptation support is on
 Oct 24 09:35:32 prxysquid squid[3586]: Ready to serve requests.
 Oct 24 09:35:32 prxysquid squid[3586]: Stop receiving ICP on
 [::]:3130
 Oct 24 09:35:32 prxysquid squid[3586]: assertion failed:
 icp_v2.cc:778:
 Comm::IsConnOpen(icpOutgoingConn)
 Oct 24 09:35:32 prxysquid squid[3480]: Squid Parent: (squid-1)
 process
 3586 exited due to signal 11 with status 0
 Oct 24 09:35:32 prxysquid squid[3480]: Squid Parent: (squid-1)
 process
 3586 will not be restarted due to repeated, frequent failures
 Oct 24 09:35:32 prxysquid squid[3480]: Exiting due to repeated,
 frequent
 failures
 Oct 24 09:35:32 prxysquid kernel: [145331.125748] squid[3586]:
 segfault
 at 40 ip 081b842c sp bfbab6b0 error 4 in squid[8048000+3d8000]


[squid-users] store_swap_size became negative....

2011-10-24 Thread jiluspo
We are caching large files only when it reach to around between 2TB and
2.5TB(cant be sure bec. Its from graph) store_swap_size became negative.
I thought swap file is corrupt so its been deleted and rebuild. But still
the same.

squid-2.HEAD-20110824
Uname -a
Linux localhost 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010
x86_64 GNU/Linux (Ubuntu server)




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



Re: [squid-users] 3.2.0.13: FATAL: dying from an unhandled exception: theGroupBSize 0

2011-10-24 Thread Amos Jeffries

On 24/10/11 20:49, David Touzeau wrote:

Le lundi 24 octobre 2011 à 11:49 +1300, Amos Jeffries a écrit :

On 23/10/11 23:49, David Touzeau wrote:

Dear

I'm using the 3.2.0.13-20111022-r11381

When set

worker 2

In squid.conf

Has i have 2 CPUs

Squid did not want to start with the following error

terminate called after throwing an instance of 'TextException'
what():  theGroupBSize   0
Aborted


http://bugs.squid-cache.org/show_bug.cgi?id=3383



When you have a dedicated server for squid with multiple CPU, is it
mandatory to set worker has the total CPUs installed on the computer ?



No. It is completely optional.

You may have more, or less. More is probably not very useful though, as
each worker still has the old Squid behaviour of scaling itself up to
consume the max cycles of a single CPU to meet traffic load.

workers and SMP support in Squid-3.2 is just a way to simplify the
multi-instance configuration and management.

Amos



You means a way to simplify the multi-instance configuration
So each Squid instance must run on a dedicated IP+port ?



Nope. Multiple instances with: shared config, shared listening ports, 
shared memory cache, aggregated manager reports, aggregated SNMP responses.


Unless you configure otherwise using the ${process_number} macros.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.16
  Beta testers wanted for 3.2.0.13


Re: [squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread Amos Jeffries

On 24/10/11 20:41, David Touzeau wrote:

Dear

I encounter many times this issue.

Cannot bind socket FD 21 to [::]:x: (98) Address already in use

Perhaps it is a misunderstand of the SMP working process.
I have 2 processors.
Is each worker try to bind the same Port/IP ?



Nope. They have a coordinator instance which does that and passes the 
socket FD to the workers.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.16
  Beta testers wanted for 3.2.0.13


Re: [squid-users] store_swap_size became negative....

2011-10-24 Thread Amos Jeffries

On 24/10/11 22:08, jiluspo wrote:

We are caching large files only when it reach to around between 2TB and
2.5TB(cant be sure bec. Its from graph) store_swap_size became negative.
I thought swap file is corrupt so its been deleted and rebuild. But still
the same.

squid-2.HEAD-20110824
Uname -a
Linux localhost 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010
x86_64 GNU/Linux (Ubuntu server)



Long ago, but still long after we stopped working on squid-2. Squid 
cache calculations had issues with 32-bit boundary. Firstly at the usual 
2GB file size boundary. Also at the next one up, at 2TB, which gets hit 
when doing disk size accounting as multiples of 1KB blocks.


We fixed that midway through the 3.1 release series. The only way to 
avoid it in older Squid is to not cache anything at or above 2GB big, 
*and* to limit the individual cache_dir size to under 2TB per dir.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.16
  Beta testers wanted for 3.2.0.13


Re: [squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread David Touzeau
Le lundi 24 octobre 2011 à 10:40 +0200, Fred B a écrit :
De: 
 Fred B fredbm...@free.fr
 À: 
 squid-users@squid-cache.org
 Sujet: 
 Re: [squid-users] 3.2.0.13: Cannot
 bind socket FD 21 to [::]:22381:
 (98) Address already in use
  Date: 
 Mon, 24 Oct 2011 10:40:49 +0200
 (CEST)
 
 
 Hi David,
 
 Please remove icp_port 
 
  Oct 24 09:35:32 prxysquid squid[3586]: assertion failed:
  icp_v2.cc:778:
  Comm::IsConnOpen(icpOutgoingConn)  - maybe ICP Bug with workers ?
 
 
 - David Touzeau da...@touzeau.eu a écrit :
 
  Dear
  
  I encounter many times this issue.
  
  Cannot bind socket FD 21 to [::]:x: (98) Address already in
 use
  
  Perhaps it is a misunderstand of the SMP working process.
  I have 2 processors.
  Is each worker try to bind the same Port/IP ?
  
  
  
  
  Oct 24 09:35:31 prxysquid-squid squid[3586]: Starting Squid Cache
  version 3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...
  Oct 24 09:35:31 prxysquid squid[3586]: Process ID 3586
  Oct 24 09:35:31 prxysquid squid[3586]: Process Roles: worker
  Oct 24 09:35:31 prxysquid squid[3586]: With 1024 file descriptors
  available
  Oct 24 09:35:31 prxysquid squid[3586]: Initializing IP Cache...
  Oct 24 09:35:31 prxysquid squid[3586]: DNS Socket created at [::],
 FD
  8
  Oct 24 09:35:31 prxysquid squid[3586]: DNS Socket created at
 0.0.0.0,
  FD
  9
  Oct 24 09:35:31 prxysquid squid[3586]: Adding nameserver 192.168.1.1
  from squid.conf
  Oct 24 09:35:31 prxysquid squid[3586]: Logfile: opening log
  daemon:/var/log/squid/access.log
  Oct 24 09:35:31 prxysquid squid[3586]: Logfile Daemon: opening
  log /var/log/squid/access.log
  Oct 24 09:35:31 prxysquid squid[3586]: Logfile: opening log
  daemon:/var/log/squid/sarg.log
  Oct 24 09:35:31 prxysquid squid[3586]: Logfile Daemon: opening
  log /var/log/squid/sarg.log
  Oct 24 09:35:32 prxysquid squid[3586]: Unlinkd pipe opened on FD 17
  Oct 24 09:35:32 prxysquid squid[3586]: Local cache digest enabled;
  rebuild/rewrite every 3600/3600 sec
  Oct 24 09:35:32 prxysquid squid[3586]: Logfile: opening log
  stdio:/var/log/squid/store.log
  Oct 24 09:35:32 prxysquid squid[3586]: Swap maxSize 2048000 + 8192
  KB,
  estimated 158168 objects
  Oct 24 09:35:32 prxysquid squid[3586]: Target number of buckets:
 7908
  Oct 24 09:35:32 prxysquid squid[3586]: Using 8192 Store buckets
  Oct 24 09:35:32 prxysquid squid[3586]: Max Mem  size: 8192 KB
  Oct 24 09:35:32 prxysquid squid[3586]: Max Swap size: 2048000 KB
  Oct 24 09:35:32 prxysquid squid[3586]: Version 1 of swap file with
  LFS
  support detected... 
  Oct 24 09:35:32 prxysquid squid[3586]: Rebuilding storage
  in /var/cache/squid (DIRTY)
  Oct 24 09:35:32 prxysquid squid[3586]: Using Least Load store dir
  selection
  Oct 24 09:35:32 prxysquid squid[3586]: Set Current Directory
  to /var/squid/cache
  Oct 24 09:35:32 prxysquid squid[3586]: Loaded Icons.
  Oct 24 09:35:32 prxysquid squid[3586]: commBind: Cannot bind socket
  FD
  21 to [::]:22381: (98) Address already in use
  Oct 24 09:35:32 prxysquid squid[3586]: HTCP Disabled.
  Oct 24 09:35:32 prxysquid squid[3586]: Squid plugin modules loaded:
 0
  Oct 24 09:35:32 prxysquid squid[3586]: Adaptation support is on
  Oct 24 09:35:32 prxysquid squid[3586]: Ready to serve requests.
  Oct 24 09:35:32 prxysquid squid[3586]: Stop receiving ICP on
  [::]:3130
  Oct 24 09:35:32 prxysquid squid[3586]: assertion failed:
  icp_v2.cc:778:
  Comm::IsConnOpen(icpOutgoingConn)
  Oct 24 09:35:32 prxysquid squid[3480]: Squid Parent: (squid-1)
  process
  3586 exited due to signal 11 with status 0
  Oct 24 09:35:32 prxysquid squid[3480]: Squid Parent: (squid-1)
  process
  3586 will not be restarted due to repeated, frequent failures
  Oct 24 09:35:32 prxysquid squid[3480]: Exiting due to repeated,
  frequent
  failures
  Oct 24 09:35:32 prxysquid kernel: [145331.125748] squid[3586]:
  segfault
  at 40 ip 081b842c sp bfbab6b0 error 4 in squid[8048000+3d8000] 


I had removed icp_port but the problem still occur : 

notice that i have 

http_port 22381

perhaps it is an ipv6 issue ??

Oct 24 11:34:19 kprxy squid[19120]: Squid Parent: (squid-1) process
19554 exited with status 1
Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
19567 started
Oct 24 11:34:22 kprxy squid[19567]: Starting Squid Cache version
3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...
Oct 24 11:34:22 kprxy squid[19567]: Process ID 19567
Oct 24 11:34:22 kprxy squid[19567]: Process Roles: worker
Oct 24 11:34:22 kprxy squid[19567]: With 1024 file descriptors available
Oct 24 11:34:22 kprxy squid[19567]: Initializing IP Cache...
Oct 24 11:34:22 kprxy squid[19567]: DNS Socket created at [::], FD 8
Oct 24 11:34:22 kprxy squid[19567]: DNS Socket created at 0.0.0.0, FD 9
Oct 24 11:34:22 kprxy squid[19567]: Adding nameserver 192.168.1.1 from
squid.conf
Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log

Re: [squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread Jean-Philippe Menil




I had removed icp_port but the problem still occur :

notice that i have

http_port 22381

perhaps it is an ipv6 issue ??

Oct 24 11:34:19 kprxy squid[19120]: Squid Parent: (squid-1) process
19554 exited with status 1
Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
19567 started
Oct 24 11:34:22 kprxy squid[19567]: Starting Squid Cache version
3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...
Oct 24 11:34:22 kprxy squid[19567]: Process ID 19567
Oct 24 11:34:22 kprxy squid[19567]: Process Roles: worker
Oct 24 11:34:22 kprxy squid[19567]: With 1024 file descriptors available
Oct 24 11:34:22 kprxy squid[19567]: Initializing IP Cache...
Oct 24 11:34:22 kprxy squid[19567]: DNS Socket created at [::], FD 8
Oct 24 11:34:22 kprxy squid[19567]: DNS Socket created at 0.0.0.0, FD 9
Oct 24 11:34:22 kprxy squid[19567]: Adding nameserver 192.168.1.1 from
squid.conf
Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log
daemon:/var/log/squid/access.log
Oct 24 11:34:22 kprxy squid[19567]: Logfile Daemon: opening
log /var/log/squid/access.log
Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log
daemon:/var/log/squid/sarg.log
Oct 24 11:34:22 kprxy squid[19567]: Logfile Daemon: opening
log /var/log/squid/sarg.log
Oct 24 11:34:22 kprxy squid[19567]: Unlinkd pipe opened on FD 17
Oct 24 11:34:22 kprxy squid[19567]: Local cache digest enabled;
rebuild/rewrite every 3600/3600 sec
Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log
stdio:/var/log/squid/store.log
Oct 24 11:34:22 kprxy squid[19567]: Swap maxSize 2048000 + 8192 KB,
estimated 158168 objects
Oct 24 11:34:22 kprxy squid[19567]: Target number of buckets: 7908
Oct 24 11:34:22 kprxy squid[19567]: Using 8192 Store buckets
Oct 24 11:34:22 kprxy squid[19567]: Max Mem  size: 8192 KB
Oct 24 11:34:22 kprxy squid[19567]: Max Swap size: 2048000 KB
Oct 24 11:34:22 kprxy squid[19567]: Version 1 of swap file with LFS
support detected...
Oct 24 11:34:22 kprxy squid[19567]: Rebuilding storage
in /var/cache/squid (DIRTY)
Oct 24 11:34:22 kprxy squid[19567]: Using Least Load store dir selection
Oct 24 11:34:22 kprxy squid[19567]: Set Current Directory
to /var/squid/cache
Oct 24 11:34:22 kprxy squid[19567]: Loaded Icons.
Oct 24 11:34:22 kprxy squid[19567]: commBind: Cannot bind socket FD 21
to [::]:22381: (98) Address already in use
Oct 24 11:34:22 kprxy squid[19567]: HTCP Disabled.
Oct 24 11:34:22 kprxy squid[19567]: Squid plugin modules loaded: 0
Oct 24 11:34:22 kprxy squid[19567]: Adaptation support is on
Oct 24 11:34:22 kprxy squid[19567]: Ready to serve requests.
Oct 24 11:34:22 kprxy squid[19567]: Unable to open HTTP Socket
Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
19567 exited with status 1
Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
19567 will not be restarted due to repeated, frequent failures
Oct 24 11:34:22 kprxy squid[19120]: Exiting due to repeated, frequent
failures



I don't think so.
Please, post log with the debug features.

Regards.

--
Jean-Philippe Menil - Pôle réseau Service IRTS
DSI Université de Nantes
jean-philippe.me...@univ-nantes.fr
Tel : 02.53.48.49.27 - Fax : 02.53.48.49.09



Re: [squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread Amos Jeffries

On 24/10/11 22:38, David Touzeau wrote:

Le lundi 24 octobre 2011 à 10:40 +0200, Fred B a écrit :

De:
Fred B


Hi David,

Please remove icp_port


Oct 24 09:35:32 prxysquid squid[3586]: assertion failed:
icp_v2.cc:778:
Comm::IsConnOpen(icpOutgoingConn)  -  maybe ICP Bug with workers ?



- David Touzeau a écrit :


Dear

I encounter many times this issue.

Cannot bind socket FD 21 to [::]:x: (98) Address already in

use


Perhaps it is a misunderstand of the SMP working process.
I have 2 processors.
Is each worker try to bind the same Port/IP ?




Oct 24 09:35:31 prxysquid-squid squid[3586]: Starting Squid Cache
version 3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...

snip

Oct 24 09:35:32 prxysquid squid[3586]: commBind: Cannot bind socket
FD
21 to [::]:22381: (98) Address already in use


snip


I had removed icp_port but the problem still occur :

notice that i have

http_port 22381

perhaps it is an ipv6 issue ??



Should not be any more IPv6 port issues in 3.2 nowdays. Possibly one 
left when sending v4mapped on a kernel with bind_v6only overrides, but 
that does not show up in the bind() stage.


What does netstat -antup | grep 22381  show?

If *any* IP on the box is already using it the wildcard will fail with 
this message.


NP: I have seen this message happen on Linux if a previous server bound 
the port then crashed. There seems to be a short timeout period where 
nothing else is allowed to touch the port number.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.16
  Beta testers wanted for 3.2.0.13


Re: [squid-users] 3.2.0.13: Cannot bind socket FD 21 to [::]:22381: (98) Address already in use

2011-10-24 Thread David Touzeau
Le lundi 24 octobre 2011 à 11:48 +0200, Jean-Philippe Menil a écrit :
 
  I had removed icp_port but the problem still occur :
 
  notice that i have
 
  http_port 22381
 
  perhaps it is an ipv6 issue ??
 
  Oct 24 11:34:19 kprxy squid[19120]: Squid Parent: (squid-1) process
  19554 exited with status 1
  Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
  19567 started
  Oct 24 11:34:22 kprxy squid[19567]: Starting Squid Cache version
  3.2.0.13-20111023-r11381 for i686-pc-linux-gnu...
  Oct 24 11:34:22 kprxy squid[19567]: Process ID 19567
  Oct 24 11:34:22 kprxy squid[19567]: Process Roles: worker
  Oct 24 11:34:22 kprxy squid[19567]: With 1024 file descriptors available
  Oct 24 11:34:22 kprxy squid[19567]: Initializing IP Cache...
  Oct 24 11:34:22 kprxy squid[19567]: DNS Socket created at [::], FD 8
  Oct 24 11:34:22 kprxy squid[19567]: DNS Socket created at 0.0.0.0, FD 9
  Oct 24 11:34:22 kprxy squid[19567]: Adding nameserver 192.168.1.1 from
  squid.conf
  Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log
  daemon:/var/log/squid/access.log
  Oct 24 11:34:22 kprxy squid[19567]: Logfile Daemon: opening
  log /var/log/squid/access.log
  Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log
  daemon:/var/log/squid/sarg.log
  Oct 24 11:34:22 kprxy squid[19567]: Logfile Daemon: opening
  log /var/log/squid/sarg.log
  Oct 24 11:34:22 kprxy squid[19567]: Unlinkd pipe opened on FD 17
  Oct 24 11:34:22 kprxy squid[19567]: Local cache digest enabled;
  rebuild/rewrite every 3600/3600 sec
  Oct 24 11:34:22 kprxy squid[19567]: Logfile: opening log
  stdio:/var/log/squid/store.log
  Oct 24 11:34:22 kprxy squid[19567]: Swap maxSize 2048000 + 8192 KB,
  estimated 158168 objects
  Oct 24 11:34:22 kprxy squid[19567]: Target number of buckets: 7908
  Oct 24 11:34:22 kprxy squid[19567]: Using 8192 Store buckets
  Oct 24 11:34:22 kprxy squid[19567]: Max Mem  size: 8192 KB
  Oct 24 11:34:22 kprxy squid[19567]: Max Swap size: 2048000 KB
  Oct 24 11:34:22 kprxy squid[19567]: Version 1 of swap file with LFS
  support detected...
  Oct 24 11:34:22 kprxy squid[19567]: Rebuilding storage
  in /var/cache/squid (DIRTY)
  Oct 24 11:34:22 kprxy squid[19567]: Using Least Load store dir selection
  Oct 24 11:34:22 kprxy squid[19567]: Set Current Directory
  to /var/squid/cache
  Oct 24 11:34:22 kprxy squid[19567]: Loaded Icons.
  Oct 24 11:34:22 kprxy squid[19567]: commBind: Cannot bind socket FD 21
  to [::]:22381: (98) Address already in use
  Oct 24 11:34:22 kprxy squid[19567]: HTCP Disabled.
  Oct 24 11:34:22 kprxy squid[19567]: Squid plugin modules loaded: 0
  Oct 24 11:34:22 kprxy squid[19567]: Adaptation support is on
  Oct 24 11:34:22 kprxy squid[19567]: Ready to serve requests.
  Oct 24 11:34:22 kprxy squid[19567]: Unable to open HTTP Socket
  Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
  19567 exited with status 1
  Oct 24 11:34:22 kprxy squid[19120]: Squid Parent: (squid-1) process
  19567 will not be restarted due to repeated, frequent failures
  Oct 24 11:34:22 kprxy squid[19120]: Exiting due to repeated, frequent
  failures
 
 
 I don't think so.
 Please, post log with the debug features.
 
 Regards.
 


Thanks ! i have found the problem

in squid 3.1x, my start script to a squid -k reconfigure before
executing the daemon and i was working without any problem.

Now in squid 3.2x, doing a squid -k reconfigure before load and instance
and create a conflict...






[squid-users] 3.2.0.13: Notice about access_log doc

2011-10-24 Thread David Touzeau
Dear

in 
http://www.squid-cache.org/Doc/config/access_log/


there is mention about 

udp To send each log line as text data to a UDP receiver.
Place: The destination host name or IP and port.
Place Format:   \\host:port

tcp To send each log line as text data to a TCP receiver.
Place: The destination host name or IP and port.
Place Format:   \\host:port


I have tested tcp:\\host:port common
it does not working

but

tcp:host:port common

Working...

Best regards



[squid-users] 3.2.0.13: send log to tcp behavior ?

2011-10-24 Thread David Touzeau
Dear


I'm using 

access_log tcp:127.0.0.1:54424 common

for testing purpose.

I have developed a daemon that listen TCP on specified port.

All logs are correctly sended but there is this behavior :

If my daemon crash and close the current TCP connection with squid,
squid stop sending logs to my daemon.

I need to do a squid -k reconfigure in order to receive again events.

Is there any parameters that force squid to restart connexion or to
re-check target port.

This behavior is dangerous because if the target port is not available
for a short period, no event is sended definitively...


Best regards.





[squid-users] multiple instances peering

2011-10-24 Thread jiluspo
How to make them sibling to each other.
Does it needs name tagging or soft of?

It says cache_peer 127.0.0.1 used more than once or some kind of(I forgot,
currently just use 2 instances).



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



RE: [squid-users] multiple instances peering

2011-10-24 Thread jiluspo
Remedy I have is making name in host file. Is there any other squid
configurations that I might need?

 -Original Message-
 From: jiluspo [mailto:jilu...@smartbro.net]
 Sent: Monday, October 24, 2011 8:42 PM
 To: squid-users@squid-cache.org
 Subject: [squid-users] multiple instances peering
 
 How to make them sibling to each other.
 Does it needs name tagging or soft of?
 
 It says cache_peer 127.0.0.1 used more than once or some kind of(I
 forgot,
 currently just use 2 instances).
 
 
 
 --
 This message has been scanned for viruses and
 dangerous content by MailScanner, and is
 believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



[squid-users] Trying to cache youtube with squid 2.7 and videocache 1.9.1

2011-10-24 Thread Soporte Técnico
Any one has been sucesfull ¿?

I had installed squid 2.7 and python and apache webserver and videocache
1.9.1 for caching youtube (testing purposes, later if sucesfull i´m going to
buy this url rewriter).

I see nothing in cachevideo.log

Any one has been sucesfull with this configuration ?

Any one has been sucesfull caching youtube videos ?

Jorge.




Re: [squid-users] Trying to cache youtube with squid 2.7 and videocache 1.9.1

2011-10-24 Thread Eliezer Croitoru

On 24/10/2011 22:04, Soporte Técnico wrote:

Any one has been sucesfull ¿?

I had installed squid 2.7 and python and apache webserver and videocache
1.9.1 for caching youtube (testing purposes, later if sucesfull i´m going to
buy this url rewriter).

I see nothing in cachevideo.log

Any one has been sucesfull with this configuration ?

Any one has been sucesfull caching youtube videos ?

Jorge.



at my work we have atleast 3 servers with videocache.

Regards Eliezer


Re: [squid-users] failed http redirection

2011-10-24 Thread Adam Binks
Is squid running on port 80 on the destination box ?

If not you either need to redirect to the correct port (3128 squid default) or 
use PREROUTING on your destination host too. 

Maybe a little more insight to your problem would help set the scene

Sent from my iPhone

On 23 Oct 2011, at 15:40, Ivan Matala ivanmat...@gmail.com wrote:

 hello, this is my code
 
 iptables -t nat -A PREROUTING -i tun0 -p tcp -m tcp --match multiport
 --dports 80 -j DNAT --to-destination 118.67.78.136:80
 
 what im trying to do is, im trying to redirect all http requests to a
 foreign proxy, but it fails
 
 thanks


[squid-users] empty acl

2011-10-24 Thread zongo saiba
Greetings to all , 

Just a quick email as I get a warning: empty ACL: acl ads dstdom_regex
/usr/local/etc/squid/ad.block.txt everytime I run the script that enables
the refresh of the ad.block.txt file. I was using linux (Ubuntu server
11.10) and never got that. I am now on freebsd 8.2; this is when the error
above started.  I modified the script and there is  no issue there. 

I can't figure out for the life of me why squid 3.1 is giving that error
message. Any help is much welcome. 

Kind Regards,

Zongo,



Re: [squid-users] configuring splash page

2011-10-24 Thread Alex F
On Mon, Oct 24, 2011 at 6:37 AM, Amos Jeffries wrote:

 The v1.2 helper with sync fixes has not made it to a 3.2 snapshot yet,
 sorry. The 3.2 current snapshot only has the v1.1 helper crash fixes.

 That snapshot will need this on top:
 http://www.squid-cache.org/Versions/v3/3.2/changesets/squid-3.2-11387.patch

 and probably this as well:
 http://www.squid-cache.org/Versions/v3/3.2/changesets/squid-3.2-11386.patch

Ok, I applied these two patches.


 BTW, how can I find out what version is the session helper?
 Cheers.

 ext_session_acl -v  should tell you.

It doesn't work, I already tried it.
/usr/local/squid/libexec/ext_session_acl -v
/usr/local/squid/libexec/ext_session_acl: invalid option -- 'v'


@Andrew, I guess I managed to apply the needed patches.
Now I am getting this behavior:
* I first GET check.html (note that I have ttl=2)
** I am able to make just ONE request which loads up fine.
*** Any other request just redirects to splash.html, unless I access
again check.html, which allows me to request just one link.

10 OK message=Welcome
10 192.168.235.136
10 OK

Is this a configuration problem?
I am following your config example
http://wiki.squid-cache.org/ConfigExamples/Portal/Splash for Squid
Configuration File - Active Mode, for the exact same reasons you
stated there.

BTW, did you leave  /var/lib/squid/session/ intentionally or was it
supposed to be /var/lib/squid/session/session.db?
# Set up the normal session helper. Mind the wrap - this is one line:
external_acl_type session_active_def concurrency=100 ttl=3 %SRC
/usr/lib/squid3/ext_session_acl -a -T 10800 -b /var/lib/squid/session/

Again, this is my config:
external_acl_type session_LOGIN_master concurrency=100 ttl=2 %SRC
/usr/local/squid/libexec/ext_session_acl -T 30 -b
/usr/local/squid//lib/session.db -a
acl session_LOGIN external session_LOGIN_master LOGIN

external_acl_type session_ACTIVE_master concurrency=100 ttl=2 %SRC
/usr/local/squid/libexec/ext_session_acl -T 30 -b
/usr/local/squid/lib/session.db -a
acl session_is_ACTIVE external session_ACTIVE_master

acl clicked_login_url url_regex -i http://192.168.235.136/check.html
http_access allow clicked_login_url session_LOGIN

http_access deny !session_is_ACTIVE
deny_info http://192.168.235.136/splash.html session_is_ACTIVE

Can you please confirm that this type of config is working with you,
so I can be sure that at least this isn't the problem.

Thank you.


Re: [squid-users] configuring splash page

2011-10-24 Thread Andrew Beverley
On Tue, 2011-10-25 at 02:23 +0300, Alex F wrote:
 
  BTW, how can I find out what version is the session helper?
  Cheers.
 
  ext_session_acl -v  should tell you.
 
 It doesn't work, I already tried it.
 /usr/local/squid/libexec/ext_session_acl -v
 /usr/local/squid/libexec/ext_session_acl: invalid option -- 'v'

Not a wholly accurate test, but if you check the man page then that will
tell you the version (man ext_session_acl).

 BTW, did you leave  /var/lib/squid/session/ intentionally or was it
 supposed to be /var/lib/squid/session/session.db?

Ah, that could be your problem. It needs to be /var/lib/squid/session/
(it works with a filename for backward compatibility). Using a directory
causes the helper to open a database environment, which prevents the
sync problems that you are seeing (the man page provides more info). Try
that and it should fix it.

 Can you please confirm that this type of config is working with you,
 so I can be sure that at least this isn't the problem.

My *exact* current config (with extra stuff) that works is as follows:

http_access allow localhost
acl our_networks src 10.0.0.0/16
external_acl_type session_active_def concurrency=100 ttl=3 %SRC 
/usr/lib/squid3/ext_session_acl -a -T 10800 -b /var/lib/squid/session/
acl session_is_active external session_active_def
acl session_day time /var/www/announce_days.txt
deny_info http://nelsonwr.wardroom/announce.php?url=%u session_day 
session_is_active
http_access deny session_day !session_is_active
http_access allow our_networks
http_access deny all

My LOGIN code is contained in a local PHP page that serves up the splash
page (I do this because local web requests bypass Squid):

  $handle = popen($session_helper, 'w');
  fwrite($handle, 10  . $_SERVER['REMOTE_ADDR'] .  LOGIN\n);
  pclose($handle);


Andy




Re: [squid-users] empty acl

2011-10-24 Thread Amos Jeffries

On Mon, 24 Oct 2011 23:48:28 +0100, zongo saiba wrote:

Greetings to all ,

Just a quick email as I get a warning: empty ACL: acl ads 
dstdom_regex
/usr/local/etc/squid/ad.block.txt everytime I run the script that 
enables
the refresh of the ad.block.txt file. I was using linux (Ubuntu 
server
11.10) and never got that. I am now on freebsd 8.2; this is when the 
error

above started.  I modified the script and there is  no issue there.

I can't figure out for the life of me why squid 3.1 is giving that 
error

message. Any help is much welcome.


The file is empty at the time of Squid reconfigure/startup or the Squid 
user account does not have read access to load it.


Amos