Dansguardian 2.12.0.3 Signal 11
-
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) -
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
-
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?
-
Is this version compiled to run under freebsd 64 bit?
I'ts only the source code.
I've compiled it for amd64. Check on my repo.
http://e-sac.siteseguro.ws/packages/amd64/8/All/dansguardian-2.12.0.6.sig11.tbz
-
Yes sorry,
Marcelloc can you also make a package with and without "–with-dgdebug=on" ?
I think the first step is trying without@rjcrowder have you tried with 300, or less ?
-
Marcelloc can you also make a package with and without "–with-dgdebug=on" ?
Sure, It's on my repo now.
http://e-sac.siteseguro.ws/packages/amd64/8/All/dansguardian-2.12.0.6.sig11.debug.tbz
-
Marcelloc can you also make a package with and without "–with-dgdebug=on" ?
Sure, It's on my repo now.
http://e-sac.siteseguro.ws/packages/amd64/8/All/dansguardian-2.12.0.6.sig11.debug.tbz
Thanks Marcello… have been a little busy. I will try to get this in over the weekend...
-
Yes sorry,
Marcelloc can you also make a package with and without "–with-dgdebug=on" ?
I think the first step is trying without@rjcrowder have you tried with 300, or less ?
OK… I wasn't 100% sure, so I made some assumptions about what you were asking for.
At the moment, I'm running dans as follows...
nohup ./dansguardian-2.12.0.6-dbg -N > & /tmp/debug &This will send all stdout and stderr messages to /tmp/debug. I'll let you know if I get a Sig 11
-
Perfect, Be careful the system can be unstable, If you have a problem with debug mode (100 % cpu or high memory usage, disk full, etc) try the other build from Marcelloc. It's less interesting for us but it's more faster.
Thanks for your help
-
Perfect, Be careful the system can be unstable, If you have a problem with debug mode (100 % cpu or high memory usage, disk full, etc) try the other build from Marcelloc. It's less interesting for us but it's more faster.
Thanks for your help
OK… got a signal 11 earlier this afternoon. Uploading now to my public dropbox - https://www.dropbox.com/sh/y3qoeiyxnvxl8c1/xmr7LJpScy It might take a while and I'll warn you that the file is huge. Let me know when you've got it. Thanks!
-
I've got it, thanks
Doh big file ! It's not easy to find where the "signal 11" hides -
I've got it, thanks
Doh big file ! It's not easy to find where the "signal 11" hidesI caught it fairly quickly… should be toward the end somewhere...
-
Yes in system.log.sig11
Jun 1 17:04:21 pfsense kernel: pid 10303 (dansguardian-2.12.0), uid 106: exited on signal 11But it's hard to correlate with the other file, for the moment I didn't see any point
-
But it's hard to correlate with the other file, for the moment I didn't see any point
yea… I was wondering how you could correlate them. There's nothing in the debug log that says "signal 11"... That's all I have though - those two logs.
-
Very, very strange, there is no error in debug's file between Date: Sat, 01 Jun 2013 17:02:09 GMT and Date: Sat, 01 Jun 2013 17:04:31 GMT
DG run with very low load, without problembusychildren:1
freechildren:32
waitingfor:0Seems close to http://forum.pfsense.org/index.php?topic=58395.0 in both case the process seem doesn't really crashed (no need to restart)
I don't know what to think, there is no problem with oldest versions ?
EDIT: For those who suffer from "dansguardian -N" issues I will release a new version with a fix next week, here http://numsys.eu/search.php?search=Dansguardian
-
Marcelloc as you know there was a problem with pcre recently, do you compile with pcre on or off ?
Can we make a test with off ? -
Seems close to http://forum.pfsense.org/index.php?topic=58395.0 in both case the process seem doesn't really crashed (no need to restart)
I know I've seen it since 12.0.3 Not sure prior to that…
-
Marcelloc as you know there was a problem with pcre recently, do you compile with pcre on or off ?
Can we make a test with off ?I think it's marked as a dependence on freebsd ports, I'll try to compile it without pcre.
Does dansguardian works fine without pcre????
-
Does dansguardian works fine without pcre????
see this http://contentfilter.futuragts.com/wiki/doku.php?id=pattern_matching. However - looks like compiling without PCRE may cause a problem with some of the regex expressions in the current config…
-
Yes, pcre is for advanced regex
