Squid issue: Your Squid cache directories Directory-Name, Directory-Name, Directory-Name, Directory-Name, /var/spool/squid have

After the recent upgrades, when I go to Squid in Webmin I see the following message:

"Your Squid cache directories Directory-Name, Directory-Name, Directory-Name, Directory-Name, /var/spool/squid have not been initialized.This must be done before Squid can be run."

When I click the Initialize Cache button, I get the following message:

"Initializing the Squid cache with the command squid -f /etc/squid/squid.conf -z .. FATAL: Bungled squid.conf line 1789: cache_dir Type Directory-Name Fs-specific-data [options] Squid Cache (Version 2.6.STABLE21): Terminated abnormally."

Please could you tell me what I need to do.

If I try to start Squid I get:

"Failed to start Squid : FATAL: Bungled squid.conf line 1789: cache_dir Type Directory-Name Fs-specific-data [options] Squid Cache (Version 2.6.STABLE21): Terminated abnormally."

Status: 
Closed (fixed)

Comments

Howdy -- if you look at your /etc/squid/squid.conf file, what does line 1789 look like? It sounds like there may be a problem with that particular line.

I see the Webmin bug that is causing this - it can happen if you originally had a line in your Squid config like :

# cache_dir Directory-Name

The work-around is to edit squid.conf and remove any such lines, then re-run the initialization in Webmin. A proper fix will be in the next release.

I edited /etc/squid/squid.conf and removed the cache_dir lines. Each time I saved it and reran the Webmin cache routine I get:

FATAL: Bungled squid.conf line 1705: cache_dir Type Directory-Name Fs-specific-data [options] Squid Cache (Version 2.6.STABLE21): Terminated abnormally.

When I go back into /etc/squid/squid.conf the problem lines have reappeared??

Are you sure there isn't any line in squid.conf that contains cache_dir Type ... perhaps one that is commented out?

I guess I must have missed some. I used :g/cache_dir/d in VIM to remove them all this time.

Thanks.

Automatically closed -- issue fixed for 2 weeks with no activity.