Erro ao iniciar squid

mn.2192
(usa Slackware)

Enviado em 04/02/2011 - 18:14h

Squid não inicia.
Ao digitar squid -NCd1
2011/02/04 17:59:22| Done reading /var/lib/squid/cache swaplog (0 entries)
2011/02/04 17:59:22| Finished rebuilding storage from disk.
2011/02/04 17:59:22| 0 Entries scanned
2011/02/04 17:59:22| 0 Invalid entries.
2011/02/04 17:59:22| 0 With invalid flags.
2011/02/04 17:59:22| 0 Objects loaded.
2011/02/04 17:59:22| 0 Objects expired.
2011/02/04 17:59:22| 0 Objects cancelled.
2011/02/04 17:59:22| 0 Duplicate URLs purged.
2011/02/04 17:59:22| 0 Swapfile clashes avoided.
2011/02/04 17:59:22| Took 0.3 seconds ( 0.0 objects/sec).
2011/02/04 17:59:22| Beginning Validation Procedure
2011/02/04 17:59:22| Completed Validation Procedure
2011/02/04 17:59:22| Validated 0 Entries
2011/02/04 17:59:22| store_swap_size = 0k
2011/02/04 17:59:23| storeLateRelease: released 0 objects
2011/02/04 17:59:26| sslReadServer: FD 34: read failure: (104) Connection reset by peer
2011/02/04 18:00:26| sslReadServer: FD 34: read failure: (104) Connection reset by peer
2011/02/04 18:00:42| sslReadServer: FD 34: read failure: (104) Connection reset by peer
2011/02/04 18:01:16| sslReadServer: FD 34: read failure: (104) Connection reset by peer
2011/02/04 18:01:34| sslReadServer: FD 34: read failure: (104) Connection reset by peer
2011/02/04 18:01:49| sslReadServer: FD 39: read failure: (104) Connection reset by peer
2011/02/04 18:02:04| sslReadServer: FD 34: read failure: (104) Connection reset by peer
2011/02/04 18:02:45| Preparing for shutdown after 69 requests
2011/02/04 18:02:45| Waiting 0 seconds for active connections to finish
2011/02/04 18:02:45| FD 31 Closing HTTP connection
2011/02/04 18:02:45| Closing Pinger socket on FD 35
2011/02/04 18:02:46| Shutting down...
2011/02/04 18:02:46| FD 32 Closing ICP connection
2011/02/04 18:02:46| FD 33 Closing SNMP socket
2011/02/04 18:02:46| Closing unlinkd pipe on FD 29
2011/02/04 18:02:46| storeDirWriteCleanLogs: Starting...
2011/02/04 18:02:47| Finished. Wrote 0 entries.
2011/02/04 18:02:47| Took 0.0 seconds ( 0.0 entries/sec).
2011/02/04 18:02:47| Squid Cache (Version 2.5.STABLE10): Exiting normally.

fs.schmidt
(usa CentOS)

Enviado em 04/02/2011 - 23:15h

Olá amigo, veja se ajuda:

http://info.ccone.at/INFO/Squid/FAQ-11.html

11.41 What does sslReadClient: FD 14: read failure: (104) Connection reset by peer mean?

``Connection reset by peer'' is an error code that Unix operating systems sometimes return for read, write, connect, and other system calls.

Connection reset means that the other host, the peer, sent us a RESET packet on a TCP connection. A host sends a RESET when it receives an unexpected packet for a nonexistent connection. For example, if one side sends data at the same time that the other side closes a connection, when the other side receives the data it may send a reset back.

The fact that these messages appear in Squid's log might indicate a problem, such as a broken origin server or parent cache. On the other hand, they might be ``normal,'' especially since some applications are known to force connection resets rather than a proper close.

You probably don't need to worry about them, unless you receive a lot of user complaints relating to SSL sites.

Rick Jones notes that if the server is running a Microsoft TCP stack, clients receive RST segments whenever the listen queue overflows. In other words, if the server is really busy, new connections receive the reset message. This is contrary to rational behaviour, but is unlikely to change.

mn.2192
(usa Slackware)

Enviado em 05/02/2011 - 09:30h

Este link não é válido

renato_pacheco
(usa Debian)

Enviado em 05/02/2011 - 12:04h

Coloca o conteúdo do seu squid.conf ae.

mn.2192
(usa Slackware)

Enviado em 05/02/2011 - 13:16h

Oi, pessoal. Fiz uma alteração no arquivo www - removi todo os relátórios de acessos que tinham lá, e o squid até agora não caiu. Obrigada, segundo confirmo se isso funcionou.
Obrigada a todos.