squid fails to start due to squid.conf

[Guest]

[sawilla]

I'm using EFW 2.3. When I enable the HTTP Proxy (transparent) in the web interface, it looks like it succeeds (the switch goes green) but all clients receive the error: (111) Connection refused. On the status page "Content filter" is shown as STOPPED, and the dashboard shows HTTP Proxy as OFF. The log at /var/log/squid/squid.out has the following errors:

FATAL: Bungled squid.conf line 87: acl allowed_ports       port "/etc/squid/acls/ports.acl"
Squid Cache (Version 2.6.STABLE22): Terminated abnormally.
FATAL: Bungled squid.conf line 87: acl allowed_ports       port "/etc/squid/acls/ports.acl"
Squid Cache (Version 2.6.STABLE22): Terminated abnormally.
2010/05/23 18:29:28| Creating Swap Directories
FATAL: Bungled squid.conf line 90: acl allowed_ports       port "/etc/squid/acls/ports.acl"
Squid Cache (Version 2.6.STABLE22): Terminated abnormally.

(last 2 lines repeat many times, then there are many repeats of:)

FATAL: Bungled squid.conf line 91: acl allowed_ports       port "/etc/squid/acls/ports.acl"
Squid Cache (Version 2.6.STABLE22): Terminated abnormally.

/etc/squid/squid.conf lines 87-91 are:
87: acl from_green          src "/etc/squid/acls/green_subnets.acl"
88: acl to_green            dst "/etc/squid/acls/green_subnets.acl"
89:
90: # allowed ports - acls
91: acl allowed_ports       port "/etc/squid/acls/ports.acl"

I've tried starting squid at the command prompt but it fails:
root@EndianFW:/etc/squid # /etc/init.d/squid start
init_cache_dir /var/spool/squid... Starting squid:         [FAILED]

I haven't modified the squid.conf file and I'm not sure what to try next. Thanks for your help.

Reg

[sawilla]

The problem turned out to be due to the comments following the allowed ports. I removed all the comments (e.g.: "80+#+http" was changed to "80") in the "Allowed ports and ssl ports" section of the "HTTP proxy: Configuration" page and then the service started OK.

[Blazer79]

Thank you for this reply. I had this exact problem today. I can't understand why this problem is still arising almost 4 years later. I'm using version 2.5.1.