Did you try just deleting your old .db files in /usr/share/squidGuard-1.4/db/* and running squidGuard -C all?

BTW we also have ufdbguard in Mageia 3 as an alternative to squidGuard.

Created attachment 4465 [details]
update the squidGuard data base

Ok. Tried this : 
# urpme squidguard --> to remove the mandriva rpm
# urpmi squidguard --> to install the mageia 3 rpm
# vi /etc/squid/squidGuard.conf --> to add the doubles quotes
# rm -rf /usr/share/squidGuard-1.4/db/* --> to delete the data base
# /root/maj_squidguard.sh --> to run my updating script (see attachment)

The script fails but the data base is correctly recreated.
Then test with :
# echo "http://www.example.com 192.168.0.160/- - GET" | squidGuard -c /etc/squid/squidGuard.conf -d
2013-11-01 17:26:26 [2554] New setting: dbhome: /usr/share/squidGuard-1.4/db
2013-11-01 17:26:26 [2554] New setting: logdir: /var/log/squidGuard
BDB1565 DB->put: method not permitted before handle's open method
2013-11-01 17:26:26 [2554] sgDbUpdate: put: Invalid argument
2013-11-01 17:26:26 [2554] Going into emergency mode

Still a no go.

I've taken a look at ufdbguard web site. This is not free software and the data base isn't costless.

(In reply to Paul Ãric Despretz from comment #3)
> I've taken a look at ufdbguard web site. This is not free software and the
> data base isn't costless.

Incorrect.  It *is* free software (GPL), and you don't need their database to use it.

(In reply to David Walser from comment #4)
> (In reply to Paul Ãric Despretz from comment #3)
> > I've taken a look at ufdbguard web site. This is not free software and the
> > data base isn't costless.
> 
> Incorrect.  It *is* free software (GPL), and you don't need their database
> to use it.

Ok perhaps I'm wrong but from their web site (http://www.urlfilterdb.com/en/products/ufdbguard.html) you can read :

ufdbGuard is an extremely fast and free URL filter in public domain.
ufdbGuard is copyright-protected, but free for use.

So I thought that if it is copyright-protected, it is not GPL.
But on Sourceforge we can read that licence is GPL V2...

BTW, I'm happily running my server with squidGuard and would like to continue. :=)

The GPL relies on copyright.  You can't place a GPL (or any other) license on your work if you don't own the copyright to it.  Copyright protection is what makes the GPL (and other licenses) enforceable.

Luckily the ufdbguard configuration file is largely compatible with squidGuard.conf, so it's not difficult to migrate over to it.  I do recommend that.

I just confirmed this bug BTW, squidguard really is broken :o(

OK, you correctly identified the culprit.  It was broken when it was changed to build against db5 instead of db4.  Building it locally against db4 fixes it and it works again.  I'll build fixed packages.

Fixed for Cauldron in squidguard-1.4-19.mga4.

Fixed package also uploaded for Mageia 3.

Thanks for the report Paul!  You can help get this update released more quickly by testing the rebuilt package in Mageia 3 core/updates_testing and confirming that it works for you.  Ultimately we'll need it tested on both i586 and x86_64 before issuing the update.

Advisory:
----------------------------------------

The squidGuard package in Mageia 3 was built against an incompatible version
of the Berkeley DB library.  It has been rebuilt against the correct version.

----------------------------------------
Updated packages in core/updates_testing:
----------------------------------------
squidguard-1.4-17.1.mga3

from squidguard-1.4-17.1.mga3.src.rpm

Hardware: x86_64 => All
Assignee: bugsquad => qa-bugs

Thanks for the quick action !
Actually testing it :
The default /etc/squid/squiGuard.conf needs to be modified. squidguard is complaining about syntax errors in the squidGuard.conf provided by the rpm.
1) Needs the double quote at line 5 --> dbhome "/usr/share/squidGuard-1.4/db"
2) Don't like the - on line 37 --> src fooclients {
3) Don't like the - on line 41 --> src barclients {
4) Don't like the /26 without a space before on line 42 --> ip   172.16.4.0 /26
5) then error in the acl because it don't find foo-clients anymore on line 68 
--> fooclients within workhours {
6) idem for line 74 --> barclients {

I will now try with my real configuration file.

Thanks for testing.  Granted I use a different directory for my dbhome than the default, but it does not need quotes.  I wonder what's going on there.

No way. :=(
squidGuard is refusing the - in the config file. The parser seems to truncate everything following a -
Some can be protected by the double quotes but some are not... 
IMHO, the parser seems to be foolish :

The line 
urllist audio-video/urls is translated in :
init urllist /usr/share/squidGuard-1.4/db/audio
2013-11-01 22:43:09 [3236] /usr/share/squidGuard-1.4/db/audio: No such file or directory
2013-11-01 22:43:09 [3236] Going into emergency mode

The line 
urllist "audio_video/urls" is translated in :

init urllist /usr/share/squidGuard-1.4/db/audio_video/urlsins
2013-11-01 22:36:20 [3226] /usr/share/squidGuard-1.4/db/audio_video/urlsins: No such file or directory
2013-11-01 22:36:20 [3226] Going into emergency mode
The parser adds ins at the end of the line...

Ahh, OK.  The dbhome I use doesn't have a - in it.  Does it work if you put a \ before the - (so /usr/share/squidGuard\-1.4/db)?  Just curious.

Honestly it'd probably be better to drop the version from the directory name.

But yeah now that you point out the other problems, sounds like there's some real issues with it.  There is a 1.5 beta, I wonder if it fixes these problems.  Ultimately it's probably better to use ufdbguard as it's more actively maintained upstream.

As far as building another update to deal with the "-" issue, I'm not sure that's really needed.  It's just a default configuration that isn't really very useful, as the examples in /usr/share/squidGuard-1.4/db really are just examples.  The real use case for this software is to either make your own filter lists or obtain some from the web, and then store them somewhere else in the filesystem (like /etc) and change the dbhome accordingly.

Protecting with \ doesn't work...

Some workaround found :
1) Replacing all the - by _ in destination name and log name
example : the line 
dest audio-video
becomes the line
dest audio_video
 
2) When a syntax error occurs and if the double quote protection is useless then pushing the line containing urllist before the line domainlist does the trick...

Example : 
dest audio_video {
        urllist "audio-video/urls"
        domainlist "audio-video/domains"
        log /var/log/squidGuard/audio_video.log
}
works and gives no error

but 
dest audio_video {
        domainlist "audio-video/domains"
        urllist "audio-video/urls"
        log /var/log/squidGuard/audio_video.log
}
is buggy and gives this error message :
init urllist /usr/share/squidGuard-1.4/db/audio-video/urlsins
2013-11-01 23:14:55 [3301] /usr/share/squidGuard-1.4/db/audio-video/urlsins: No such file or directory
2013-11-01 23:14:55 [3301] Going into emergency mode

I've modified my config file. It seems to work...

I can confirm that the updae is working on my newly upgraded proxy server. Just wish I had found it earlier when I started yesterday my update from 2 to 3 !

Thanks a lot and I hope it will soon move to updates as the current one is broken anyway.

CC: (none) => bruno

Bruno, what architecture are you running?  Paul has already confirmed it working on x86_64, so once someone confirms it working on i586, it's ready to validate and push as an update.

Mine is i586 so go ;-)

Advisory 11575.adv committed to svn.

Before validating the update, what about the underscore
and hyphen issue from comment 13?

CC: (none) => davidwhodgins

That's a software issue, not a packaging issue.  I won't be updating this further.

Validating the update.
Could someone from the sysadmin team push 11575.adv to updates.

Keywords: (none) => validated_update
Whiteboard: (none) => MGA3-64-OK MGA3-32-OK
CC: (none) => sysadmin-bugs

Update pushed:
http://advisories.mageia.org/MGAA-2013-0122.html

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED