Linux Forums - Linux Help,Advice & support community:LinuxSolved.com
		Network Troublshooting => Linux Servers Support => Topic started by: Silverado on July 12, 2004, 10:20:33 AM
		
			
			- 
				Hello,
 
 Im a linux newbie.. i faced a crash in squid2.4STABLE7 while adding ACLs by using webmin,actually what was there in the ACL is an empty DENY at the end of the ACLs,which i thought its something like EOF ,... after applying settings i got an error in that line,i managed to restore the squid.conf but no use! , squid keeps dying after starting
 
 From cache.log:
 
 
 2004/07/08 18:46:40| Starting Squid Cache version 2.4.STABLE7 for i686-pc-linux-gnu...
 2004/07/08 18:46:40| Process ID 1035
 2004/07/08 18:46:40| With 1024 file descriptors available
 2004/07/08 18:46:40| DNS Socket created on FD 4
 2004/07/08 18:46:40| Adding nameserver 10.10.10.12 from /etc/resolv.conf
 2004/07/08 18:46:40| logfileOpen: /var/log/squid: (21) Is a directory
 2004/07/08 18:46:40| Unlinkd pipe opened on FD 8
 2004/07/08 18:46:40| Swap maxSize 18058240 KB, estimated 1389095 objects
 2004/07/08 18:46:40| Target number of buckets: 69454
 2004/07/08 18:46:40| Using 131072 Store buckets
 2004/07/08 18:46:40| Max Mem  size: 8192 KB
 2004/07/08 18:46:40| Max Swap size: 18058240 KB
 2004/07/08 18:46:40| Rebuilding storage in /var/spool/squid (DIRTY)
 2004/07/08 18:46:40| Using Least Load store dir selection
 2004/07/08 18:46:40| Set Current Directory to /var/spool/squid
 2004/07/08 18:46:40| Loaded Icons.
 2004/07/08 18:46:40| Accepting HTTP connections at 0.0.0.0, port 8080, FD 10.
 2004/07/08 18:46:40| Accepting ICP messages at 0.0.0.0, port 3130, FD 12.
 2004/07/08 18:46:40| WCCP Disabled.
 2004/07/08 18:46:40| Ready to serve requests.
 2004/07/08 18:46:40| Store rebuilding is  0.3% complete
 FATAL: Received Segment Violation...dying.
 2004/07/08 18:46:41| Not currently OK to rewrite swap log.
 2004/07/08 18:46:41| storeDirWriteCleanLogs: Operation aborted.
 CPU Usage: 1.060 seconds = 0.630 user + 0.430 sys
 Maximum Resident Size: 0 KB
 Page faults with physical i/o: 439
 Memory usage for squid via mallinfo():
 total space in arena:   13669 KB
 Ordinary blocks:        13666 KB      1 blks
 Small blocks:               0 KB      0 blks
 Holding blocks:           952 KB      3 blks
 Free Small blocks:          0 KB
 Free Ordinary blocks:       3 KB
 Total in use:           14618 KB 107%
 Total free:                 3 KB 0%
 
 
 btw, squid keeps dying and starting for seconds (with different PIDs),then it die for good untill the next manual start
 
 plz help..
 
 cheerz
- 
				I hope ur squid has corrupt....
 
 You do onething....
 mv squid.conf squid.old
 and reinstall the squid by
 
 rpm -ivh --replacepckgs  squid*.*
 
 this will reinstall your squid
 then add ur rules in squid.conf
 and do the following
 
 squid -z
 
 this will solve ur problem
- 
				Hello..
 I havn't been in such problem bfore but I have its solution lying in my computer. Here is...
 -------------------
 Some versions of GCC (notably 2.95.1 through 2.95.3) have bugs with compiler optimization. These GCC bugs may cause NULL pointer accesses in Squid, resulting in a ``FATAL: Received Segment Violation...dying'' message and a core dump.
 
 You can work around these GCC bugs by disabling compiler optimization. The best way to do that is start with a clean source tree and set the CC options specifically:
 
 % cd squid-x.y
 % make distclean
 % setenv CFLAGS='-g -Wall'
 % ./configure ...
 
 To check that you did it right, you can search for AC_CFLAGS in src/Makefile:
 
 % grep AC_CFLAGS src/Makefile
 AC_CFLAGS       = -g -Wall
 
 Now when you recompile, GCC won't try to optimize anything:
 
 % make
 Making all in lib...
 gcc -g -Wall -I../include -I../include -c rfc1123.c
 ...etc...
 
 NOTE: some people worry that disabling compiler optimization will negatively impact Squid's performance. The impact should be negligible, unless your cache is really busy and already runs at a high CPU usage. For most people, the compiler optimization makes little or no difference at all.
- 
				Thank you! for ur replies, but the re-installation didnt solve the problem, neither the steps for the compiler optimization thingie!
 
 i think its something to do with memory,, but how?!!
 
 any help guys!! :(