After update to core 145 Squidguard does not work any longer. Receive following error in URL filter log viewer
Cursor: Invalid argument followed by
Going into emergency mode
Any hints how to resolve this?
Hi,
I last saw this…10 years ago!? And I’m running a heavily patched 1.5 beta for about 4 years now.
Some more information about your configuration would be useful:
How is squidguard configured?
Which blocklist?
Any other addons running?
Anything else but this single line in the log?
HTH,
Matthias
Hallo Matthias,
Thank you for your reply. I do not have any add-ons installed; just the basic ipfire. I have both shallalist and Univ. Toulouse active plus my own huge blocklist. Everything else is standard. When I googled for this, I saw that this was a bug in squidguard quite some time ago. All was working fine till the update to 145.
Regards,
Christoph
Look for example here
https://nightly.ipfire.org/master/2020-05-30%2018:04:33%20+0000-bea09ff2/x86_64/changelog.txt
core145: remove converted urlfilter databaseto force rebuilt with new db.
Try a new build.
Hi,
I did that, too.
The last ones I found were around 2013/2014.
Anything helpful in the squidguard log? There must be more than “…going into emergency mode”.
Best,
Matthias
deleted all in /var/ipfire/urlfilter/blacklists
reloaded shallist via GUI
now I see in log:
New setting: logdir: /var/log/squidGuard
New setting: dbhome: /var/ipfire/urlfilter/blacklists
init domainlist /var/ipfire/urlfilter/blacklists/adv/domains
BDB1565 DB->put: method not permitted before handle’s open method -->> shown when run autoupdate manualy in ssh shell
sgDbLoadTextFile: put: Invalid argument
Going into emergency mode
Hi,
it looks as we are back to a really old squidguard bug. This is the one from 2013…
- Would you please file a bug report as soon as possible!?
- This could be due to this update - as I said, I haven’t seen this error for years.
- Since you’re on a testing tree, go back to stable and squidguard should run again.
Best,
Matthias
EDIT:
P.S.: Are you on 32bit or 64bit?
I would love to open a bug report but how do I create the login credentials in bugzilla? I do not see any link to create a new account.
I am on 64 bit on an APU1
You don’t need to create a new account, just login with the same credentials as here.
I created the bug report.
When I put the second line of /var/ipfire/urlfilter/squidGuard.conf in double quotes (dbhome “/var/ipfire/urlfilter/blacklists”) I am getting syntax error for line 2
Hi,
then we’re really back in 2013 - could be a problem with the Berkeley DB(?).
Could you please send the output of ldd /usr/bin/squidGuard!?
Best,
Matthias
Hi,
here it is:
[root@pelikan ~]# ldd /usr/bin/squidGuard
linux-vdso.so.1 (0x00007ffe8cf34000)
libpthread.so.0 => /lib/libpthread.so.0 (0x0000770a8faf9000)
libdb-5.3.so => /usr/lib/libdb-5.3.so (0x0000770a8f935000)
libc.so.6 => /lib/libc.so.6 (0x0000770a8f750000)
/lib64/ld-linux-x86-64.so.2 (0x0000770a8fb24000)
and squidGuard -v SquidGuard: 1.4 Berkley DB 5.3.28: (September 9, 2013)
Thats it.
I have some “strange” idea…
But I’m not sure yet - which installer did you need/use for APU1?
What do you doing guys? 
Try what i said above, new build. Have no problems with that.
bea09ff2
https://nightly.ipfire.org/master/2020-05-30%2018:04:33%20+0000-bea09ff2/
Ok, right now I’m building this one here. You didn’t mention that you’re running that one without problems. Sounded like “try and see what happens” to me. 
I have used ipfire-2.25.x86_64-full-core140.iso
try the newest stable version Core 144.
Hi
I did a fresh install using bea09ff2 followed by a configuration restore. All seems to be working again. Thank you for all the help.
Just out of interest: what was the cause of this squidGuard db issues?
Hi,
Berkeleydb was updated from 4.4.20 to 5.3.28.
Squidguard needs a patch for this to work.
Best,
Matthias