On 27/11/2015 7:19 p.m., Alex Samad wrote: > On 27 November 2015 at 17:12, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: >> On 27/11/2015 1:51 p.m., Alex Samad wrote: >>> Hi >>> >>> Just to add to this, I am not seeing a clean start of squid either. >>> the sysvinit comes back as failed, but the process is started and its >>> seems to be working. >>> >>> Also I get lots of >>> ignoring malformed cache entry >>> >> >> Which is preceeded by: > > Hi > > it was in the bottom of the previous mail, thats a copy of the log > starting from the start up Exactly. The new install of Squid is a newer version. With a new format of cache storage, updated data corruption protection, and detection. The old install was so old it had a v1 cache format, which is a clear sign that the old version also lacked some of those corruption protections. It is not unexpected to see signs of that lack in the old cache contents. > > This is is trying to start up > > 2015/11/27 11:02:41 kid1| Set Current Directory to /var/spool/squid > 2015/11/27 11:02:41 kid1| Starting Squid Cache version 3.5.11 for > x86_64-redhat-linux-gnu... ... > 2015/11/27 11:02:41 kid1| Rejecting swap file v1 to avoid cache index > corruption. Forcing a full cache index rebuild. See Squid bug #3441. > 2015/11/27 11:02:41 kid1| Rebuilding storage in /var/spool/squid (no log) > 2015/11/27 11:02:41 kid1| Rejecting swap file v1 to avoid cache index > corruption. Forcing a full cache index rebuild. See Squid bug #3441. > 2015/11/27 11:02:41 kid1| Rebuilding storage in /var/spool/squid2 (no log) > 2015/11/27 11:02:41 kid1| Rejecting swap file v1 to avoid cache index > corruption. Forcing a full cache index rebuild. See Squid bug #3441. > 2015/11/27 11:02:41 kid1| Rebuilding storage in /var/spool/squid3 (no log) ... > 2015/11/27 11:03:33 kid1| WARNING: Ignoring malformed cache entry. > 2015/11/27 11:03:33 kid1| WARNING: Ignoring malformed cache entry. > 2015/11/27 11:04:26 kid1| Done scanning /var/spool/squid dir (153502 entries) > 2015/11/27 11:04:44 kid1| WARNING: Ignoring malformed cache entry. > 2015/11/27 11:06:15 kid1| WARNING: Ignoring malformed cache entry. > ... Until all of the cache directories have been fully scanned, their contents corrected, and the new swap.state journals produced you can expect to see various warnings or messages about cache content errors. I see /var/spool/squid completed scanning this time (but not the other cache_dir). If the proxy shuts down cleanly, then you should not see the "Rejecting swap file v1" message for it on next startup, nor warnings about the objects inside it. It is only a worry if your Squid shutdown correctly (fully) and they occur on the next run as well. That said, not much of a worry because Squid is detecting and handling it well enough to just warn and keep operating. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
