Crash report or programming bug after upgrading to squid3 0.3.8
-
Hi all!
I uninstalled the previous version (0.3.7) and then installed the new (0.3.8).
I see all the services started in "Status / Services," but whenever access to WebGUI, the "Status: Dashboard" displays the following message:
pfSense has detected a crash report or programming bug. Click here for more information.
And the information these are:
–---------------------------------------------------------------------
Crash report begins. Anonymous machine information:amd64
10.1-RELEASE-p15
FreeBSD 10.1-RELEASE-p15 #0 c5ab052(releng/10.1)-dirty: Sat Jul 25 20:20:58 CDT 2015 root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10Crash report details:
PHP Errors:
Example config file for freshclam
Please read the freshclam.conf(5) manual before editing this file.
Comment or remove the line below.
#Example
Path to the database directory.
Default: hardcoded (depends on installation options)
DatabaseDirectory /var/db/clamav
Path to the log file (make sure it has proper permissions)
Default: disabled
UpdateLogFile /var/log/clamav/freshclam.log
Maximum size of the log file.
Value of 0 disables the limit.
You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes)
and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes).
in bytes just don't use modifiers. If LogFileMaxSize is enabled,
log rotation (the LogRotate option) will always be enabled.
Default: 1M
#LogFileMaxSize 2M
Log time with each message.
Default: no
#LogTime yes
Enable verbose logging.
Default: no
#LogVerbose yes
Use system logger (can work together with UpdateLogFile).
Default: no
#LogSyslog in /usr/local/pkg/squid.inc on line 1675
Example config file for freshclam
Please read the freshclam.conf(5) manual before editing this file.
Comment or remove the line below.
#Example
Path to the database directory.
Default: hardcoded (depends on installation options)
DatabaseDirectory /var/db/clamav
Path to the log file (make sure it has proper permissions)
Default: disabled
UpdateLogFile /var/log/clamav/freshclam.log
Maximum size of the log file.
Value of 0 disables the limit.
You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes)
and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes).
in bytes just don't use modifiers. If LogFileMaxSize is enabled,
log rotation (the LogRotate option) will always be enabled.
Default: 1M
#LogFileMaxSize 2M
Log time with each message.
Default: no
#LogTime yes
Enable verbose logging.
Default: no
#LogVerbose yes
Use system logger (can work together with UpdateLogFile).
Default: no
#LogSyslog in /usr/local/pkg/squid.inc on line 1675
Grateful for any help.
Jairo Raiol
-
Perhaps you could read the FAQ in the proper thread…
-
I'm having the exact same problem after updating the package. Trying the recommended update procedure now and will feedback once it's done.
jairoraiol, did you have the HAVP package installed on your system at some point?
EDIT: the problem persists after using the recommended update procedure. The crash happens only when Antivirus is enabled, directly after saving the Squid config, even on the "General" tab.
EDIT2: the crash also happens directly after clicking the "Update AV" button.
Crash log:
Crash report begins. Anonymous machine information: amd64 10.1-RELEASE-p15 FreeBSD 10.1-RELEASE-p15 #0 c5ab052(releng/10.1)-dirty: Sat Jul 25 20:20:58 CDT 2015 root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 Crash report details: PHP Errors: ## Example config file for freshclam ## Please read the freshclam.conf(5) manual before editing this file. ## # Comment or remove the line below. #Example # Path to the database directory. # Default: hardcoded (depends on installation options) DatabaseDirectory /var/db/clamav # Path to the log file (make sure it has proper permissions) # Default: disabled UpdateLogFile /var/log/clamav/freshclam.log # Maximum size of the log file. # Value of 0 disables the limit. # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes) # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes). # in bytes just don't use modifiers. If LogFileMaxSize is enabled, # log rotation (the LogRotate option) will always be enabled. # Default: 1M #LogFileMaxSize 2M # Log time with each message. # Default: no #LogTime yes # Enable verbose logging. # Default: no #LogVerbose yes # Use system logger (can work together with UpdateLogFile). # Default: no #LogSyslog in /usr/local/pkg/squid.inc on line 1675 ## Example config file for freshclam ## Please read the freshclam.conf(5) manual before editing this file. ## # Comment or remove the line below. #Example # Path to the database directory. # Default: hardcoded (depends on installation options) DatabaseDirectory /var/db/clamav # Path to the log file (make sure it has proper permissions) # Default: disabled UpdateLogFile /var/log/clamav/freshclam.log # Maximum size of the log file. # Value of 0 disables the limit. # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes) # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes). # in bytes just don't use modifiers. If LogFileMaxSize is enabled, # log rotation (the LogRotate option) will always be enabled. # Default: 1M #LogFileMaxSize 2M # Log time with each message. # Default: no #LogTime yes # Enable verbose logging. # Default: no #LogVerbose yes # Use system logger (can work together with UpdateLogFile). # Default: no #LogSyslog in /usr/local/pkg/squid.inc on line 1675 -
No, you plain did not read the FAQ. Which part of make the "advanced" fields empty, configure the rest of Antivirus and Save the Antivirus settings is unclear? That takes about 15 seconds. Getting ridiculous really. >:(
-
I did read the FAQ and I did follow it step by step, and I'm still getting the crashes.
EDIT: I just repeated the "clear advanced options" routine just to be certain, and I'm still getting the crash reports. I can save the config without crashes when Antivirus is disabled, but as soon as it's enabled and I save the configuration I'm getting the crashes. Happy to give more detailed information if it helps, just tell me what you need.
-
Yeah, OK. Then read the FAQ again to clean up your broken configuration. (If you still have HAVP installed, then don't bother before uninstalling that thing.) Finally… already explained multiple times on that exact same thread - the damned advanced config thing needs to redone from scratch and certainly will NOT stay in the current form. That's not going to happen before this PR gets merged, cleaning up, shuffling and reordering the 3K lines squid.inc monstrosity.
There won't be any effort to fix whatever are you seeing with the current nonsense that uses 4 different places to save the same piece of configuration:
- foo.conf.default is shipped with PBI; if not, foo.conf.sample shipped with PBI is copied to it
- after that, foo.conf.sample is patched with pfSense specific config
- after that, foo.conf.sample is imported to config.xml
- after that, the config.xml part is saved to foo.conf, overwriting the shipped foo.conf - that's what is used for the actual services, and that's NOT what you in fact see in the advanced boxes in the GUI.
On whatever change you make in the AV GUI, things get messed up unless the "advanced" boxes are empty - in which case - the foo.conf.sample is re-imported to config.xml reflecting the rest of configured options in the AV GUI, foo.conf is re-saved and things get aligned once again. Configure the AV once per the FAQ and do NOT touch it after that.
-
I've had HAVP installed at some point in the past, but it was removed before I've updated the Squid package. As I wrote, I uninstalled the Squid package with "keep config" deselected, not sure what else I could do to "clear my broken config".
My gut feeling is that this problem is connected with having HAVP installed at some point, maybe one of the advanced config files and/or logs has incorrect permissions/owner or something. I've checked permissions on various files, but I'm not proficient enough with FreeBSD and/or the pfSense inner workings to be certain that I got all instances.
-
No, this is not any permissions problem. If you don't have any real problem beyond "crash report", then stop wasting your time.
-
Yes, it seems the only "problem" is the crash report, virus scanning is working and it seems like the virus defs are being updated. You're saying I should ignore the crash report for the time being, until the mess with the config files is sorted out, right? Why did't you say so from the beginning instead of assuming I'm a moron in this peculiar passive-aggressive way of yours? (;
Anyway, thanks for the support and for your work on this package.
-
As explained above, the AV configuration logic is completely broken and not fixable without redoing from scratch. Cannot reproduce the "crash" issue, and even if I could, I wouldn't be working around that in any way, just pure waste of time.
-
Hi all!
SaschaITM not installed HAVP in no time.
I also believe that the problem is only the notice because I had no problem with using the pfSense box on my network. However, my client may not like to see something related to "crash". He will be concerned about the future of the box.
I performed all procedures FAQ, yes, even cleaned all settings fields. As this did not solve, I decided to reinstall everything again, including the pfSense, but once activated the AV the report was again shown.
For me fine. I explain to my client so that it is quiet.
Thank doktornotor! His work is important.
Sorry for the English, translated with Google translator.
-
The antivirus GUI madness will be fixed in 0.3.9; I have it working internally (at least as far as switching between manual and GUI config is concerned).
-
Resolved with the new version!
Thank you doktornotor.