squid 3.1.6
прозрачный

squid каждые 60 минут рвет связь, потом восстанавливает, и все могут работать дальше.

те у кого были закачки нужно качать снова, кто работал с удаленным сервером нужно перезаходить в программы.

подскажите где смотреть squid.conf на исправление данной проблеммы.


# TIMEOUTS
# -----------------------------------------------------------------------------

# TAG: forward_timeout time-units
# This parameter specifies how long Squid should at most attempt in
# finding a forwarding path for the request before giving up.
#Default:
# forward_timeout 4 minutes

# TAG: connect_timeout time-units
# This parameter specifies how long to wait for the TCP connect to
# the requested server or peer to complete before Squid should
# attempt to find another path where to forward the request.
#Default:
# connect_timeout 1 minute

# TAG: peer_connect_timeout time-units
# This parameter specifies how long to wait for a pending TCP
# connection to a peer cache. The default is 30 seconds. You
# may also set different timeout values for individual neighbors
# with the 'connect-timeout' option on a 'cache_peer' line.
#Default:
# peer_connect_timeout 30 seconds

# TAG: read_timeout time-units
# The read_timeout is applied on server-side connections. After
# each successful read(), the timeout will be extended by this
# amount. If no data is read again after this amount of time,
# the request is aborted and logged with ERR_READ_TIMEOUT. The
# default is 15 minutes.
#Default:
# read_timeout 15 minutes

# TAG: request_timeout
# How long to wait for an HTTP request after initial
# connection establishment.
#Default:
# request_timeout 5 minutes

# TAG: persistent_request_timeout
# How long to wait for the next HTTP request on a persistent
# connection after the previous request completes.
#Default:
# persistent_request_timeout 2 minutes

# TAG: client_lifetime time-units
# The maximum amount of time a client (browser) is allowed to
# remain connected to the cache process. This protects the Cache
# from having a lot of sockets (and hence file descriptors) tied up
# in a CLOSE_WAIT state from remote clients that go away without
# properly shutting down (either because of a network failure or
# because of a poor client implementation). The default is one
# day, 1440 minutes.
#
# NOTE: The default value is intended to be much larger than any
# client would ever need to be connected to your cache. You
# should probably change client_lifetime only as a last resort.
# If you seem to have many client connections tying up
# filedescriptors, we recommend first tuning the read_timeout,
# request_timeout, persistent_request_timeout and quick_abort values.
#Default:
# client_lifetime 1 day

# TAG: half_closed_clients
# Some clients may shutdown the sending side of their TCP
# connections, while leaving their receiving sides open. Sometimes,
# Squid can not tell the difference between a half-closed and a
# fully-closed TCP connection.
#
# By default, Squid will immediately close client connections when
# read(2) returns "no more data to read."
#
# Change this option to 'on' and Squid will keep open connections
# until a read(2) or write(2) on the socket returns an error.
# This may show some benefits for reverse proxies. But if not
# it is recommended to leave OFF.
#Default:
# half_closed_clients off

# TAG: pconn_timeout
# Timeout for idle persistent connections to servers and other
# proxies.
#Default:
# pconn_timeout 1 minute

# TAG: ident_timeout
# Maximum time to wait for IDENT lookups to complete.
#
# If this is too high, and you enabled IDENT lookups from untrusted
# users, you might be susceptible to denial-of-service by having
# many ident requests going at once.
#Default:
# ident_timeout 10 seconds

# TAG: shutdown_lifetime time-units
# When SIGTERM or SIGHUP is received, the cache is put into
# "shutdown pending" mode until all active sockets are closed.
# This value is the lifetime to set for all open descriptors
# during shutdown mode. Any active clients after this many
# seconds will receive a 'timeout' message.
#Default:
# shutdown_lifetime 30 seconds

acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network

acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 995
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

acl worktime time MTWHF 00:00-04:00
acl noworksites dstdomain "/etc/squid3/badsites.txt"
acl block dstdomain "/etc/squid3/block.txt"

acl ipacl dstdom_regex ^[0-9]*.[0-9]*.[0-9]*.[0-9]*


http_access allow manager localhost
http_access deny manager


http_access deny !Safe_ports


http_access deny CONNECT !SSL_ports

http_access deny block

http_access allow localnet
http_access allow localhost


http_access deny all

http_port 3128

hierarchy_stoplist cgi-bin ?


coredump_dir /var/spool/squid3

refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320

delay_pools 2

delay_class 1 3
delay_class 2 3

delay_access 1 allow noworksites
delay_access 1 deny all
delay_parameters 1 256000/256000 128000/128000 32000/128000

delay_access 2 allow localnet
delay_access 2 deny all
delay_parameters 2 1792000/1792000 1792000/1792000 384000/3276800

crontabs

59 23 * * * /etc/init.d/squid3 restart

Sergey OrlovСтатистику наверное собираете каждый час, там и рестартуете squid, хотя надо squid -k reconfigure, а не restart

но рестарт производится в 23:59 по cronу, при чем тут каждый час.

Спасибо Сергей.

Все работает как надо. каждый час не рвет.

Действительно был крон, второй админ без меня убрал перегрузку проксика каждый час, и все пошло ок.
Сейчас перезагрузка только вечером, когда нет никого на работе.