Bug(let) in 2.2.STABLE4?

 Version: Squid/2.2.STABLE4 (no patches)
    Opts: --enable-xmalloc-statistics
          --enable-async-io
          --enable-cache-digests
Platform: Sun Solaris 2.5.1 (SPARC)

Seen in cache.log:

  WARNING: Probable misconfigured neighbor at x.x.x.x
  WARNING: 5765 of the last 5765 ICP replies are DENIED
  WARNING: No replies will be sent for the next 3600 seconds

yet in cachemgr, the "List of Unknown sites sending ICP messages" reports:

  There are no neighbors installed.

- dump_peers() [line 1173, file ./src/neighbors.c] is called by both
  neighborDumpPeers() and neighborDumpNonPeers() [same file], with no
  distinction for peers/non-peers passed to dump_peers(). To save on
  confusion, could the message above [line 1180] be changed to:

  There are no neighbors installed or detected.

  or alternatively could neighborDumpPeers() and neighborDumpNonPeers() pass
  a flag/msg to indicate which message should be displayed:

  There are no neighbors installed.
  There are no non-neighbors detected.

- clientdbCutoffDenied() [line 96, file ./src/client_db.c] does not update
  non_peers when the above "WARNING" message is displayed; could non_peers
  be exported (or an accessor function created) so that as the above WARNING
  is logged, the client is added to the non_peers list?

- alternatively, could neighborsUdpAck() [line 735, file ./src/neighbors.c]
  be updated to add the misconfigured peer to non_peers upon receipt of an
  ICP_OP_QUERY opcode?

Thanks..

dave
Received on Sat Jul 31 1999 - 22:05:50 MDT