Today I registered that proxy stopped it’s work. I could navigate to all sites, also the blocked ones.
After restarting squid and ufdbguard everything went fine, but perhaps somebody can help finding out what happens before. Here is the ufdbguard log with the errors:
The ufdbGuard (1.33.4) software suite is free and Open Source Software. Copyright (C) 2005-2017 by URLfilterDB B.V. and others.
2018-04-16 03:32:00 [19585] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977 2018-04-16 03:32:00 [19585] ufdbgclient 1.33.4 started
2018-04-16 03:32:00 [19585] cannot connect to ufdbguardd daemon - is it running? If yes, check the -p option.
2018-04-16 03:32:00 [19588] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-04-16 03:32:00 [19588] ufdbgclient 1.33.4 started
2018-04-16 03:32:00 [19588] cannot connect to ufdbguardd daemon - is it running? If yes, check the -p option.
2018-04-16 03:32:02 [19585] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-04-16 03:32:02 [19585] after sleeping 2 seconds I still could not connect to the ufdbguardd daemon
2018-04-16 03:32:02 [19585]
2018-04-16 03:32:02 [19585] FATAL ERROR: cannot connect to ufdbguardd daemon socket: No such file or directory
2018-04-16 03:32:02 [19585] Check if ufdbguardd is running and if the -p option is required. *****
2018-04-16 03:32:02 [19585]
2018-04-16 03:32:02 [19584] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-04-16 03:32:02 [19584] after sleeping 2 seconds I still could not connect to the ufdbguardd daemon
2018-04-16 03:32:02 [19586] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-04-16 03:32:02 [19586] after sleeping 2 seconds I still could not connect to the ufdbguardd daemon
2018-04-16 03:32:02 [19587] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-04-16 03:32:02 [19587] after sleeping 2 seconds I still could not connect to the ufdbguardd daemon
2018-04-16 03:32:02 [19588] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-04-16 03:32:02 [19588] after sleeping 2 seconds I still could not connect to the ufdbguardd daemon
Those log lines don’t tell me what’s the problem.
Hints may be somewhere else in /var/log/ufdbguard/ufdbguardd.log or in other logs (/var/log/messages, /var/log/squid/cache.log).
Search around the time of the problem (03:32:00).
Thanks for your answer Filippo.
/var/log/ufdbguard/ufdbgardd stopped logging a time ago at the 6th April and started logging again after I restarted the service today. The log says, that it killed the process because there are running two of them.
Here are the last lines of the old log (it was already zipped)
2018-03-06 09:58:25 [1194] database status: up to date
2018-03-06 09:58:25 [1194] license status: unknown
2018-03-06 09:58:25 [1194] configuration status: ok
2018-03-06 09:58:25 [1194]
2018-03-06 09:58:25 [1194] using OpenSSL library 1.0.1e R (OpenSSL 1.0.1e-fips 11 Feb 2013)
2018-03-06 09:58:26 [1194] HTTPS/SSL verification with trusted certificates from file "/var/ufdbguard/blacklists/security/cacerts" and directory "none"
2018-03-06 09:58:26 [1194] LC_CTYPE is not set
2018-03-06 09:58:26 [1194] LANG is 'C'
2018-03-06 09:58:26 [1194] 32 HTTPS verification threads created.
2018-03-06 09:58:26 [1194] time definitions are used; evaluating current ACLs
2018-03-06 09:58:26 [1194] Changing daemon status to "started"
2018-03-06 09:58:26 [1194] raising privileges to check if an other ufdbguardd process exists
2018-03-06 09:58:26 [1194] dropped privileges and became user 'ufdb'
2018-03-06 09:58:26 [1194]
2018-03-06 09:58:26 [1194] FATAL ERROR: another instance of ufdbguardd with pid 1194 is running. *****
2018-03-06 09:58:26 [1194]
2018-03-06 09:58:26 [1194]
2018-03-06 09:58:26 [1194] FATAL ERROR: cannot bind daemon socket: Success (protocol=UNIX) *****
2018-03-06 09:58:26 [1194]
2018-03-06 09:58:26 [1194] check for and kill old daemon processes
2018-03-06 09:58:26 [1194] and remove UNIX socket file "/tmp/ufdbguardd-03977"
2018-03-06 09:58:26 [1194] Changing daemon status to "error"
2018-03-06 09:58:26 [1194] terminating connections with clients
2018-03-06 09:58:26 [1194] Changing daemon status to "terminated"
2018-03-06 09:58:26 [1194] ufdbGuard daemon stopped
Maybe cross checking other logs to see if something “strange” happened on 2018-03-06 9:58?
I suspect a one time hanging process.
I did some research and there were not much satisfying results, a sudden shutdown could be a reason:
Thanks for your answer Markus, I think I have no chance. Other logs like messages, squid and ufdbguard were deleted by system.
I’ve checked the uptime and I restarted the server at 6th March around 12 o’clock.
I remember I had a problem that it wasn’t reachable before, so I killed it by power-of.
I really want to know how you fix this issue, I met the same error:
2018-08-30 16:04:52 [4530] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
2018-08-30 16:04:52 [4527] ERROR: cannot connect to UNIX socket /tmp/ufdbguardd-03977
When I restart squid, no log.
When I restart ufdb, here are the log in each file:
/var/log/message:
Sep 4 13:10:11 vm-squid-ppd systemd: Stopping LSB: ufdbguardd daemons from URLfilterDB…
Sep 4 13:10:11 vm-squid-ppd ufdb: sent signal sigterm to ufdbguardd (pid=917)
Sep 4 13:10:12 vm-squid-ppd ufdb: Shutting down URLfilterDB daemons OK
Sep 4 13:10:12 vm-squid-ppd systemd: Starting LSB: ufdbguardd daemons from URLfilterDB…
Sep 4 13:10:13 vm-squid-ppd ufdb: Starting URLfilterDB daemons OK
Sep 4 13:10:13 vm-squid-ppd systemd: Started LSB: ufdbguardd daemons from URLfilterDB.
/var/ufdbguard/logs: no other log except reminding the database update.
Hi, Now it works for http but https is bad.
Error:
Proxy tunneling failed: ForbiddenUnable to establish SSL connection.
in/var/log/squid/access/log:
2018-09-06 11:19:40 CST 1 ms 10.70.2.4 TCP_DENIED/403 3890 bits CONNECT www.urlfilterdb.com:443 HIER_NONE/- text/html - Wget/1.14%20(linux-gnu)