Re: [squid-users] Re: squid 3.2.0.5 even slower than squid 3.1 and doesn't work with workers >1

On 22/03/11 18:22, david_at_lang.hm wrote:
> On Tue, 22 Mar 2011, Amos Jeffries wrote:
>
>> On Mon, 21 Mar 2011 17:10:23 -0700 (PDT), david_at_lang.hm wrote:
>>> On Mon, 21 Mar 2011, david_at_lang.hm wrote:
>>>
>>>> resending without the attachments since this doesn't appear to have
>>>> gotten through to the list. if this gets through I'll reply with them.
>>>
>>> ok, apparently the list doesn't like attachments
>>>
>>
>> Yes this is a Q&A help list.
>> The dev list where this should be going on accepts attachments.
>
> Ok, I was put off by the 'submit a resume and apply' wording for the dev
> list (since I don't _plan_ on doing development work, I'm just trying to
> use it)
>
>>
>>> here is workers 1 (starts and works)
>>>
>>> Mar 21 23:14:11 gromit1-p squid[12080]: Squid Parent: child process
>>> 12082 started
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Starting Squid Cache version
>>> 3.2.0.5 for x86_64-unknown-linux-gnu...
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Process ID 12082
>>> Mar 21 23:14:11 gromit1-p squid[12082]: With 65535 file descriptors
>>> available
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Initializing IP Cache...
>>> Mar 21 23:14:11 gromit1-p squid[12082]: DNS Socket created at
>>> 0.0.0.0, FD 8
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Adding domain diginsite.com
>>> from /etc/resolv.conf
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Warning: Could not find any
>>> nameservers. Trying to use localhost
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Please check your
>>> /etc/resolv.conf file
>>> Mar 21 23:14:11 gromit1-p squid[12082]: or use the 'dns_nameservers'
>>> option in squid.conf.
>>
>> The system resolver resolv.conf appears broken.
>
> this is in use in an internal environment, there is no DNS server to use.

K, no problem then.

>
>>> Mar 21 23:14:11 gromit1-p squid[12082]: errorpage.cc(302)
>>> errorTryLoadText: '/etc/squid/errorpage.css': (2) No such file or
>>> directory
>>
>> 3.1+ configure the error page display with this CSS file.
>
> this is mostly being accessed by applications, so I don't care what the
> error page looks like, the simpler the better (if the full error was
> logged, I wouldn't care about the error page at all)

K. Then make it an empty file.

>
>> <snip>
>>> Mar 21 23:14:11 gromit1-p squid[12082]: mimeLoadIconFile:
>>> /usr/squid/var/www/squid/icons/anthony-image.gif: (2) No such file or
>>> directory
>>>
>>
>> In 3.2 the icons have changed. A bug in 3.2.0.5 makes the mime
>> configuration file not get updated. There should be a
>> /etc/squid/mime.conf.default with the new icon configuration that
>> needs to be moved over the mime.conf from 3.1 and older. Or the
>> src/mime.conf.default can be extracted manually and used.
>
> Ok, again, I don't care about icons and similar eye candy, they will
> never be called.

Then just replace the old file with the 3.2 one. Problem fixed.

>
>> <snip>
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Loaded Icons.
>>> Mar 21 23:14:11 gromit1-p squid[12082]: HTCP Disabled.
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Configuring Parent
>>> 192.168.106.27/8000/0
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Configuring Parent
>>> 192.168.106.12/8000/0
>>> Mar 21 23:14:11 gromit1-p squid[12082]: Ready to serve requests.
>>> Mar 21 23:14:11 gromit1-p squid[12082]: AcceptingHTTP Socket
>>> connections at FD 13 on 0.0.0.0:8000
>>> Mar 21 23:14:12 gromit1-p squid[12082]: storeLateRelease: released 0
>>> objects
>>
>> Hmm, ten second gap. Could be the icons killing this, or something
>> else. It looks like a normal "-k shutdown" or SIGHUP was received by
>> the master process.
>
> yes, this was a normal shutdown after it started.
>

Great. Okay. You have the non-working startup trace then?

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.11
   Beta testers wanted for 3.2.0.5