Search squid archive

Bad opcode: 112 from [6661:6c73:6522:2061:7420:6c69:6e65:2036]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Bad opcode: 112 from [6661:6c73:6522:2061:7420:6c69:6e65:2036]
From: "David Touzeau" <david@xxxxxxxxxxxxxx>
Date: Sat, 19 Jan 2013 19:20:52 +0100
Importance: Normal

Dear

I’m using squid 3.2.6 with 4 workers on i386
After restarting squid all kids write the

Bad opcode: 112 from [6661:6c73:6522:2061:7420:6c69:6e65:2036]

event

I’m unable to surf trough squid.
processes still in memory, cache mgr:info give to me a good status

What does it means ?

Follow-Ups:
- Re: Bad opcode: 112 from [6661:6c73:6522:2061:7420:6c69:6e65:2036]
  - From: Amos Jeffries

Prev by Date: Re: Re: Re: Help with Kerberos Configuration
Next by Date: Re: can squid follow 301/302 without passing the 301/302 back to the client?
Previous by thread: Squid Proxy Server Setup & Configuration
Next by thread: Re: Bad opcode: 112 from [6661:6c73:6522:2061:7420:6c69:6e65:2036]
Index(es):
- Date
- Thread

[Index of Archives] [Linux Audio Users] [Samba] [Big List of Linux Books] [Linux USB] [Yosemite News]

Powered by Linux