RHEL 7 squid proxy run perfectly suddenly stop work
 

Hi All,

I am getting below error when start the proxy server on RHEL 7
squid is working fine from last 6 month suddenly the issue pop'sup
now i have update the entire OS and try to fix it but unable to achieve it
when i started the service after few seconds it is failed seems like this process create multiple process and after that it failed

i have empty the cache and access logs but getting the same issue

Please help me in fixing the issue



● squid.service - Squid caching proxy
Loaded: loaded (/usr/lib/systemd/system/squid.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2019-01-08 13:07:59 UTC; 1min 4s ago
Process: 28158 ExecStop=/usr/sbin/squid -k shutdown -f $SQUID_CONF (code=exited, status=1/FAILURE)
Process: 12280 ExecStart=/usr/sbin/squid $SQUID_OPTS -f $SQUID_CONF (code=exited, status=0/SUCCESS)
Process: 12275 ExecStartPre=/usr/libexec/squid/cache_swap.sh (code=exited, status=0/SUCCESS)
Main PID: 12283 (squid)
CGroup: /system.slice/squid.service
├─12283 /usr/sbin/squid -f /etc/squid/squid.conf
├─20265 (squid-1) -f /etc/squid/squid.conf
├─20266 (logfile-daemon) /var/log/squid/access.log
├─20267 (unlinkd)
├─20900 (squid-1) -f /etc/squid/squid.conf
└─20907 (squid-1) -f /etc/squid/squid.conf

squid[12283]: Squid Parent: (squid-1) process 13561 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 17410 started
squid[12283]: Squid Parent: (squid-1) process 17410 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 19411 started
squid[12283]: Squid Parent: (squid-1) process 19411 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 19671 started
squid[12283]: Squid Parent: (squid-1) process 19671 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 20133 started
squid[12283]: Squid Parent: (squid-1) process 20133 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 20265 started
[root@ ~]# service squid status
● squid.service - Squid caching proxy
Loaded: loaded (/usr/lib/systemd/system/squid.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2019-01-08 13:09:03 UTC; 504ms ago
Process: 21008 ExecStop=/usr/sbin/squid -k shutdown -f $SQUID_CONF (code=exited, status=1/FAILURE)
Process: 12280 ExecStart=/usr/sbin/squid $SQUID_OPTS -f $SQUID_CONF (code=exited, status=0/SUCCESS)
Process: 12275 ExecStartPre=/usr/libexec/squid/cache_swap.sh (code=exited, status=0/SUCCESS)
Main PID: 12283 (code=exited, status=1/FAILURE)

squid[12283]: Squid Parent: (squid-1) process 19671 started
squid[12283]: Squid Parent: (squid-1) process 19671 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 20133 started
squid[12283]: Squid Parent: (squid-1) process 20133 exited due to signal 6 with status 0
squid[12283]: Squid Parent: (squid-1) process 20265 started
systemd[1]: squid.service: main process exited, code=exited, status=1/FAILURE
squid[21008]: squid: ERROR: Could not send signal 15 to process 20265: (3) No such process
systemd[1]: squid.service: control process exited, code=exited status=1
systemd[1]: Unit squid.service entered failed state.
systemd[1]: squid.service failed.


squid -NCd10
2019/01/08 13:19:56| Set Current Directory to /var/spool/squid
2019/01/08 13:19:56| Starting Squid Cache version 3.5.20 for x86_64-redhat-linux-gnu...
2019/01/08 13:19:56| Service Name: squid
2019/01/08 13:19:56| Process ID 21140
2019/01/08 13:19:56| Process Roles: master worker
2019/01/08 13:19:56| With 4096 file descriptors available
2019/01/08 13:19:56| Initializing IP Cache...
2019/01/08 13:19:56| DNS Socket created at [::], FD 8
2019/01/08 13:19:56| DNS Socket created at 0.0.0.0, FD 9
2019/01/08 13:19:56| Adding domain us-west-2.compute.internal from /etc/resolv.conf
2019/01/08 13:19:56| Adding nameserver 172.31.0.2 from /etc/resolv.conf
2019/01/08 13:19:56| helperOpenServers: Starting 0/20 'squidGuard' processes
2019/01/08 13:19:56| helperOpenServers: No 'squidGuard' processes needed.
2019/01/08 13:19:56| Logfile: opening log daemon:/var/log/squid/access.log
2019/01/08 13:19:56| Logfile Daemon: opening log /var/log/squid/access.log
2019/01/08 13:19:56| Unlinkd pipe opened on FD 15
2019/01/08 13:19:56| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec
2019/01/08 13:19:56| Store logging disabled
2019/01/08 13:19:56| Swap maxSize 102400 + 262144 KB, estimated 28041 objects
2019/01/08 13:19:56| Target number of buckets: 1402
2019/01/08 13:19:56| Using 8192 Store buckets
2019/01/08 13:19:56| Max Mem size: 262144 KB
2019/01/08 13:19:56| Max Swap size: 102400 KB
2019/01/08 13:19:56| Rebuilding storage in /var/spool/squid (dirty log)
2019/01/08 13:19:56| Using Least Load store dir selection
2019/01/08 13:19:56| Set Current Directory to /var/spool/squid
2019/01/08 13:19:56| Finished loading MIME types and icons.
2019/01/08 13:19:56| HTCP Disabled.
2019/01/08 13:19:56| Squid plugin modules loaded: 0
2019/01/08 13:19:56| Adaptation support is off.
2019/01/08 13:19:56| Accepting HTTP Socket connections at local=[::]:3128 remote=[::] FD 18 flags=9
2019/01/08 13:19:56| Done reading /var/spool/squid swaplog (2 entries)
2019/01/08 13:19:56| Finished rebuilding storage from disk.
2019/01/08 13:19:56| 2 Entries scanned
2019/01/08 13:19:56| 0 Invalid entries.
2019/01/08 13:19:56| 0 With invalid flags.
2019/01/08 13:19:56| 2 Objects loaded.
2019/01/08 13:19:56| 0 Objects expired.
2019/01/08 13:19:56| 0 Objects cancelled.
2019/01/08 13:19:56| 0 Duplicate URLs purged.
2019/01/08 13:19:56| 0 Swapfile clashes avoided.
2019/01/08 13:19:56| Took 0.01 seconds (217.72 objects/sec).
2019/01/08 13:19:56| Beginning Validation Procedure
2019/01/08 13:19:56| Completed Validation Procedure
2019/01/08 13:19:56| Validated 2 Entries
2019/01/08 13:19:56| store_swap_size = 8.00 KB
2019/01/08 13:19:56| Starting new redirector helpers...
2019/01/08 13:19:56| helperOpenServers: Starting 1/20 'squidGuard' processes
2019/01/08 13:19:56| WARNING: redirector #Hlpr1 exited
2019/01/08 13:19:56| Too few redirector processes are running (need 1/20)
2019/01/08 13:19:56| Starting new helpers
2019/01/08 13:19:56| helperOpenServers: Starting 1/20 'squidGuard' processes
2019/01/08 13:19:56| ERROR: URL rewrite helper returned invalid result code. Wrong helper? {result=Unknown}
2019/01/08 13:19:56| WARNING: redirector #Hlpr2 exited
2019/01/08 13:19:56| Too few redirector processes are running (need 1/20)
2019/01/08 13:19:56| Starting new helpers
2019/01/08 13:19:56| helperOpenServers: Starting 1/20 'squidGuard' processes
2019/01/08 13:19:56| WARNING: redirector #Hlpr3 exited


squid -k parse
2019/01/08 13:24:44| Startup: Initializing Authentication Schemes ...
2019/01/08 13:24:44| Startup: Initialized Authentication Scheme 'basic'
2019/01/08 13:24:44| Startup: Initialized Authentication Scheme 'digest'
2019/01/08 13:24:44| Startup: Initialized Authentication Scheme 'negotiate'
2019/01/08 13:24:44| Startup: Initialized Authentication Scheme 'ntlm'
2019/01/08 13:24:44| Startup: Initialized Authentication.
2019/01/08 13:24:44| Processing Configuration File: /etc/squid/squid.conf (depth 0)
2019/01/08 13:24:44| Processing: acl localnet src 172.31.0.0/16
2019/01/08 13:24:44| Processing: acl AllowedSites dstdomain "/etc/squid/acls/allow_sites.txt"
2019/01/08 13:24:44| Processing: acl blocked_sites dstdomain "/etc/squid/acls/blocked_sites.txt"
2019/01/08 13:24:44| Processing: http_access allow localnet AllowedSites
2019/01/08 13:24:44| Processing: acl keyword_block url_regex "/etc/squid/acls/keyword_block.txt"
2019/01/08 13:24:44| Processing: http_access deny keyword_block
2019/01/08 13:24:44| Processing: acl ext_block url_regex "/etc/squid/acls/ext_block.txt"
2019/01/08 13:24:44| Processing: http_access deny ext_block
2019/01/08 13:24:44| Processing: http_access deny blocked_sites
2019/01/08 13:24:44| Processing: acl SSL_ports port 10022
2019/01/08 13:24:44| Processing: acl SSL_ports port 5432
2019/01/08 13:24:44| Processing: acl SSL_ports port 25
2019/01/08 13:24:44| Processing: acl SSL_ports port 443
2019/01/08 13:24:44| Processing: acl SSL_ports port 8080
2019/01/08 13:24:44| Processing: acl Safe_ports port 80 # http
2019/01/08 13:24:44| Processing: acl Safe_ports port 21 # ftp
2019/01/08 13:24:44| Processing: acl Safe_ports port 443 # https
2019/01/08 13:24:44| Processing: acl Safe_ports port 70 # gopher
2019/01/08 13:24:44| Processing: acl Safe_ports port 210 # wais
2019/01/08 13:24:44| Processing: acl Safe_ports port 1025-65535 # unregistered ports
2019/01/08 13:24:44| Processing: acl Safe_ports port 280 # http-mgmt
2019/01/08 13:24:44| Processing: acl Safe_ports port 488 # gss-http
2019/01/08 13:24:44| Processing: acl Safe_ports port 591 # filemaker
2019/01/08 13:24:44| Processing: acl Safe_ports port 777 # multiling http
2019/01/08 13:24:44| Processing: acl CONNECT method CONNECT
2019/01/08 13:24:44| Processing: url_rewrite_program /usr/bin/squidGuard
2019/01/08 13:24:44| Processing: http_access deny !Safe_ports
2019/01/08 13:24:44| Processing: http_access deny CONNECT !SSL_ports
2019/01/08 13:24:44| Processing: http_access allow localhost manager
2019/01/08 13:24:44| Processing: http_access deny manager
2019/01/08 13:24:44| Processing: http_access allow localnet
2019/01/08 13:24:44| Processing: http_access allow localhost
2019/01/08 13:24:44| Processing: http_access deny all
2019/01/08 13:24:44| Processing: http_port 3128
2019/01/08 13:24:44| Processing: cache_dir ufs /var/spool/squid 100 16 256
2019/01/08 13:24:44| Processing: coredump_dir /var/spool/squid
2019/01/08 13:24:44| Processing: refresh_pattern ^ftp: 1440 20% 10080
2019/01/08 13:24:44| Processing: refresh_pattern ^gopher: 1440 0% 1440
2019/01/08 13:24:44| Processing: refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
2019/01/08 13:24:44| Processing: refresh_pattern . 0 20% 4320
2019/01/08 13:24:44| Initializing https proxy context
[root@ ~]#

Put things like this in CODE tags...your post is almost impossible to read, but as you've been here eight years now, you should know this. That said, your post is hard to make out. You say RHEL 7, and that everything was working fine, when 'suddenly' it stopped. Things don't work like that; what did you change/update to make it 'suddenly' stop? You say you 'update the entire OS'....does that mean you reloaded from scratch, updated from the online repositories, updated Squid by itself?? What???

SOMETHING changed...what was it? How did you start squid? Because without seeing your config file (and if you post it, again, put it in CODE tags), the pieces of logs you've posted doesn't give us many clues. The "signal 6" message typically indicates a problem with the cache directory, either location or permissions. Have you checked that?

Apologies for that!!!! Nothing had been changed once I know that squid is not working. Then only I am trying to fix it. I am assuming that this could be any bug as per number of articles I have searched on internet. So I have update the OS from yum. Regarding the cache directory
It is been their.

As per the redhat this is a bug in RHEL 6 which is fix in squid34.but I am facing this issue in RHEL7

Sorry, but you're not making sense here.

You say "nothing had been changed once I know that squid is not working"...yet you said "suddenly the issue pop'sup now i have update the entire OS", indicating that you HAVE done something (again, either reloading the OS or updating it). Which is it?? Either you DID change something or you didn't. And again, things 'suddenly' don't stop...they stop because **SOMETHING HAS CHANGED** on the system. We know this because:

• It WAS working for six months
• It STOPPED working

So what changed? Again, check the cache directory (and deleting it/re-creating it would be fairly easy to do), and check the permissions.
[QUOTE]As per the redhat this is a bug in RHEL 6 which is fix in squid34.but I am facing this issue in RHEL7
So then have you contacted Red Hat support?? Have you applied the RHEL bug fixes, since you're paying for Red Hat?

Hi

This proxy is working fine from last 6 month. Now yesterday when the browser are not open any website then i come to know that there is problem in the squid.Therefore i have restart the service of the squid during that time i notice that after starting the squid service when i check the status of the squid service below issue shown and service went down. hence i have check the configuration "squid -k parse" then check the cache and access logs in the /var/log/squid and null those file and then restart the services but it shown the same result.

Therefore i am searching on the internet if any once have face same issue. so few blogs or articles suggested that this could be the bug of the package so try with the updates. As my server didn't update from long time therefore i have update the full OS. But after update the issue didn't fixed

Below are error when check the status of squid service

Now regarding the REDHAT i have checked one of the solution of the redhat in which they mention same issue in RHEL 6 and that had been fix on squid34 But i am using RHEL7 and having different version of the proxy

So again: WHAT CHANGED YESTERDAY???
AGAIN: What do you mean you 'have update the full OS'?? Again: did you totally reload your whole system, or did you just perform an update?? And why didn't you keep your RHEL system up to date? Should run automatically.
...and unless your system is paid for and registered with Red Hat, you have *NOT* received any of the bugfixes for other parts of the system. You're still not being clear what you mean by 'update the full OS', despite being asked several times now.

AGAIN: **HAVE YOU CHECKED THE CACHE DIRECTORY**????? Again, this is for permissions/size/location/whatever. Something changed, and based on the error that's where I'd start. And AGAIN: have you contacted Red Hat support?? Are you PAYING for RHEL???? The article you linked to says "SOLUTION IN PROGRESS"...meaning OUTSTANDING, and has moved forward. Did you read the rest of that article, that describes the workaround?


You just keep restating "It just stopped yesterday, and I did a full update of the OS", but you don't answer any of the questions you've been asked so far, acknowledge the advice given about checking the cache location, or tell us what Red Hat told you. Asking the same thing over and over won't get you anything new, and if you'd like help, then you need to participate in the conversation, answer questions, and clarify things when needed. We are now 7 posts in, and we know NOTHING past what you first posted, despite you being asked several times.

1) when i come to know the issue come up. i checked the logs of the squid but unable to found the reason of issue then i checked the logs of the start and stop of the squid service, which give the error of then i did google to figure out the reason for this issue and get few suggestion on blogs and article. so few suggestion ask to update the squid packages as this is stand alone server for squid and didn't updated from long period. Therefore i did "yum update" and assuming that this will fix the issue but that didn't work

Then i did to empty the logs and restart the service but it is also not working

then i increase the file descriptor



these all changes had been done after the issue pop's up... I think this will makes the picture clear to you.

Nope, because you **STILL ARE NOT ANSWERING THE QUESTIONS YOU WERE ASKED**. And you are STILL ignoring the advice you were given, about checking the cache directory.

If you won't answer questions that you've now been asked three times now, there is no point in posting. Good luck; I'm done.

i am not ignoring the below path for the squid but this is not causing the issue.. i know i will figure out this issue soon.


sorry for irritating on this issue.I am trying my best to fix it.

Thanks
dk

Are you just not paying attention??? What you've shown are the LOG FILES...which is NOT what's been asked/suggested, nor what a very brief Google search indicates might be a cause.

And what about all the OTHER QUESTIONS that you still haven't answered????

**AGAIN** You need to check the CACHE DIRECTORY. Not the log files; not the log directory...the CACHE DIRECTORY.
**AGAIN** Check the permissions; delete it and re-create it if needed. Try another location; check disk space. Perform BASIC TROUBLESHOOTING, and ANSWER THE QUESTIONS YOU HAVE BEEN ASKED FOUR TIMES NOW.

we need few more information please post output of following list of commands

1) cat /var/log/squid/ squid error log
2) cat /etc/squid/squid.conf
3)cat /etc/squidgaurd/squidguard.conf

df-k

ip a

status squidgaurd

so seeing this can assist you to fix the issue , as it seems your squid.conf configuration is exited , due to network or config miss match

Thanks for the reply. i have fixed it already on Friday. Now i am sharing, how i have resolve it.


1) When i have check the logs of the Squid i am unable see any issue. But when i have restarted the service of the squid then i come to know that after few second the service of the squid goes fail. Now on Friday i all so checked /varlog/message and able to see there is squid Guard logs and this create issue then i try to understand why this happening. hence i have disable the and run again the squid this time squid responded perfectly then i checked the squidGuard configuration but unable to figure out the issue then i recreate the configuration file and compile it

SquidGuard Error found in message logs

Squid Configuration


Now all works fine.

So when you were asked at the beginning to check the log files...you just didnt??? The "signal 6" indicates a cache directory problem. The Squidguard log (which you didn't check or mention), indicates a known bug/error.

Next time you post, answer questions and provide details when asked...great that its working and you shared the solution, but it would have been fixed last week had you provided details.

Hi

Yes i have checked the logs on the concerned directory But during that time unable to figure out it. then i tried to check the logs in message logs with "squid*" and assuming that their might be something.... and lucky the error log of Squid Guard found.

Your intention/Guidance is correct. But i am not aware of the Squid guard error logs will be in the message log


Regards
DK