Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Squid e SquiGuard - Serviço parado repentinamente

    Scheduled Pinned Locked Moved Portuguese
    8 Posts 3 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      andretoniate
      last edited by

      Ola, boa tarde.

      O serviço do squid e squidguard estão parando sem qualquer alteração no pfsense, o que pode estar ocorrendo?

      Aconteceu esta semana sempre apos as 00:00 e ao longo do dia, inclusive agora a 5 minutos atras.

      Obrigado.

      At,
      André T

      1 Reply Last reply Reply Quote 0
      • T
        tomaswaldow
        last edited by

        Veja em System Logs se algum erro para poder te ajudar…

        Tomas @ 2W Consultoria

        1 Reply Last reply Reply Quote 0
        • A
          andretoniate
          last edited by

          @Tomas:

          Veja em System Logs se algum erro para poder te ajudar…

          Bom dia.
          Segue log abaixo, só não entendo porque o squid está sem permissão para acesso ao arquivo de log ou melhor está "perdendo" a permissão. Eu refiz a permissão para a pasta e alguns dias depois perde a permissão. O que pode estar ocorrendo?

          
[b]Mar  7 00:00:20 getcontrol squid[63479]: Cannot open /var/squid/log/access.log: (13) Permission denied[/b]
Mar  7 00:00:20 getcontrol kernel: pid 63479 (squid), uid 62: exited on signal 6
Mar  7 00:00:20 getcontrol squid[62935]: Squid Parent: child process 63479 exited due to signal 6
Mar  7 00:00:23 getcontrol squid[62935]: Squid Parent: child process 7815 started
Mar  7 00:00:24 getcontrol squid[7815]: Cannot open '/var/squid/log/access.log' for writing. 	The parent directory must be writeable by the 	user 'proxy', which is the cache_effective_user 	set in squid.conf.
Mar  7 00:00:24 getcontrol squid[62935]: Squid Parent: child process 7815 exited due to signal 6
Mar  7 00:00:24 getcontrol kernel: pid 7815 (squid), uid 62: exited on signal 6
Mar  7 00:00:27 getcontrol squid[62935]: Squid Parent: child process 63211 started
Mar  7 00:00:27 getcontrol squid[63211]: Cannot open '/var/squid/log/access.log' for writing. 	The parent directory must be writeable by the 	user 'proxy', which is the cache_effective_user 	set in squid.conf.
Mar  7 00:00:27 getcontrol squid[62935]: Squid Parent: child process 63211 exited due to signal 6
Mar  7 00:00:27 getcontrol kernel: pid 63211 (squid), uid 62: exited on signal 6
Mar  7 00:00:30 getcontrol squid[62935]: Squid Parent: child process 13351 started
Mar  7 00:00:30 getcontrol squid[13351]: Cannot open '/var/squid/log/access.log' for writing. 	The parent directory must be writeable by the 	user 'proxy', which is the cache_effective_user 	set in squid.conf.
Mar  7 00:00:30 getcontrol kernel: pid 13351 (squid), uid 62: exited on signal 6
Mar  7 00:00:30 getcontrol squid[62935]: Squid Parent: child process 13351 exited due to signal 6
Mar  7 00:00:33 getcontrol squid[62935]: Squid Parent: child process 91881 started
Mar  7 00:00:33 getcontrol squid[91881]: Cannot open '/var/squid/log/access.log' for writing. 	The parent directory must be writeable by the 	user 'proxy', which is the cache_effective_user 	set in squid.conf.
Mar  7 00:00:34 getcontrol kernel: pid 91881 (squid), uid 62: exited on signal 6
Mar  7 00:00:33 getcontrol squid[62935]: Squid Parent: child process 91881 exited due to signal 6
Mar  7 00:00:36 getcontrol squid[62935]: Squid Parent: child process 19880 started
Mar  7 00:00:36 getcontrol squid[19880]: Cannot open '/var/squid/log/access.log' for writing. 	The parent directory must be writeable by the 	user 'proxy', which is the cache_effective_user 	set in squid.conf.
Mar  7 00:00:36 getcontrol squid[62935]: Squid Parent: child process 19880 exited due to signal 6
Mar  7 00:00:36 getcontrol kernel: pid 19880 (squid), uid 62: exited on signal 6
Mar  7 00:00:36 getcontrol squid[62935]: Exiting due to repeated, frequent failures

          At,
          André T

          1 Reply Last reply Reply Quote 0
          • A
            andretoniate
            last edited by

            Apos dar permissao ao user proxy na pasta voltou a funcionar, porem agora as 12h novamente parou, segue log abaixo.

            Mar 7 12:00:22	squid[13059]: Exiting due to repeated, frequent failures
Mar 7 12:00:22	kernel: pid 37412 (squid), uid 62: exited on signal 6
Mar 7 12:00:22	squid[13059]: Squid Parent: child process 37412 exited due to signal 6
Mar 7 12:00:22	squid[37412]: The url_rewriter helpers are crashing too rapidly, need help!
Mar 7 12:00:21	squid[13059]: Squid Parent: child process 37412 started
Mar 7 12:00:18	kernel: pid 59824 (squid), uid 62: exited on signal 6
Mar 7 12:00:18	squid[13059]: Squid Parent: child process 59824 exited due to signal 6
Mar 7 12:00:18	squid[59824]: The url_rewriter helpers are crashing too rapidly, need help!
Mar 7 12:00:17	squid[13059]: Squid Parent: child process 59824 started
Mar 7 12:00:14	squid[13059]: Squid Parent: child process 74950 exited due to signal 6
Mar 7 12:00:14	kernel: pid 74950 (squid), uid 62: exited on signasw6
Mar 7 12:00:14	squid[74950]: The url_rewriter helpers are crashing too rapidly, need help!
Mar 7 12:00:13	squid[13059]: Squid Parent: child process 74950 started
Mar 7 12:00:10	squid[13059]: Squid Parent: child process 239 exited due to signal 6
Mar 7 12:00:09	kernel: pid 239 (squid), uid 62: exited on signal 6
Mar 7 12:00:09	squid[239]: The url_rewriter helpers are crashing too rapidly, need help!
Mar 7 12:00:09	squid[13059]: Squid Parent: child process 239 started
Mar 7 12:00:06	squid[13059]: Squid Parent: child process 23075 exited due to signal 6
Mar 7 12:00:05	kernel: pid 23075 (squid), uid 62: exited on signal 6
Mar 7 12:00:05	squid[23075]: The url_rewriter helpers are crashing too rapidly, need help!
Mar 7 12:00:05	squid[13059]: Squid Parent: child process 23075 started
Mar 7 12:00:02	squid[13059]: Squid Parent: child process 13325 exited due to signal 6
Mar 7 12:00:02	kernel: pid 13325 (squid), uid 62: exited on signal 6
Mar 7 12:00:02	squid[13325]: The url_rewriter helpers are crashing too rapidly, need help!

            At,
            André T

            1 Reply Last reply Reply Quote 0
            • maxwelberM
              maxwelber
              last edited by

              Qual versão do pfsense e squid? Estou tendo problemas parecidos de parar do nada tbm.

              1 Reply Last reply Reply Quote 0
              • T
                tomaswaldow
                last edited by

                Tem pelo menos uma Target criada no squidGuard?

                Tomas @ 2W Consultoria

                1 Reply Last reply Reply Quote 0
                • A
                  andretoniate
                  last edited by

                  @maxwelber:

                  Qual versão do pfsense e squid? Estou tendo problemas parecidos de parar do nada tbm.

                  pfsense 2.1 / squid 2.7
                  @Tomas:

                  Tem pelo menos uma Target criada no squidGuard?

                  Sim

                  At,
                  André T

                  1 Reply Last reply Reply Quote 0
                  • A
                    andretoniate
                    last edited by

                    Bom dia.

                    Dei permissão novamente ao diretorio para o proxy e novamente a permisso foi desfeita, o que pode estar ocorrendo?
                    /var/squid/log

                    -rw-r--r--  1 root   proxy  1 Mar 10 00:00 access.log
-rw-r-----  1 proxy  proxy  1 Mar 10 00:00 access.log.0
-rw-r-----  1 proxy  proxy  1 Mar 10 00:00 access.log.1
-rw-r-----  1 proxy  proxy  1 Mar 10 00:00 access.log.2
-rw-r--r--  1 root   proxy  1 Mar 10 00:00 cache.log
-rw-r--r--  1 root   proxy  1 Mar 10 00:00 cache.log.0
-rw-r--r--  1 root   proxy  1 Mar 10 00:00 cache.log.1
-rw-r--r--  1 root   proxy  1 Mar 10 00:00 cache.log.2

                    Abaixo log apos tentar iniciar mesmo sem permissao de acesso ao access.log

                    Mar 10 07:02:01	kernel: pid 4748 (squid), uid 62: exited on signal 6
Mar 10 07:02:01	squid[94100]: Squid Parent: child process 4748 exited due to signal 6
Mar 10 07:02:01	squid[4748]: Cannot open '/var/squid/log/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf.
Mar 10 07:02:01	squid[94100]: Squid Parent: child process 4748 started
Mar 10 07:01:58	kernel: pid 2941 (squid), uid 62: exited on signal 6
Mar 10 07:01:58	squid[94100]: Squid Parent: child process 2941 exited due to signal 6
Mar 10 07:01:58	squid[2941]: Cannot open '/var/squid/log/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf.
Mar 10 07:01:58	squid[94100]: Squid Parent: child process 2941 started
Mar 10 07:01:55	kernel: pid 97110 (squid), uid 62: exited on signal 6
Mar 10 07:01:55	squid[94100]: Squid Parent: child process 97110 exited due to signal 6
Mar 10 07:01:55	squid[97110]: Cannot open '/var/squid/log/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf.
Mar 10 07:01:55	squid[94100]: Squid Parent: child process 97110 started
Mar 10 07:01:52	kernel: pid 94352 (squid), uid 62: exited on signal 6
Mar 10 07:01:52	squid[94100]: Squid Parent: child process 94352 exited due to signal 6
Mar 10 07:01:52	squid[94352]: Cannot open '/var/squid/log/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf.
Mar 10 07:01:52	squid[94100]: Squid Parent: child process 94352 started
Mar 10 07:01:49	php: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was 'squid: ERROR: Could not send signal 15 to process 83784: (3) No such process'

                    Qual a recomendação?

                    At,
                    André T

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.