SARG Error Generate

27 03 2009

Td pagi abis nambah paket baru SARG di router Ubuntu 8.04 Hardy Heron LTS wnet punya tmn, pdhal smua seting dah pd bener cmn pas wkt generate koq malah gini:
sarg -l /var/log/squid/access.log
*** stack smashing detected ***: sarg terminated
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7e89138]
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7e890f0]
sarg[0x805eea7]
[0x5a555142]
======= Memory map: ========
08048000-08084000 r-xp 00000000 08:01 921217 /usr/bin/sarg
08084000-08090000 rw-p 0003b000 08:01 921217 /usr/bin/sarg
08090000-0825c000 rw-p 08090000 00:00 0 [heap]
...

Read the rest of this entry »





access.log di SQUID

3 11 2008

TCP_HIT ::: A valid copy of the requested object was in the cache.
TCP_MISS ::: The requested object was not in the cache.
TCP_REFRESH_HIT ::: The requested object was cached but STALE. The IMS query for the object resulted in "304 not modified".
TCP_REFRESH_FAIL_HIT ::: The requested object was cached but STALE. The IMS query failed and the stale object was delivered.
TCP_REFRESH_MISS ::: The requested object was cached but STALE. The IMS query returned the new content.
TCP_CLIENT_REFRESH_MISS ::: The client issued a "no-cache" pragma, or some analogous cache control command along with the request. Thus, the cache has to refetch the object.
TCP_IMS_HIT ::: The client issued an IMS request for an object which was in the cache and fresh.
TCP_SWAPFAIL_MISS ::: The object was believed to be in the cache, but could not be accessed.
TCP_NEGATIVE_HIT ::: Request for a negatively cached object, e.g. "404 not found", for which the cache believes to know that it is inaccessible. Also refer to the explainations for negative_ttl in your squid.conf file.
TCP_MEM_HIT ::: A valid copy of the requested object was in the cache and it was in memory, thus avoiding disk accesses.
TCP_DENIED ::: Access was denied for this request.
TCP_OFFLINE_HIT ::: The requested object was retrieved from the cache during offline mode. The offline mode never validates any object, see offline_mode in squid.conf file.
TCP_STALE_HIT ::: The object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error.
TCP_ASYNC_HIT ::: A background request (e.g., one started by stale-while-revalidate) resulted in a refresh hit.
TCP_ASYNC_MISS ::: A background request (e.g., one started by stale-while-revalidate) resulted in a miss; i.e., the cached object (if any) was updated).
UDP_HIT ::: A valid copy of the requested object was in the cache.
UDP_MISS ::: The requested object is not in this cache.
UDP_DENIED ::: Access was denied for this request.
UDP_INVALID ::: An invalid request was received.
UDP_MISS_NOFETCH ::: During "-Y" startup, or during frequent failures, a cache in hit only mode will return either UDP_HIT or this code. Neighbours will thus only fetch hits.
NONE ::: Seen with errors and cachemgr requests.

The following codes are no longer available in Squid-2:
ERR_* ::: Errors are now contained in the status code.
TCP_CLIENT_REFRESH ::: See: TCP_CLIENT_REFRESH_MISS.
TCP_SWAPFAIL ::: See: TCP_SWAPFAIL_MISS.
TCP_IMS_MISS ::: Deleted, now replaced with TCP_IMS_HIT.
UDP_HIT_OBJ ::: Refers to an old version that would send cache hits in ICP replies. No longer implemented.
UDP_RELOADING ::: See: UDP_MISS_NOFETCH.

Sumber