[squid-users] General Questions in squid 4.x

[Dr.X]

Hello James ,
Thank you for your reply,
But I don’t have cache manager enabled .

From: James Zuelow <james.zuelow at juneau.gov>
Date: Thursday, 13 April 2023 02:15
To: 'Dr.X' <0xff1f at gmail.com>
Subject: RE: General Questions in squid 4.x
For question 1, try using squidclient to retrieve mgr:config from your local server.  That will at least show you the currently running setup (including things like ACLs) which will let you re-create a configuration file.

For example, on my server (running on port 8080) it would look like this:

squidclient -h 127.0.0.1 -p 8080 -U cachemgr -W password mgr:config

where password is your cachemgr_password.   Your settings may dictate a different user.

For question 2, I believe that mgr:config resolves this as well.


James Zuelow
Systems Operations Manager
City and Borough of Juneau Information Technology
(907) 586-5295 x4212

From: squid-users <squid-users-bounces at lists.squid-cache.org> On Behalf Of Dr.X
Sent: Wednesday, April 12, 2023 1:37 PM
To: squid-users at lists.squid-cache.org
Subject: [squid-users] General Questions in squid 4.x
Importance: High

Hi Squid Folks,

I have a few questions regarding Squid:

Question #1:

My Squid server is working fine, but we accidentally removed the conf file. The service is still running without any issues, but if we stop it, we won't be able to power it up again as no conf file exists. Is there a file dropped in RAM or somewhere else where we can retrieve the configuration file?

Question #2:

I believe there are some Squid config directives that are added by default to squid.conf and are hidden in the config file. Is there a way to check all the Squid directives that are loaded, whether they are hidden or not?

Question #3:

If we start Squid but mistakenly start it again, we receive the error message below:

2023/04/12 17:33:52| FATAL: squid is already running: Found fresh instance PID file (/var/run/squidtest.pid) with PID 959949
exception location: Instance.cc(121) ThrowIfAlreadyRunningWith

As a result, the old service becomes dead, and we have to stop and start it again. Is there any Squid directive that prevents the instance from crashing in case we accidentally start it again?

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20230413/701cf836/attachment-0001.htm>