Error Connecting Via Ipc Socket To Log Connection Refused
just recently upgraded dansguardian (2.10-r1) and finally found the problem. I originally posted this issue in February on the Gentoo forums and didn't receive any response. Today, I found the problem and the fix. Below is an example of the logs: Nov 11 09:08:10 comp dansguardian[22266]: Error connecting via IPC socket to log: No such file or directory
Nov 11 09:08:21 comp dansguardian[22262]: Error connecting via IPC socket to log: No such file or directory
Nov 11 09:08:22 comp dansguardian[22262]: Error connecting via IPC socket to log: No such file or directory
Nov 11 09:08:22 comp dansguardian[22267]: Error connecting via IPC socket to log: No such file or directory
Nov 11 09:08:22 comp dansguardian[22266]: Error connecting via ipc to url cache: No such file or directory
Nov 11 09:08:22 comp dansguardian[22266]: Error connecting via ipc to url cache: No such file or directory
Nov 11 09:08:22 comp dansguardian[22266]: Error connecting via IPC socket to log: No such file or directory
Nov 11 09:19:40 comp dansguardian[22262]: Error connecting via ipc to url cache: No such file or directory
Nov 11 09:19:40 comp dansguardian[22262]: Error connecting via IPC socket to log: No such file or directory
Nov 11 09:19:40 comp dansguardian[22263]: Error connecting via ipc to url cache: No such file or directory
Nov 11 09:19:41 comp dansguardian[22263]: Error connecting via ipc to url cache: No such file or directory
Nov 11 09:19:41 comp dansguardian[22263]: Error connecting via IPC socket to log: No such file or directory What I should have done originally was searched the dansguardian directory and sub-directories for instances of IPC. I found that IPC was referenced in dansguardian.conf, and found that the sockets were being created in /tmp. srwxr-xr-x 1 nobody nobody 0 Nov 11 10:12 .dguardianipc
srwxr-xr-x 1 nobody nobody 0 Nov 11 10:12 .dguardianurlipc That's when the light bulb appeared above my head. I use tmpreaper to clean out my /tmp folder. It will delete anything older than a day old. This is what was nuking my sockets. I added the following argument to my tmpreaper command: tmpreaper --all 1d --mtime --force --protect '.dguardian*' /tmp Everthing is much better now.If you found this post helpful, buy me a beer. admin's blog • Login to p
Felipe
previous next » Print Pages: [1] Go Down Author Topic: Dansguardian not blocking (Read 2254 times) 0 Members and 1 Guest are viewing this topic. awsiemieniec Full Member Posts: 181 Karma: +2/-0 Dansguardian https://forum.pfsense.org/index.php?topic=55331.0 not blocking « on: November 01, 2012, 05:21:10 pm » I have a fresh install of pfS 2.0.1 AMD64.Dansguardian: 2.12.0.0 pkg v.0.1.6_1 via the package manager of webConfiguratorSquid3: 3.1.20 pkg https://readthefuckingmanual.net/error/3878/Error-connecting-via-IPC-socket-to-log-Connection-refused 2.0.5_5 via the package manager of webConfiguratorI first installed squid3, then Dansguardian. Squid3 is configured and working. Dansguardian is configured but doesn't appear to be working. I've created a NAT error connecting port forward of "LAN/TCP/LAN net/*/*/80 (HTTP)/127.0.0.1/8080". I have squid3 working on loopback, 3128, transparent and Dans configured on LAN, 8080 with proxy of 127.0.0.1:3128.I've done all the configuring via the webConfigurator - no modifying via shell or whathaveyou. I add "playboy.com" to the config (text file) section of Services, Dansguardian, Access Lists, Site, Default (edit), Banned and then navigate to error connecting via said site and I still am able to see all the site.I've overlooked something but can't see what/where. I've rebooted pfS multiple times, run dansguardian -Q after each config change... still nothing.Looking at the system log this stands out:QuoteNov 1 15:01:27php: : Not calling package sync code for dependency squidreverse of squid3 because some include files are missing.Nov 1 15:01:24php: : XML error: XML_ERR_NAME_REQUIRED at line 1 in /usr/local/pkg/dansguardian_users_footer.xmlNov 1 15:01:24php: : XML error: Invalid document end at line 99 in /usr/local/pkg/dansguardian_users_header.xmlNov 1 15:01:24php: : XML error: Invalid document end at line 114 in /usr/local/pkg/dansguardian_ips_header.xmlAny help is appreciated.Thx Logged marcelloc Hero Member Posts: 12161 Karma: +435/-3 Re: Dansguardian not blocking « Reply #1 on: November 02, 2012, 12:51:00 am » The first step is to check and save all dansguardian config tabs.Second step is check you nat for transparent proxy Logged Treinamentos de Elite: http://sys-squad.comHelp a community developer! Te ajudei? Doações são sempre bem vindas! awsiemieniec Full Member Posts: 181 Karma: +2/-0 Re: Dansguardian not blocking « Reply #2 on: November 02, 2012, 12:31:23 pm » Thanks fo
400 Permalink Add an answer/solution If you know the answer, please add your own solution below. If you don't know, but find out later, please come back and share your answer - there will be other people struggling with this too. Please enter 61948 here If you want to be notified via email when this is solved, enter your email address here: Psst - want to help build a list of common error messages? Put the following line in your /etc/[r]syslog.conf file: *.emerg,*.alert,*.crit,*.err @syslog.readthefuckingmanual.net Collecting solutions to error messages since Aug 2005. © rtfm 2005-2016