Dansguardian (2.12.0.3 pkg v.0.1.8) does NOT start on x64 8-16-13 build
-
Hello…. anyone? Please?
-
"I have touched the access.log"
I'm lead to believe touching logs on pfsense is "bad" because they are circular.
I've had problems with dansguardian in the past and I eventually just reinstalled pfsense, reinstalled squid got that running. Then re-added dansguardian. Some strange interaction between squid and dansguardian was causing my issue.
Maybe try blowing away the squid cache, then reinstalling the squid package then the dansguardian package.
If that doesn't work, maybe just nuke pfsense and reinstall. Its alot faster than it sounds. 4 minutes or so and you know you have a clean install.
-
Hello…. anyone? Please?
No idea why yours isn't starting… this is what mine looks like if it helps...
[root@pfsense /var/log]# ls -ald dansguardian drwxr-xr-x 3 clamav nobody 512 Aug 1 12:46 dansguardian [root@pfsense /var/log]# ls -al dansguardian total 5478 drwxr-xr-x 3 clamav nobody 512 Aug 1 12:46 . drwxr-xr-x 10 root wheel 1024 Aug 13 14:55 .. -rw-r--r-- 1 clamav nobody 5575013 Aug 26 14:10 access.log drwxr-xr-x 2 clamav nobody 512 Aug 1 12:32 stats [root@pfsense /var/log]# -
Thanks RJ,
are you running the x64 build?
And I just did a clean install, not even restoring old config… still complains about not being able to write to the log file.
I wish Marcelloc would look at my thread...
-
Yes… 2.1 RC1 but not sure the exact date (pretty recent though) and x64. I did have some similar rights related issues on the install. I can't remember exactly what I did to fix it, but it is working fine now. If I get a chance this coming weekend, I might do a reinstall and document the steps.
-
Thankee-Sai ;D
-
Yes… 2.1 RC1 but not sure the exact date (pretty recent though) and x64. I did have some similar rights related issues on the install. I can't remember exactly what I did to fix it, but it is working fine now. If I get a chance this coming weekend, I might do a reinstall and document the steps.
OK… I just did a full install of yesterdays (8/29) amd64 RC1 build and had no issues at all with dansguardian/squid. Here's what I did in order...
1. Full install on local drive
2. Setup wan/lan and appropriate addresses for the LAN with DHCP turned on. Also reset the web to http
3. Turn on SSH
4. Login via the web UI and install the following packages (in order)
cron
vhosts
dansguardian
squid3
OpenVPN client export utility
5. Reboot
6. Login via the web UI and do the following
enable DG
set squid proxy to localhost
7. RebootEverything worked and came up fine...
-
Yes… 2.1 RC1 but not sure the exact date (pretty recent though) and x64. I did have some similar rights related issues on the install. I can't remember exactly what I did to fix it, but it is working fine now. If I get a chance this coming weekend, I might do a reinstall and document the steps.
OK… I just did a full install of yesterdays (8/29) amd64 RC1 build and had no issues at all with dansguardian/squid. Here's what I did in order...
1. Full install on local drive
2. Setup wan/lan and appropriate addresses for the LAN with DHCP turned on. Also reset the web to http
3. Turn on SSH
4. Login via the web UI and install the following packages (in order)
cron
vhosts
dansguardian
squid3
OpenVPN client export utility
5. Reboot
6. Login via the web UI and do the following
enable DG
set squid proxy to localhost
7. RebootEverything worked and came up fine...
Well, sadly I ain't still not getting no love (wow, way to mangle the Queen's English :P) Just did a reinstall and am still getting the same log access error…
Thanks for your info, though. Appreciate it.
-
Hmmm… at a little bit of a loss because I can't seem to replicate the problem. Did you install in the same order? Is there any way you could replicate the problem in a Virtualbox VM that I could download and play with?
-
Hmmm… at a little bit of a loss because I can't seem to replicate the problem. Did you install in the same order? Is there any way you could replicate the problem in a Virtualbox VM that I could download and play with?
Sadly I am off on business travel all next week and probably the next. Thank you for your offer, I'll set one up as soon as I can.