[squid-users] log message oddities -- what do they mean? how to interpret?

Most recent info as at the bottom, but am curious about things I ran
into....

Still have 1 unknown error and no estimate on load handling ability,
But think I will send this off now.

Hopefully others will be able to give it a gander and offer insights....

Thanks!

Linda...

I recently upgraded to 3.2.0.9

(had been at 3.HEAD some time back, but then upgraded my server,
and squid3.1.11 got installed).

With it, I got messages like:

Jul 13 22:28:49 Ishtar squid[10383]: /var/cache/squid/03/29/00003A79
squid[10383]: DiskThreadsDiskFile::openDone: (2) No such file or directory
squid[10383]: /var/cache/squid/03/29/00003A7B
squid[10383]: DiskThreadsDiskFile::openDone: (2) No such file or directory

But looking in those dirs. I can see those files....so what file doesn't
exist?
They are owned by user/group 'squid.squid', w/perms 640.
-----

NOTE, the above message are ***real*** important personally, as I'm
not getting them with my new build and using aufs.

Seems like their build was using diskthreads.

I don't know if I wanted to use disk threads. (do I?)

Isn't AIO faster or would disk threads be?
Of course, aio doesn't seem to give errors like the ones above! ;-)

But, that might be fixable if they are faster....

Anyway -- (just noticed that log message above...as was looking at
current long
messages with 3.2.0.9... am getting many more messages/ much more
verbosity.
I guess my default 'build' settings are for a bit more 'noise'? (or I
don't have
something config'ed correctly in my squid.conf for the new 3.2).

But what do these mean (and why am I seeing them in the log if they are
normal
-- they look like PROXY CONNECT requests(?), but that's just a guess...)

First set of weird messages (not getting these now that I have log
settings set correctly
in squid.conf (just had filename)...am using daemon now).

    squid[27996]: forward.cc(96) FwdState: Forwarding client request
    local=192.168.3.1:8080 \
         remote=192.168.3.140:51873 FD 13 flags=1,\
        
    url=http://technet.microsoft.com/en-us/library/dd349396(v=WS.10).aspx
    squid[27996]: IcmpSquid.cc(156) Recv: recv: (111) Connection refused
    squid[27996]: IcmpSquid.cc(282) Close: Closing Pinger socket on FD 22
    squid[27996]: storeLateRelease: released 0 objects
    squid[27996]: forward.cc(96) FwdState: Forwarding client request
    local=192.168.3.1:8080 \
         remote=192.168.3.140:51873 FD 13 flags=1, \
        
    url=http://i3.technet.microsoft.com/Hash/489f173fe4c898064bb69f941d1e4ca3.css

.... and many other Forwarding notes in log...

This looks like what I was seeing with 3.1 as well: lots of fails...
with SIG 6's

    squid[957]: assertion failed: comm.cc:1904:
    "!commHasHalfClosedMonitor(fd)"
    squid[7072]: Squid Parent: child process 957 exited due to signal 6
    with status 0
    squid[7072]: Squid Parent: child process 6023 started
    squid[6023]: Starting Squid Cache version 3.2.0.9 for
    x86_64-unknown-linux-gnu...
    squid[6023]: Process ID 6023
    squid[6023]: With 16384 file descriptors available
    squid[6023]: Initializing IP Cache...

...and restart...

   So What's a !commHasHalfClosedMonitor(fd)...and why does it cause death?

----
(before I sent this.....going over and over config and 
squid.conf/configure/filesystem!/
addressings and have noticed some things and tried fixes...:
filesystem:  looks like both the suse version (and mine, I copied theirs 
as closely as
possible, as wanted it to use the same file locations -- presuming that 
they had set them
up properly....*cough*)...
/var/squid was (is) set for the comm shared state dir, but it didn't 
exist on my machine.
---
just created it and will see if that fixes that...but now see:
         assertion failed: mem.cc:511: "MemPools[t]"
---
Not sure why I saw this, but I twiddled some memory settings, though
I'm not really using any delay pools...hmmm...
Only error on the last restart was :
     commBind: Cannot bind socket FD 18 to [::]: (13) Permission denied
Impact?  What won't work?  how do I shut it off if I don't need it?
Well it's been up for a while ... but to see if it handles load or I 
keep getting
'proxy refusing connections' (NOT GOOD with 1 user!!!)....