Zeller, Jan wrote:
hi Amos, dear list,
the problem
It seems to be a fread() issue between Squid and x86_64. Disappears on
i386/i686.
Maybe *BSD specific as well, but there are a few reports without OS info
fuzzing my info there.
I plan on spending more time over the weekend adding good tracing info to
find it.
Amos
I'm getting that too on
FreeBSD a.ujena.net 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24
00:14:3
5 UTC 2009
root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC
amd64
bounced back to 15 - doesn't seem to crash like 17
17:
2009/07/30 06:26:21| assertion failed: http.cc:738: "!eof"
2009/07/30 07:01:37| assertion failed: http.cc:738: "!eof"
2009/07/30 07:31:11| assertion failed: http.cc:738: "!eof"
2009/07/30 07:34:21| assertion failed: http.cc:738: "!eof"
2009/07/30 07:34:54| assertion failed: http.cc:738: "!eof"
2009/07/30 07:38:32| assertion failed: http.cc:738: "!eof"
2009/07/30 08:03:21| assertion failed: http.cc:738: "!eof"
2009/07/30 08:34:27| assertion failed: http.cc:738: "!eof"
2009/07/30 08:36:58| assertion failed: http.cc:738: "!eof"
2009/07/30 08:37:32| assertion failed: http.cc:738: "!eof"
2009/07/30 08:44:49| assertion failed: http.cc:738: "!eof"
2009/07/30 08:47:02| assertion failed: http.cc:738: "!eof"
2009/07/30 08:57:41| assertion failed: http.cc:738: "!eof"
2009/07/30 09:06:08| assertion failed: http.cc:738: "!eof"
2009/07/30 09:10:26| assertion failed: http.cc:738: "!eof"
2009/07/30 09:16:20| assertion failed: http.cc:738: "!eof"
2009/07/30 09:18:14| assertion failed: http.cc:738: "!eof"
2009/07/30 09:24:53| assertion failed: http.cc:738: "!eof"
2009/07/30 09:26:39| assertion failed: http.cc:738: "!eof"
2009/07/30 09:28:00| assertion failed: http.cc:738: "!eof"
2009/07/30 10:12:42| assertion failed: http.cc:738: "!eof"
2009/07/30 10:20:23| assertion failed: http.cc:738: "!eof"
2009/07/30 10:41:26| assertion failed: http.cc:738: "!eof"
2009/07/30 10:49:26| assertion failed: http.cc:738: "!eof"
2009/07/30 10:54:05| assertion failed: http.cc:738: "!eof"
2009/07/30 11:17:02| assertion failed: http.cc:738: "!eof"
2009/07/30 11:32:34| assertion failed: http.cc:738: "!eof"
2009/07/30 11:48:03| assertion failed: http.cc:738: "!eof"
2009/07/30 11:48:38| assertion failed: http.cc:738: "!eof"
2009/07/30 11:51:24| assertion failed: http.cc:738: "!eof"
2009/07/30 12:16:29| assertion failed: http.cc:738: "!eof"
2009/07/30 12:20:50| assertion failed: http.cc:738: "!eof"
2009/07/30 12:36:55| assertion failed: http.cc:738: "!eof"
2009/07/30 12:50:45| assertion failed: http.cc:738: "!eof"
2009/07/30 12:57:19| assertion failed: http.cc:738: "!eof"
2009/07/30 13:04:00| assertion failed: http.cc:738: "!eof"
2009/07/30 13:09:29| assertion failed: http.cc:738: "!eof"
2009/07/30 13:10:32| assertion failed: http.cc:738: "!eof"
2009/07/30 13:18:39| assertion failed: http.cc:738: "!eof"
2009/07/30 13:18:53| assertion failed: http.cc:738: "!eof"
2009/07/30 13:40:04| assertion failed: http.cc:738: "!eof"
2009/07/30 13:47:31| assertion failed: http.cc:738: "!eof"
2009/07/30 13:51:05| assertion failed: http.cc:738: "!eof"
2009/07/30 13:51:23| assertion failed: http.cc:738: "!eof"
2009/07/30 13:53:10| assertion failed: http.cc:738: "!eof"
2009/07/30 13:59:32| assertion failed: http.cc:738: "!eof"
2009/07/30 14:01:15| assertion failed: http.cc:738: "!eof"
2009/07/30 14:02:27| assertion failed: http.cc:738: "!eof"
2009/07/30 14:03:38| assertion failed: http.cc:738: "!eof"
2009/07/30 14:04:01| assertion failed: http.cc:738: "!eof"
2009/07/30 14:25:06| assertion failed: http.cc:738: "!eof"
2009/07/30 14:57:59| assertion failed: http.cc:738: "!eof"
2009/07/30 15:07:41| assertion failed: http.cc:738: "!eof"
2009/07/30 15:15:01| assertion failed: http.cc:738: "!eof"
2009/07/30 15:17:09| assertion failed: http.cc:738: "!eof"
2009/07/30 15:17:49| assertion failed: http.cc:738: "!eof"
it always restarts promptly but user gets 1/2 images and sometimes error
page depending on when it crashes. no good for production... ;-) my
experimentation -> looks like it crashes when fetching pages full of
images, but the bug reports show a user making a single request and
getting the error.
also, i didn't notice any problems when the cache was mostly empty,
crashing seemed to start happening after awhile.
tried #17-7/30 and didn't help, went to #16 and wouldn't build happily
so i'm using #15 at the moment, seems to work so far. well hasn't dumped
core yet. (sorry, lame i know - i used to do things with and hack squid
years ago, several years ago - back in the old days - but it's been a
long time and today was the day to get back into it i guess.)
if you need a 'fix tester' over the weekend, etc. lemme know. i'm
running reverse for a moderate-traffic site.
i browsed through the code tonight but it's late and i'm tired.
take care,
waitman
