On 2016-12-17 18:39, Odhiambo Washington wrote:
Also whether swap.state for that cache_dir is being correctly and
completely
written out to disk on shutdown or restart. Using an outdated
swap.state
file can also lead to these warnings.
The last paragraph explains your issue. The signal 6 (abort) forces
Squid worker to terminate immediately (to avoid all required
shutdown procedures) and leave core dump. You can find a reason for
abort in cache.log.
Garri
Hi Garri,
So, checking, I don't see swap.state being written to disk and there
is no core dump either.
swap.state description [1]:
This index file holds
the metadata of objects saved on disk. It is used to rebuild
the cache during startup. Normally this file resides in each
'cache_dir' directory, but you may specify an alternate
pathname here.
You can learn how to get core dump on wiki [2].
There is no directive in my squid.conf to suppress the two.
What do you mean?
AIUI, your Squid instance faced unexpected event and initiated abort.
Abort produces core dump which could be useful for developers to
investigate unexpected event. As a side effect of abort, swap.state file
was not updated correctly. The errors you see in cache.log are harmless
and just confirm that swap.state and cache_dir objects are not
synchronized due to abort.
You should concentrate on an event which led to abort. Usually, Squid
inform about unexpected event in cache.log. Find the lines before
'Starting Squid Cache version'.
[1] http://www.squid-cache.org/Doc/config/cache_swap_state/
[2]
http://wiki.squid-cache.org/SquidFaq/BugReporting#crashes_and_core_dumps
Garri
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
