Web Proxy stops immediately after upgrade to 157

Networking Web Proxy
1

I’ve got a backup/test install of IPFire in a VM that I’ve upgraded from 156 to 157 and hit a problem where the Web Proxy stops immediately after following a reboot.

08:37:54 squid[2693]: Squid Parent: squid-1 process 2700 exited with status 0
08:37:54 squid[2693]: Squid Parent: (squid-1) process 2700 started
08:37:54 squid[2693]: Squid Parent: will start 1 kids

If I do a ‘Save and Restart’ the Web Proxy starts and runs correctly.

Automatic start of Web Proxy on 156 worked ok.

I have restored the VM to 156 and repeated the upgrade but the problem persists.

Any ideas what might be wrong or what further steps I can take to identify the problem?

2

Try to change some settings in Network → Web Proxy:
Memory cache size (MB): 10
Harddisk cache size (MB): 1024
then press “save and restart” button.

3

Hello @flaorus and welcome to the IPFire users Community !

These settings are in the “Cache management” section of the Web proxy page, right ?

So your solution only works if the cachemanager is enabled ?

Best, Stéphane

4

Hello. I apologize for google translate.
No, the cache manager was not activated, there was no check mark. But it still worked for me. Perhaps it was some kind of coincidence. And it worked in version 159. In version 160 it didn’t work. Problems with autostart squid at boot started after I restored the settings by installing ipfire, the squid stopped starting automatically. I looked at the logs and found there a message stating that the cache folders were not found, so I decided to specify the size of the cache on the HDD in the cache manager. The problem disappeared and the squid started to start itself every time.
Logs can be viewed here.
“cat /var/log/squid/cache.log”
fatal or error deserve attention.
In version 160, I did not restore the settings, but simply configured everything manually myself. I have two computers, so when a new version comes out, I don’t update it, but install it on the second computer and restore the settings. This way I always have a working server.
Let’s see what you have in cache.log.

5

Ok @flaorus,

Thank you for all these explanations !

I did not find much in the “cache.log” file, here is :

2021/12/05 11:36:22 kid1| Logfile: closing log stdio:/var/log/squid/access.log
2021/12/05 11:36:22 kid1| Open FD READ/WRITE 8 redirect_wrapper #1
2021/12/05 11:36:22 kid1| Open FD READ/WRITE 10 redirect_wrapper #2
2021/12/05 11:36:22 kid1| Open FD UNSTARTED 12 redirect_wrapper #3
2021/12/05 11:36:22 kid1| Open FD UNSTARTED 14 redirect_wrapper #4
2021/12/05 11:36:22 kid1| Open FD READ/WRITE 17 asnbl-helper.py #1
2021/12/05 11:36:22 kid1| Open FD UNSTARTED 19 asnbl-helper.py #2
2021/12/05 11:36:22 kid1| Squid Cache (Version 4.15): Exiting normally.
2021/12/05 11:36:22| Removing PID file (/var/run/squid.pid)
2021/12/05 11:36:22| Current Directory is /
2021/12/05 11:36:22| Current Directory is /
2021/12/05 11:39:09| Created PID file (/var/run/squid.pid)
2021/12/05 11:39:09| FATAL: Squid is already running: Found fresh instance PID file (/var/run/squid.pid) with PID 3649
exception location: Instance.cc(121) ThrowIfAlreadyRunningWith

…
…

2021/12/07 02:39:51| Current Directory is /
2021/12/07 02:39:51 kid1| Squid Cache (Version 4.15): Exiting normally.
2021/12/07 02:39:51| Removing PID file (/var/run/squid.pid)
2021/12/07 02:39:52| Current Directory is /
2021/12/07 02:39:52| Current Directory is /
2021/12/07 02:39:58| Created PID file (/var/run/squid.pid)
2021/12/07 02:39:58| FATAL: Squid is already running: Found fresh instance PID file (/var/run/squid.pid) with PID 491
exception location: Instance.cc(121) ThrowIfAlreadyRunningWith

Maybe this will mean something to someone…

6

yes, I also saw such an error in the logs, and the first thing that comes to mind is to add the initialization script and start the squid when the system boots, something like:
"if FATAL: Squid is already running then
remove /var/run/squid.pid
&& flush. "
but I haven’t figured out exactly where the init script is. I’m going to try changing something in the script at /etc/init.d/squid
Can someone from the developers tell me in the right direction I am looking for a solution?