Squid aufs crashes under 10.0

[Pavel Timofeev]

Hi!
There is a problem with squid under FreeBSD10.0.
Squid crashes immediately if storage type is set to aufs.
It goes down during read of config file.

No problem with diskd. No problem with aufs under FreeBSD9.2.

Someone thinks that it's related to clang which is default compiler on
FreeBSD 10.0.

I recompiled www/squid33 with DEBUG option. Got coredump.
Then I did and got this:
gdb /usr/local/sbin/squid /var/squid/squid.core
....
Reading symbols from /usr/lib/private/libheimipcc.so.11...done.
Loaded symbols for /usr/lib/private/libheimipcc.so.11
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
Segmentation fault (core dumped)

Gdb goes down too =)
Any ideas?
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"

[Dennis Glatting]

There are several problems with Squid source with one of the most
significant in "debug." Specifically, there are print statements using
cstring that DO NOT manage the case where cstring is empty (i.e.,
c_str() returns NULL) thereby producing SIGSEV. There are also a cases
where strlen() is called with a NULL pointer, also causing SIGSEV.

I have ported 3.4 to FreeBSD and I have patches available here. Some
bugs are fixed, others not; However, I am running this code on two busy
sites.

http://www.pki2.com/squid34.tar

I posted this stuff to ports@ but no response (it's a hack of the 3.3
Makefile, files, etc, but I'm not a ports commiter, for the sake of
others :)).

I believe aufs code is broken. I don't use it so I DID NOT try to figure
out why. For certain the Rock Store code is broken.

Note that I used clang++ 3.3 c++11.

--
Dennis Glatting <d...@pki2.com>

[Dennis Glatting]

Oh, and for fun it also compiles under clang++ 3.4 c++11. I don't recall
trying g++ 4.8 or 4.9.

[Adrian Chadd]

Have you filed a bug with the squid developers? I'm sure they'd like
to fix this stuff. :-P


-a

[Volodymyr Kostyrko]

07.02.2014 15:17, Pavel Timofeev wrote:
> Hi!
> There is a problem with squid under FreeBSD10.0.
> Squid crashes immediately if storage type is set to aufs.
> It goes down during read of config file.
>
> No problem with diskd. No problem with aufs under FreeBSD9.2.
>
> Someone thinks that it's related to clang which is default compiler on
> FreeBSD 10.0.
>
> I recompiled www/squid33 with DEBUG option. Got coredump.
> Then I did and got this:
> gdb /usr/local/sbin/squid /var/squid/squid.core

> .....

> Reading symbols from /usr/lib/private/libheimipcc.so.11...done.
> Loaded symbols for /usr/lib/private/libheimipcc.so.11
> Reading symbols from /libexec/ld-elf.so.1...done.
> Loaded symbols for /libexec/ld-elf.so.1
> Segmentation fault (core dumped)
>
> Gdb goes down too =)
> Any ideas?

Well... I'd just like to share some thoughts and facts:

* aufs is not asynchronous anymore, it uses threads now;
* diskd is highly experimental, broken and I suppose noone would fix
it as it all comes down to incorrect prerequisites when planning this
datastore internals;
* rock is not working.

Besides that ufs is still stable and usable. And fast.

--
Sphinx of black quartz, judge my vow.

[Pavel Timofeev]

Hi, I've made a PR for squid34.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192828
Based on www/squid33 and Dennis Glatting's work.
Please, test it!
There are 2 broken options (ECAP and FS_COSS) that I don't know how to
fix (I'm unskillful). It will be great if someone knows a solution.

2014-05-13 10:51 GMT+04:00 Pavel Timofeev <tim...@gmail.com>:
> Hi! Any plans to import squid34 to ports tree?
>
> 2014-02-11 9:40 GMT+04:00 Dennis Glatting <fre...@pki2.com>:
>> On Mon, 2014-02-10 at 20:11 +0100, Florian Smeets wrote:
>>> On 10/02/14 16:21, Dennis Glatting wrote:
>>> > On Mon, 2014-02-10 at 11:15 +0400, Pavel Timofeev wrote:
>>> >> So what should I do?
>>> >> Write a PR to squid's bugzilla with link to this thread?
>>> >> Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
>>> >> look at PRs about squid).
>>> >> And it seems like this problem is retaled to all of squid ports, not
>>> >> only to www/squid33.
>>> >>
>>> >
>>> > Good question. I don't know. I ported 3.4 and sent email to the
>>> > maintainer and to the list. Zip in response.
>>> >
>>>
>>> I plan to take care of it this week. (squid34 + aufs patches)
>>>
>>
>> My stuff here:
>>
>> fetch http://www.pki2.com/squid34.tar
>>
>>
>>> Florian