2.2 Update Woes - Squid/Squidguard/vnstat

tester_02

I tried running the RC builds of 2.2 in my past and failed with issues on squid/squidguard.

This time around I have just as many issues. I believe this is my worst update ever (been here since before 1.2.1)

1. vmware tools. errors all over vmware (using workstation). I tried installing/uninstalling. I saw errors on he console with version mismatching. I am guessing that vmware support is out of the box in the new freebsd and not really needed? Only way to avoid these issues was to just remove it.
2. Squid/squidguard. Update left this not working. This is a downright mess. Package manager shows squid 2.x available and it just does not work at all. Squid 3.X does install but leaves me with 2 services failing to start (clam and c-icap). Both services are new to me from the past. rebooted, uninstalled, rebooted, reinstalled. now it seems to be running. Squidguard. There are 3 shown in the package manager. If they don't work, then they should be removed, or at least show that it's not for 2.2.
Bunch of errors.
Jan 24 22:30:36 php: squidGuard_blacklist_update.sh: The command 'umount -f /tmp/squidGuard' returned exit code '1', the output was 'umount: /tmp/squidGuard: not a file system root directory'
Jan 24 22:30:36 php: squidGuard_blacklist_update.sh: The command '/usr/pbi/squid-amd64/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'
Jan 24 22:30:03 php: squidGuard_blacklist_update.sh: The command 'chmod 1777 /tmp/squidGuard' returned exit code '1', the output was 'chmod: /tmp/squidGuard: No such file or directory'
Jan 24 22:30:03 php: squidGuard_blacklist_update.sh: The command '/sbin/mdmfs -s 300M md15 /tmp/squidGuard' returned exit code '1', the output was 'mdmfs: mount exited with error code 1'

I still have no answer as it's not working.

3. Vnstat. Not working in 2.2. Gives errors when entering. creates a pfsense crash report.
otice: Undefined index: totalrx in /usr/local/www/vnstat2/index.php on line 86 Notice: Undefined index: totalrxk in /usr/local/www/vnstat2/index.php on line 86 Notice: Undefined index: totaltx in /usr/local/www/vnstat2/index.php on line 87 Notice: Undefined index: totaltxk in /usr/local/www/vnstat2/index.php on line 87 Notice: Illegal string offset 'rx' in /usr/local/www/vnstat2/index.php on line 94 Notice: Illegal string offset 'tx' in /usr/local/www/vnstat2/index.php on line 95 Notice: Illegal string offset 'rx' in /usr/local/www/vnstat2/index.php on line 99 Notice: Illegal string offset 'tx' in /usr/local/www/vnstat2/index.php on line 100 Notice: Illegal string offset 'rx' in /usr/local/www/vnstat2/index.php on line 104 Notice: Illegal string offset 'tx' in /usr/local/www/vnstat2/index.php on line 105

So what is the solution? For me it's restore an earlier vm and stick with 2.1.5 until the packages are more stable. Just want basic squidguard for filtering and vnstat to track monthly traffic.
The highlight. Snort works!!!!

marcelloc

@tester_02:

1. vmware tools. errors all over vmware (using workstation).

Install openvmtools from ports. It's a freebsd10 x vmware issue, not related to pfsense.
http://ogris.de/vmware/freebsd10.html
https://www.freebsd.org/cgi/ports.cgi?query=open-vm-tools-nox11&stype=all&sektion=all

@tester_02:

2. Squid/squidguard.
Squid 3.X does install but leaves me with 2 services failing to start (clam and c-icap).

Check and save all config tabs on squid. antivirus is working on squid3.

@tester_02:

Squidguard. There are 3 shown in the package manager.

Run latest squidguard version as cino posted on other thread.

@tester_02:

I still have no answer as it's not working.

search the forum. Answers are there.

@tester_02:

3. Vnstat. Not working in 2.2. Gives errors when entering. creates a pfsense crash report.

Not using it but there are other topics with workarounds.
https://forum.pfsense.org/index.php?topic=85304.msg468491#msg468491

Did you read Release notes before updating?

https://blog.pfsense.org/
…
Packages

While the most popular packages should be fine, lesser-used ones may not have been updated by their maintainer, or may not be well-tested and have issues. If you’re dependent on packages, we encourage you to test your combination of packages before upgrading in production.
...

LinuxTracker

Same squidGuard issue as the OP - on 2 machines running pfSense natively (1 Xeon & 1 AMD64).

Squid 3 installs fine. Squid3, clamd and c-icap services are running.
SquidGuard for Squid3 seems to install OK but the sucker just won't run.

There are no errors on run in the System log. The filter logs on both systems show:

squidGuard stopped (1422302209.338)
db update done
squidGuard 1.4 started (1422302209.331)

I have some squidGuard install log errors - same on both machines.

php: squidGuard_blacklist_update.sh: The command 'umount -f /tmp/squidGuard' returned exit code '1', the output was 'umount: /tmp/squidGuard: not a file system root directory'
php: squidGuard_blacklist_update.sh: The command '/usr/pbi/squid-amd64/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'
php: squidGuard_blacklist_update.sh: The command 'chmod 1777 /tmp/squidGuard' returned exit code '1', the output was 'chmod: /tmp/squidGuard: No such file or directory'
php: squidGuard_blacklist_update.sh: The command '/sbin/mdmfs -s 300M md15 /tmp/squidGuard' returned exit code '1', the output was 'mdmfs: mount exited with error code 1'

These are 2.1.5 x64 -to- 2.2 x64 upgrades on boxes that had been running squid 3 & squidGuard-for-squid3.
(On the AMD64 box I uninstalled squid and squidGuard before upgrading pfSense.)

I've:

clicked tabs (left to right) on squid+squidGuard and set the settings including reconfiguring ClamAV, Shallalist download and setting ACLs
Removed both packages, did find / -name "squid*" and rm -r what was left, reinstalled both packages, repeated step 1
Read through each thread posted in the last year mentioning squidGuard and pfSense 2.2

FYI: squid -z gives

Warning: empty ACL: acl throttle_exts urlpath_regex -i "/var/squid/acl/throttle_exts.acl"
Squid is already running!  Process ID 3462

Unsure if that's relevant

I could use some inspiration if anyone has any ideas.
Thanks

PS: Noticed squidGuard hasn't been updated in a year
squidguard-squid3-1.4_4-amd64.pbi 12-Feb-2014 17:58 13387060
http://files.pfsense.org/packages/10/All/

KOM

I think I remember reading that the new SquidGuard works on demand and doesn't stay running if there is nothing for it to do.

mhab12

@tester_02:

2. Squid/squidguard.
Squid 3.X does install but leaves me with 2 services failing to start (clam and c-icap).

Check and save all config tabs on squid. antivirus is working on squid3.

This worked for me, squid 3.4.10/0.2.6 is now up and running in transparent mode. Thanks marcelloc!

LinuxTracker

@KOM:

I think I remember reading that the new SquidGuard works on demand and doesn't stay running if there is nothing for it to do.

It'd be weird for the service to show as not started. There'd probably be a lot of posts about it too.

I'll keep poking at it, see if I can puzzle it out.
Thanks.

marcelloc

If it's not dead by missing libs, the status may show stopped when squid does not have any client request.

That's a squid3 feature to control helpers processes.

LinuxTracker

@marcelloc:

If it's not dead by missing libs, the status may show stopped when squid does not have any client request.

That's a squid3 feature to control helpers processes.

I was struggling with that because squid3 shows as running. It's squidGuard that's stopped.

However I set my struggle aside and went back to test your theory with some browser traffic.

Before launching a test browser, I logged into pfSense, went to squidGuard config
and
squidGuard
is
running.

fWhat?!

Yep. Running.
I set some ACLs, restarted squidGuard and squidGuard is stopped again.
Restared my test browser and squidGuard automagically comes to life.

I have very mixed feelings.
Until now, getting a STOPped status after pushing the Start button is how squidGuard told us IT WAS BROKEN.

Nonetheless, my problem is solved and I appreciate the help.

tester_02

Thanks for the reply marcelloc.
Your openvpn solution is great.
squid I did more installing/reinstalling and then saving tabs and I finally got it working. I never got squidguard working and I am following the other threads and will give it another go in a few more days. I still see lots of daily messages, so I can see it's not all clear at this point.
Vnstat is still not working for me even with the workarounds. I will give it another go in a few days.

I am sure it will work. I am mostly writing it to tell people that this is not a seamless update like we have had in the past. The package system seem to be broken and unmanaged. Packages that are clearly not working are shown to be compatible for 2.2 and packages that are currently working to be at 2.1).
A common sense approach would be that the packages should be flagged for the last confirmed working version and leave the maintainer to set the flag on his package. If packages like openvpn are not confirmed working for say 2.2, then it should show 2.15. We have many squid and squidguard packages and they all show working on 2.2 when we know that is not the case.
The core pfsense seems to be great and stable, but the packages seem to be slipping. This might not be the place for it, but I know I would pay a small amount on my home setup to keep the basic packages running (proxy server/a filter/intrusion detection/metering package) and maintained by a core team.

Cino

try squidguard-dev instead of squidguard3

there is an issue with the libs after reboot but search for my post on how to correct it if you still need squidguard