Hi Amos,
Since last week, I am facing below issues and really want to resolve
it.While moving around and looking on Google, I found that some similar
post for below problem in 3.2. series also. Can you please comment on
below problem that is it open bug with 3.1 and 3.2 series ? Or is it
resolved in current 3.2 series?
Your inputs are highly appreciated.
BR
Ben
> Hi Kinkie,
>
> Thanks for your kind response. Please find the below more entries
> before and after FATAL error.
>
> What does it FATAL error says?
>
>
> 2012/10/19 15:22:24| clientProcessRequest: Invalid Request
> 2012/10/19 15:22:39| clientProcessRequest: Invalid Request
> 2012/10/19 15:23:03| clientProcessRequest: Invalid Request
> 2012/10/19 15:23:35| clientProcessRequest: Invalid Request
> 2012/10/19 15:24:51| clientProcessRequest: Invalid Request
> 2012/10/19 16:03:02| clientProcessRequest: Invalid Request
> 2012/10/19 16:07:03| clientProcessRequest: Invalid Request
> 2012/10/19 16:08:41| clientProcessRequest: Invalid Request
> 2012/10/19 16:11:04| clientProcessRequest: Invalid Request
> 2012/10/19 16:13:50| WARNING: swapfile header inconsistent with
> available data
> 2012/10/19 16:15:05| clientProcessRequest: Invalid Request
> 2012/10/19 16:17:51| WARNING: swapfile header inconsistent with
> available data
> 2012/10/19 16:19:06| clientProcessRequest: Invalid Request
> 2012/10/19 16:23:01| WARNING: swapfile header inconsistent with
> available data
> 2012/10/19 16:23:07| clientProcessRequest: Invalid Request
> 2012/10/19 16:24:59| clientProcessRequest: Invalid Request
> 2012/10/19 16:25:08| clientProcessRequest: Invalid Request
> 2012/10/19 16:26:07| clientProcessRequest: Invalid Request
> 2012/10/19 16:27:01| clientProcessRequest: Invalid Request
> 2012/10/19 16:27:08| clientProcessRequest: Invalid Request
> 2012/10/19 16:27:08| WARNING: swapfile header inconsistent with
> available data
> FATAL: Received Segment Violation...dying. <--
> 2012/10/19 16:27:08| storeDirWriteCleanLogs: Starting...
> 2012/10/19 16:27:08| WARNING: Closing open FD 21
> 2012/10/19 16:27:08| 65536 entries written so far.
> 2012/10/19 16:27:08| 131072 entries written so far.
> 2012/10/19 16:27:08| 196608 entries written so far.
> 2012/10/19 16:27:08| 262144 entries written so far.
> 2012/10/19 16:27:08| 327680 entries written so far.
> 2012/10/19 16:27:08| 393216 entries written so far.
> 2012/10/19 16:27:08| Finished. Wrote 410417 entries.
> 2012/10/19 16:27:08| Took 0.10 seconds (3937042.54 entries/sec).
> CPU Usage: 367.492 seconds = 212.301 user + 155.191 sys
> Maximum Resident Size: 6021760 KB
> Page faults with physical i/o: 1
> Memory usage for squid via mallinfo():
> total space in arena: 1361484 KB
> Ordinary blocks: 1361359 KB 308 blks
> search hit TOP, continuing at BOTTOM
> 2012/10/20 11:47:25| Finished rebuilding storage from disk.
> 2012/10/20 11:47:25| 819651 Entries scanned
> 2012/10/20 11:47:25| 0 Invalid entries.
> 2012/10/20 11:47:25| 0 With invalid flags.
> 2012/10/20 11:47:25| 819651 Objects loaded.
> 2012/10/20 11:47:25| 0 Objects expired.
> 2012/10/20 11:47:25| 0 Objects cancelled.
> 2012/10/20 11:47:25| 0 Duplicate URLs purged.
> 2012/10/20 11:47:25| 0 Swapfile clashes avoided.
> 2012/10/20 11:47:25| Took 2.04 seconds (402003.52 objects/sec).
> 2012/10/20 11:47:25| Beginning Validation Procedure
> 2012/10/20 11:47:26| Completed Validation Procedure
> 2012/10/20 11:47:26| Validated 1639327 Entries
> 2012/10/20 11:47:26| store_swap_size = 21508128
> 2012/10/20 11:47:26| storeLateRelease: released 0 objects
> 2012/10/20 11:47:31| WARNING: swapfile header inconsistent with
> available data
> FATAL: Received Segment Violation...dying. <--
> 2012/10/20 11:47:31| storeDirWriteCleanLogs: Starting...
> 2012/10/20 11:47:31| WARNING: Closing open FD 21
> 2012/10/20 11:47:31| 65536 entries written so far.
> 2012/10/20 11:47:31| 131072 entries written so far.
> 2012/10/20 11:47:31| 196608 entries written so far.
> 2012/10/20 11:47:31| 262144 entries written so far.
> 2012/10/20 11:47:31| 327680 entries written so far.
> 2012/10/20 11:47:31| 393216 entries written so far.
> 2012/10/20 11:47:31| 458752 entries written so far.
> 2012/10/20 11:47:31| 524288 entries written so far.
> 2012/10/20 11:47:31| 589824 entries written so far.
> 2012/10/20 11:47:31| 655360 entries written so far.
> 2012/10/20 11:47:31| 720896 entries written so far.
> 2012/10/20 11:47:31| 786432 entries written so far.
> 2012/10/20 11:47:31| Finished. Wrote 819742 entries.
> 2012/10/20 11:47:31| Took 0.18 seconds (4520395.05 entries/sec)
>
> Regards,
> Ben
>> Hi Ben,
>> in order to investigate we would need to know WHAT caused the
>> segment violation. Can you please paste the 20 lines BEFORE that
>> message in cache.log?
>>
>> Thanks
>>
>>
>> On Fri, Oct 19, 2012 at 8:13 AM, Ben <benjo11111_at_gmail.com> wrote:
>>> Hi Amos,
>>>
>>> Any suggestions please, I tested same setup with other 3.1.x
>>> releases and
>>> got same error messages from cache.log.
>>>
>>> what does this error message inform? Kindly guide us to resolve it.
>>>
>>>
>>> cat /var/log/squid/cache.log | grep -i fatal
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>> FATAL: Received Segment Violation...dying.
>>>
>>> BR
>>> Ben
>>>
>>>> Hi,
>>>>
>>>> I noticed one serious issue in squid, squid crashed and that time,
>>>> log
>>>> shows "FATAL: Received Segment Violation...dying.". what does it mean?
>>>>
>>>> Squid Cache: Version 3.1.19
>>>>
>>>> BR
>>>> Ben
>>>
>>
>>
>
Received on Sat Oct 20 2012 - 08:09:38 MDT
This archive was generated by hypermail 2.2.0 : Sun Oct 21 2012 - 12:00:09 MDT