Project

General

Profile

Actions

Bug #4388

closed

Squid exits when listening on port 800

Added by Vincent Bentley almost 10 years ago. Updated over 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Squid
Target version:
-
Start date:
02/08/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.2
Affected Plus Version:
Affected Architecture:
amd64

Description

Squid 3.4.10_2 pkg 0.2.6 running on 2.2 Release AMD64
After changing the port that the proxy listens on from 3128 to 800, Squid attempts to start but exits after frequent failures. This is with transparent proxy enabled for LAN and OPT1. Changing the listening port back to 3128 enables Squid to start and stay running. The listening port was changed using the package GUI.

Listening ports 3129 and 8080 appear to work.
Listening ports 800, 801, 808 do not work.

Should Squid be configurable to listen on any available port or should the GUI be changed to have a selection list of approved ports instead?

Squid 3.1.20 pkg 2.1.2 running on 2.1.5 Release i386 is unaffected.

Excerpt from Status: System Logs: General...

Feb 7 23:25:50 squid4370: Exiting due to repeated, frequent failures
Feb 7 23:25:50 squid4370: Squid Parent: (squid-1) process 44659 will not be restarted due to repeated, frequent failures
Feb 7 23:25:50 squid4370: Squid Parent: (squid-1) process 44659 exited with status 1
Feb 7 23:25:50 (squid-1): Unable to open HTTP Socket
Feb 7 23:25:50 squid4370: Squid Parent: (squid-1) process 44659 started
Feb 7 23:25:47 squid4370: Squid Parent: (squid-1) process 41436 exited with status 1
Feb 7 23:25:47 (squid-1): Unable to open HTTP Socket
Feb 7 23:25:46 squid4370: Squid Parent: (squid-1) process 41436 started

Actions #1

Updated by Kill Bill over 9 years ago

System - Advanced - System Tunebles: edit net.inet.ip.portrange.first

Duplicate of #4297

Actions #2

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF