No Running Copy Squid Error
Contents |
I have a solution to this problem! First off, I figured out why cache.log and access.log were 0 bytes: It turns out squid 2.6.STABLE1 puts its logs in
Squid Error No Running Copy Centos
/var/log/squid, while 2.6.STABLE9 puts them in another directory altogether. I think it was zero sized reply squid error /var/spool/squid/logs. It was entirely by accident that I happened to find them. The problem of no running copy: The first (squid): cannot open http port line of the log I posted below was a clue: DNS tests failed. It turns out my routing tables were somehow messed up. I could ping and lynx, though, which made it more
Squid Dead But Pid File Exists
confusing. Once I fixed the routing tables, squid was able to start normally. I now have *yet another* problem with squid, which I will post in a new message. Thanks for the help. -----Original Message----- From: Angela Burrell [mailto:angela@jobsearchnetwork.ca] Sent: March 7, 2007 5:45 PM To: squid users Subject: RE: [squid-users] ERROR: No running copy! I have some additional information to report. First of all, the
Zero Sized Reply Barracuda
cache.log and access.log are still 0 bytes. I ran squid with -X -s (Xtra super logging, log to syslog) and got the following new error messages in my /var/log/syslog file: (because it is in syslog I do not know if all messages were generated from squid or not; also because the error msgs are redundant I have only copied a single line of each) Mar 7 17:17:10 proxy squid[27306]: ipcache_init: DNS name lookup tests failed. Mar 7 17:17:10 proxy squid[27304]: Squid Parent: child process 27306 exited due to signal 6 Mar 7 17:17:13 proxy (squid): Memory pools are 'off'; limit: 0.00 MB Mar 7 17:17:13 proxy (squid): diskd started Mar 7 17:17:13 proxy squid[27375]: Starting Squid Cache version 2.6.STABLE9 for amd64-debian-linux-gnu... Mar 7 17:17:13 proxy squid[27375]: Process ID 27375 Mar 7 17:17:13 proxy squid[27304]: Squid Parent: child process 27375 started Mar 7 17:17:13 proxy squid[27375]: With 1024 file descriptors available Mar 7 17:17:13 proxy squid[27375]: Using epoll for the IO loop Mar 7 17:17:13 proxy squid[27375]: Performing DNS Tests... Mar 7 17:17:16 proxy squid[27377]: execvp failed: (2) No such file or directory Mar 7 17:17:16 proxy squid[27377]: Squid Parent: child process 0 started Mar 7 17:17:
Tue, 20 Jul 2004 10:26:47 +0200 Thank you, but I have already restarted several times and all it´s failed... -----Mensaje squid debug_options original----- De: Elsen Marc [mailto:elsen@imec.be] Enviado el: martes 20 de julio de
Squid The Proxy Server Is Refusing Connections
2004 10:28 Para: Prada Mateo, Manuel; squid-users@squid-cache.org Asunto: RE: [squid-users] squid: ERROR: No running copy > > Hi! squid error log > > I am running Squid 2.5 stable with Linux 9 and, since I used the "-k > reconfigure" option, > squid don´t run nevermore... squid: ERROR: No running copy > http://www.squid-cache.org/mail-archive/squid-users/200703/0204.html > I have read from FAQ this solution: > <..> > 11.43. squid: ERROR: no running copy > You may get this message when you run commands like squid -krotate. > This error message usually means that the squid.pid file is missing. > Since the PID file is normally present when squid is running, the > absence of the PID file usually means http://www.squid-cache.org/mail-archive/squid-users/200407/0544.html Squid is not running. If you > accidentally delete the PID file, Squid will continue > running, and you > won't be able to send it any signals. > If you accidentally removed the PID file, there are two ways > to get it > back. > 1. run ps and find the Squid process id. You'll probably see two > processes, like this: > bender-wessels % ps ax | grep squid > 83617 ?? Ss 0:00.00 squid -s > 83619 ?? S 0:00.48 (squid) -s (squid) > You want the second process id, 83619 in this case. Create the PID > file and put the process id number there. For example: > echo 83619 > /usr/local/squid/logs/squid.pid > 2. Use the above technique to find the Squid process id. Send the > process a HUP signal, which is the same as squid -kreconfigure: > kill -HUP 83619 > The reconfigure process creates a new PID file automatically. >... >... > But I don´t have the process up and, therefore, I can´t > create the PID > file and put the process id number there... > An
Evento Oportunidade de trabalho Pergunta Script Screenshot Sobre Contato Anuncie FAQ Política de privacidade Quem somos Termos de uso LoginCadastre-se Home Dicas Linux Configuração Squid: "ERROR: no running copy" [Resolvido] https://www.vivaolinux.com.br/dica/Squid-ERROR-no-running-copy-Resolvido Squid: "ERROR: no running copy" [Resolvido] Publicado por Jeferson R. Costa em 12/02/2014 [ Hits: 11.051 ] Blog: http://www.jefersonrc.com.br/ 0 0 Denuncie Favoritos Indicar Impressora Squid: "ERROR: no running copy" [Resolvido] Na dica de hoje, vou mostrar como resolver um problema que pode ser um pouco preocupante, para quem trabalha com o Squid. squid error O problema, é que quando vamos usar alguma ferramenta do Squid, como por exemplo, recarregar as configurações com o comando squid -k reconfigure, o resultado será o erro no console: Squid: ERROR: no running copy Além disso, outro problema, é que o Squid não aplica as regras que são necessárias, por exemplo, não no running copy bloqueia os sites que deveria bloquear. Como a maioria dos serviços o Squid armazena o PID do seu processo principal (o Squid executa geralmente em dois processos) em um arquivo, que é setado no squid.conf através do parâmetro pid_filename, e geralmente fica em /var/run/squid.pid. Esse arquivo é atualizado com o PID, sempre que o serviço é iniciado ou reiniciado. O problema é que, em alguns momentos, pode acontecer do Squid ser finalizado incorretamente, seja intencional ou não, e nestes casos, pode acontecer de o arquivo não ser atualizado com o PID atual do processo, deixando o serviço perdido. Bom, sabendo qual é o problema, você, provavelmente, já pensou na solução (atualizar o arquivo com o PID atual), uma vez que reiniciar o Squid não resolverá o problema, e é isso que vou mostrar aqui. Para pegarmos o PID do processo atual, devemos rodar o seguinte comando: ps aux | grep -i squid A saída será mais ou menos assi