qlproxyd crash during daemonize resulting in ICAP error

UPDATE: another reason for this error may be – https://sichent.wordpress.com/2014/11/21/icap-error-when-filtering-https-response-headers/

Current version of Diladele Web Safety (3.2.0.4CAF) may crash upon start when improperly configured. The fact that qlproxyd daemon cannot drop root privileges because there is no “qlproxy” user configured results in the exception (unhandled) which in turn results into core dump. For properly configured system impact is minimal as DEB, RPM installer makes sure such “qlproxy” user exists after installation. Fix for this bug will be included into upcoming qlproxy 3.3. See issue https://github.com/ra-at-diladele-com/qlproxy_external/issues/413.

If you are badly affected by this bug – write to support@diladele.com stating so and we will make a patch specifically for you. Sorry for the inconvenience and thanks a lot for Eric!

Diladele Development Team

About sichent

sichent
This entry was posted in Linux and tagged , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s