Dansguardian 2.12.0.3 Signal 11

rjcrowder

Configuration files http://numsys.eu/dansguardian/

Requires

Proxy timeout

Set tcp timeout between the Proxy and DansGuardian

Min 5 - Max 100

proxytimeout = 20

Proxy header exchange

Set timeout between the Proxy and DansGuardian

Min 20 - Max 300

proxyexchange = 20

Pconn timeout

how long a persistent connection will wait for other requests

squid apparently defaults to 1 minute (persistent_request_timeout),

so wait slightly less than this to avoid duff pconns.

Min 5 - Max 300

pcontimeout = 55

Now you can can disabled some (if) unused values, like maxcontentramcachescansize, I think It should be interesting about signal 11 and a potential memory leak.

Marcello… are you going to add these config settings to the UI? If I manually add them to the config files, will they be dropped when I save via the UI?

marcelloc

@rjcrowder:

Marcello… are you going to add these config settings to the UI?

yes. you can force it on dansguardian.inc near

$proxytimeout=($dansguardian['proxytimeout']?$dansguardian['proxytimeout']:"30");

@rjcrowder:

If I manually add them to the config files, will they be dropped when I save via the UI?

Yes.

rjcrowder

@marcelloc:

yes. you can force it on dansguardian.inc near
$proxytimeout=($dansguardian['proxytimeout']?$dansguardian['proxytimeout']:"30");
Thanks - No problem… I'll add them on my setup.

rjcrowder

@marcelloc:

yes. you can force it on dansguardian.inc near

The easiest thing to do was to just add them into dansguardian.conf.template - so that's what I did for now.

Up and running with 2.12.0.6 - I'll keep you posted…!!!

Thanks!

Fredb

If You See Something, please try to reduce your unused values to 0

rjcrowder

@Fredb:

If You See Something, please try to reduce your unused values to 0

Besides "maxcontentramcachescansize", which ones are no longer used?

Fredb

Yes, options with maxsomething, for example those for AV scan, but not now please
EDIT: Only those you don't use of course

Max content filter size

Sometimes web servers label binary files as text which can be very

large which causes a huge drain on memory and cpu resources.

To counter this, you can limit the size of the document to be

filtered and get it to just pass it straight through.

This setting also applies to content regular expression modification.

The value must not be higher than maxcontentramcachescansize

The size is in Kibibytes - eg 2048 = 2Mb

use 0 to set it to maxcontentramcachescansize

maxcontentfiltersize = 0 -> If weightedphrasemode = 0

Max content ram cache scan size

This is only used if you use a content scanner plugin such as AV

This is the max size of file that DG will download and cache

in RAM. After this limit is reached it will cache to disk

This value must be less than or equal to maxcontentfilecachescansize.

The size is in Kibibytes - eg 10240 = 10Mb

use 0 to set it to maxcontentfilecachescansize

This option may be ignored by the configured download manager.

maxcontentramcachescansize = 0 if no AV

Max content file cache scan size

This is only used if you use a content scanner plugin such as AV

This is the max size file that DG will download

so that it can be scanned or virus checked.

This value must be greater or equal to maxcontentramcachescansize.

The size is in Kibibytes - eg 10240 = 10Mb

maxcontentfilecachescansize = 0 if no AV

rjcrowder

OK… good info, but I can't change any of them anyway. I'm using weightedphrasemode=1 and I'm also doing virus scanning...

Thanks

rjcrowder

kernel: pid 53406 (dansguardian), uid 106: exited on signal 11

Just got another one… :-[

marcelloc

@rjcrowder:

Just got another one… :-[
[/quote]

How many on older version.

this latest version suports max clients=8192

Fredb

If you play with maxagechildren it change something ?
I mean maxagechildren = 10 more signal 11 than maxagechildren = 15000 ?

rjcrowder

@marcelloc:

@rjcrowder:

Just got another one… :-[
[/quote]

How many on older version.

this latest version suports max clients=8192

So far it doesn't seem like I'm getting as many. I've only had one in the last 24 hours and I was getting a half dozen or so. I'll try playing with MaxAgeChildren as well…

Fredb

Traffic as usual ? more or less ?

rjcrowder

@Fredb:

Traffic as usual ? more or less ?

Haven't been monitoring total traffic well enough to know. I dropped MaxAgeChildren from 4000 down to 1000 after my last post and I got 5 more signal 11's last night…

I'll bump it up to about 8000 and see what happens.

Fredb

@rjcrowder:

@Fredb:

Traffic as usual ? more or less ?

Haven't been monitoring total traffic well enough to know. I dropped MaxAgeChildren from 4000 down to 1000 after my last post and I got 5 more signal 11's last night…

I'll bump it up to about 8000 and see what happens.

So If I understand right

With 4000 -> 1
With 1000 -> 4

Interresting …

Another question, did you restart DG each day ?

rjcrowder

@Fredb:

Another question, did you restart DG each day ?

I didn't manually restart it… but I believe saving the setting (in the UI) would have at least done a soft restart... and it was 5 of them at 1000.

BTW... Bumped it up to 8000 and had 3 more last night.

Fredb

Ok thank, can you try with 300 ?
There is nothing in the log just before signal 11 , and no complaint from users ?
Are you agree to test a special version which should help us ? I hope without problem …

Fredb

@rjcrowder:

BTW… Bumped it up to 8000 and had 3 more last night.

Last night ? Without activity ?
Please restart the process, and take a look for signal 11 (also with soft restart if you can)

Fredb

http://numsys.eu/dansguardian/pfsense/ This test package contains two changes

Fixed dansguardian -N was broken with recent 2.12.0.3
Change behaviour when a child die (just a test for Freebsd) also add some informations in syslog

I'm focused about child die because DG seem works good although signal 11 is a critical message, so maybe there is a problem only when it exit.
But perhaps I'm wrong and the user just refresh and take an another process, very hard to test without having a working Freebsd …

If someone can try, I need

Just run this version and post here the syslog part with signal 11 , if the problem still present also try to run with dansguardian -N (no background)

But the best way is to make a debug version --with-dgdebug=on and run dg with dansguardian -N /tmp/debug and post the file somewhere (after one signal 11 of course)

Be careful dansguardian -N reduce performance

rjcrowder

@Fredb:

http://numsys.eu/dansguardian/pfsense/ This test package contains two changes

Fixed dansguardian -N was broken with recent 2.12.0.3

Change behaviour when a child die (just a test for Freebsd) also add some informations in syslog

I'm focused about child die because DG seem works good although signal 11 is a critical message, so maybe there is a problem only when it exit.
But perhaps I'm wrong and the user just refresh and take an another process, very hard to test without having a working Freebsd …

If someone can try, I need

Just run this version and post here the syslog part with signal 11 , if the problem still present also try to run with dansguardian -N (no background)

But the best way is to make a debug version --with-dgdebug=on and run dg with dansguardian -N /tmp/debug and post the file somewhere (after one signal 11 of course)

Be careful dansguardian -N reduce performance

Is this version compiled to run under freebsd 64 bit?