satendrajain
asked on
red hat linux, squid, 2.3, ERROR: Could not send signal 0 to process 5229: (3) No such process
i have configured squid sometime back and it was runing perfectly but now its not working . i really dont know the cause of all the errors.
if i run the command #service squid status ,i get the error:
squid dead but subsys locked
squid: ERROR: Could not send signal 0 to process 5229: (3) No such process
if i run the command #service squid restart , i get the error:
Stopping /etc/squid/sbin/squid: squid: ERROR: Could not send signal 0 to process 5229: (3) No such process
if i run the command #service squid status ,i get the error:
squid dead but subsys locked
squid: ERROR: Could not send signal 0 to process 5229: (3) No such process
if i run the command #service squid restart , i get the error:
Stopping /etc/squid/sbin/squid: squid: ERROR: Could not send signal 0 to process 5229: (3) No such process
ok, your squid is offline nad never starts.... what happend when you do a service squid start ??
Check your /var/log/messages file, and if you have a separate Log file for squid, that file too after you have rebooted the PC. It should tell you whether squid has started, and if not, there should be error messages which tell you what the reason could.
Often the reason for squid not starting is that the disk is full, so check for the amount of empty space on your PC.
Often the reason for squid not starting is that the disk is full, so check for the amount of empty space on your PC.
squid -k check
or
Also try starting Squid interactively to see if any errors is seen
/path/to/sbin/squid -DNYCd3
or
Also try starting Squid interactively to see if any errors is seen
/path/to/sbin/squid -DNYCd3
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
then check for squid status
service squid status
if you get a amessage like this:
squid dead but subsys locked
then go to /var/lock/subsys
and remove 0 byte squid file there too.
Then it should run without a problem..
service squid status
if you get a amessage like this:
squid dead but subsys locked
then go to /var/lock/subsys
and remove 0 byte squid file there too.
Then it should run without a problem..
ASKER
@ KeremE:
I did a lot of R&D which include some from the above mentioned also and somehow am able to start the squid service, but can anybody tell me what cud be the reason behind that, why my squid service is failing quite often. I am running squid squid-2.5.STABLE1-2 on linux9.
I did a lot of R&D which include some from the above mentioned also and somehow am able to start the squid service, but can anybody tell me what cud be the reason behind that, why my squid service is failing quite often. I am running squid squid-2.5.STABLE1-2 on linux9.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
As rindi indicated. To see the files there indicates although you start your service succcessfully at some point the squid is crashed without properly removing the service created files. You need to inspect the reasons behind.
The best starting point will be to initialize your cache with "squid -z" command. Then you might want to modify your startup script and add -X (enable ful debug to it):
- edit the file /etc/init.d/squid
- locate this variable here:
SQUID_OPTS=${SQUID_OPTS:-" -D"}
- modify the string such as:
SQUID_OPTS=${SQUID_OPTS:-" -D -X"}
- Restart the service
service squid restart
Then it will create lots of debugigng information in /var/log/squid. Watch the files to see the reason.
Don't forget to restore the switch once you've got results becasue it will take op sso much disk space, although lo rotate indexes and comresesses them.
As rindi indicated. To see the files there indicates although you start your service succcessfully at some point the squid is crashed without properly removing the service created files. You need to inspect the reasons behind.
The best starting point will be to initialize your cache with "squid -z" command. Then you might want to modify your startup script and add -X (enable ful debug to it):
- edit the file /etc/init.d/squid
- locate this variable here:
SQUID_OPTS=${SQUID_OPTS:-"
- modify the string such as:
SQUID_OPTS=${SQUID_OPTS:-"
- Restart the service
service squid restart
Then it will create lots of debugigng information in /var/log/squid. Watch the files to see the reason.
Don't forget to restore the switch once you've got results becasue it will take op sso much disk space, although lo rotate indexes and comresesses them.
Forced accept.
Computer101
EE Admin
Computer101
EE Admin
check squid.log access.log and cache.log size they maybe over 1GB, delete them and restart squid.