RE: [squid-users] squid dead but subsys locked

No, it's giving the error below for first status check;

        [root@squid subsys]# service squid start
        Starting /usr/local/squid/sbin/squid: [ OK ]
        [root@squid subsys]# service squid status
        squid (pid 7862) is running...
        squid: ERROR: Could not send signal 0 to process 7908: (3) No such
process

If I repeat status check, it's giving a different one;

        [root@squid subsys]# service squid status
        squid dead but subsys locked
        squid: ERROR: Could not send signal 0 to process 8060: (3) No such
process

I tried to remove the cache directories, but it also didn't work..

Here is a part of cache.log file;

2004/07/05 17:13:55| Starting Squid Cache version 2.5.STABLE5 for
i686-pc-linux-gnu...
2004/07/05 17:13:55| Process ID 8060
2004/07/05 17:13:55| With 1024 file descriptors available
2004/07/05 17:13:55| DNS Socket created at 0.0.0.0, port 32769, FD 4
2004/07/05 17:13:55| Adding nameserver X.X.X.X1 from squid.conf
2004/07/05 17:13:55| Adding nameserver X.X.X.X12 from squid.conf
2004/07/05 17:13:55| Adding nameserver X.X.X.X3 from squid.conf
2004/07/05 17:13:55| helperOpenServers: Starting 5 'squidGuard' processes
2004/07/05 17:13:55| helperStatefulOpenServers: Starting 30 'ntlm_auth'
processes
2004/07/05 17:13:56| helperOpenServers: Starting 5 'msnt_auth' processes
2004/07/05 17:13:56| User-Agent logging is disabled.
2004/07/05 17:13:56| Referer logging is disabled.
2004/07/05 17:13:56| Unlinkd pipe opened on FD 49
2004/07/05 17:13:56| Swap maxSize 102400 KB, estimated 7876 objects
2004/07/05 17:13:56| Target number of buckets: 393
2004/07/05 17:13:56| Using 8192 Store buckets
2004/07/05 17:13:56| Max Mem size: 8192 KB
2004/07/05 17:13:56| Max Swap size: 102400 KB
2004/07/05 17:13:56| Rebuilding storage in /usr/local/squid/var/cache
(DIRTY)
2004/07/05 17:13:56| Using Least Load store dir selection
2004/07/05 17:13:56| Set Current Directory to /usr/local/squid/var/cache
2004/07/05 17:13:56| Loaded Icons.
2004/07/05 17:13:56| Accepting HTTP connections at 0.0.0.0, port 3128, FD
51.
2004/07/05 17:13:56| Accepting ICP messages at 0.0.0.0, port 3130, FD 52.
2004/07/05 17:13:56| Accepting SNMP messages on port 3401, FD 53.
2004/07/05 17:13:56| WCCP Disabled.
2004/07/05 17:13:56| Ready to serve requests.
2004/07/05 17:13:56| Store rebuilding is 43.5% complete
fgets() failed! dying..... errno=0 (Success)
fgets() failed! dying..... errno=0 (Success)

-----Original Message-----
From: Elsen Marc [mailto:elsen@imec.be]
Sent: Monday, July 05, 2004 5:15 PM
To: IRFAN BUYURAN (EBI Bsk.Sistem Prog.); squid-users@squid-cache.org
Subject: RE: [squid-users] squid dead but subsys locked

 
>
> Thank you for your response.
>
> /var/lock/subsys/squid was existing, I removed "squid" but it didn't
> work.
> Squid is still down.
 
 Is it still giving the same error when trying to start squid, after
removing this file ?

M.
===================================================================
Bu e-mail mesaji ve ekleri, isimleri yazili alicilar disindaki kisilere
aciklanmamasi, dagitilmamasi ve iletilmemesi gereken kisiye ozel ve gizli
bilgiler icerebilir. Mesajin muhatabi degilseniz lutfen gonderici ile
irtibat kurunuz, mesaj ve eklerini siliniz. E-mail sistemlerinin tasidigi
guvenlik risklerinden dolayi, mesajlarin gizlilikleri ve butunlukleri
bozulabilir, mesaj virus icerebilir. Bilinen viruslere karsi kontrolleri
yapilmis olarak yollanan mesajin sisteminizde yaratabilecegi olasi
zararlardan Sirketimiz (T.H.Y. A.O.) sorumlu tutulamaz.
This email and its attachments may contain private and confidential
information intended for the use of the addressee only, which should not be
announced, copied or forwarded. If you are not the intended recipient,
please contact the sender, delete the message and its attachments. Due to
security risks of email systems, the confidentiality and integrity of the
message may be damaged, the message may contain viruses. This message is
scanned for known viruses and our Company (Turkish Airlines Inc.) will not
be liable for possible system damages caused by the message.
Received on Mon Jul 05 2004 - 08:24:50 MDT