latest squid package seems to be corrupting itself?
-
so, I'm using the most updated squid version, just updated it, and this also seems to have begun happening for me randomly (have had squid turned off for 3 months, tried to tinker with it out of a fit of depression, only to find this seemingly bug style end result across 5 different reboots, and even a full nuking/cleaning of squid per the netgate documents to rid myself of the seemingly bug behaviour only to recreate it all over again)
anyways, so I'm trying to get squid fixed, got it fixed after a full clean of it, only to make the problem come back again, meaning I reproduced it apparently, the problem being, that even when getting squid fully reconfigured, simply telling it to use custom MITM mode seems to corrupt squid entirely somehow, in which that after turning MITM mode on, even without setting it to do anything and leaving all the custom configs blank/empty, then turning it off again and trying to revert back to splice whitelist bump otherwise makes squid unable to restart and run again, nothing outside of simply telling it to use custom, then saving, and then going back to bump/splice default behavior breaks it entirely.
I'm at a total loss for whats going on here, and I have confirmed this issue with 4.4.35 and 4.4.36, I figured updating it after nuking all of its data/configs would fix this and thought I messed something up, but even a fully clean squid installation after nuking all of its remnants, still makes it happen for me...
trying to edit my post to add the config files contents and the site keeps yelling saying my post/edit was blocked for spam...I want to scream today so very much.
-
almost a week later and still no replies? is there something else I need to add here to get someones help? I mean, I know my posts tend to take a while to get someones response, but not a week usually...
-
@high_voltage said in latest squid package seems to be corrupting itself?:
squid unable to restart and run again
And what does the log say - it squid is not starting there should/would be something in the log that it could not start?
-
@johnpoz said in latest squid package seems to be corrupting itself?:
@high_voltage said in latest squid package seems to be corrupting itself?:
squid unable to restart and run again
And what does the log say - it squid is not starting there should/would be something in the log that it could not start?
which log file do I need to view, and I'll post whats up in the log file (I do not actually know off hand what log file you need to know the contents of)
-
It should be in the normal system general log..
You should see it trying to start, and then some error if it can not start. I do not currently have it installed because I have zero use for it.
Have you gone over
https://docs.netgate.com/pfsense/en/latest/troubleshooting/squid.html -
@johnpoz said in latest squid package seems to be corrupting itself?:
It should be in the normal system general log..
You should see it trying to start, and then some error if it can not start. I do not currently have it installed because I have zero use for it.
Have you gone over
https://pfsense-docs.readthedocs.io/en/latest/cache-proxy/squid-troubleshooting.htmlyep, 4 times, complete with the total/complete removal instructions each time, it still does this as soon as I try and turn on custom mode for ssl interception, regardless of turning it back to splice whitelist/bump other, just turning it on ONCE to custom breaks it this way. in the process of trying to find the log file info on it at all, but so far, nothing at all about squid to be seen what so ever.
EDIT: found squids attempt at loading, it just repeats this couple chunks of text multiple times.
Jan 25 23:10:44 voltwall check_reload_status: Reloading filter
Jan 25 23:10:46 voltwall php-fpm[73585]: /rc.filter_configure_sync: [squid] Installed but not started. Not installing 'nat' rules.
Jan 25 23:10:46 voltwall php-fpm[73585]: /rc.filter_configure_sync: [squid] Installed but not started. Not installing 'pfearly' rules.
Jan 25 23:10:46 voltwall php-fpm[73585]: /rc.filter_configure_sync: [squid] Installed but not started. Not installing 'filter' rules.SECOND EDIT: .............some days I am a forgetful moron....I forgot pfsense has an actual system log viewer, and that page just freaking told me what the problem is =-=;
Jan 25 23:47:31 squid FATAL: Bungled /usr/local/etc/squid/squid.conf line 283: range_offset_limit -1;
ohay reason squid keeps dieing on me......... facepalms
mmmmmmmhmm...fixing that line gets it to restart...... SOME DAYS I SWEAR...I feel like I dont have a brain lmao
-
@johnpoz thank you, I am a derp, but you helped me figure out what I was doing wrong.