Bug 12424 - Core 145: Squidguard going into emergency mode
Summary: Core 145: Squidguard going into emergency mode
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: x86_64 Linux
: Will affect an average number of users Crash
Assignee: Arne.F
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-01 08:31 UTC by Christoph Moser
Modified: 2020-06-06 07:51 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Moser 2020-06-01 08:31:03 UTC
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

Matthias Fischer
mfischer
3
3h

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 1 - 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
Comment 1 Michael Tremer 2020-06-02 08:02:28 UTC
Christoph, I cannot make much sense out of your bug report, but I suppose this has already been fixed here:

https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91b23ce05b77dc96b38de3589049cbe8350ba9ad
Comment 2 Matthias Fischer 2020-06-06 07:51:31 UTC
=> https://community.ipfire.org/t/core-145-squidguard-going-into-emergency-mode/2377/17

"I did a fresh install using bea09ff2 followed by a configuration restore. All seems to be working again."