Using build 12090, it went down again Monday and Tuesday, leaving these
lines in debugSignal.txt:
Apr-16-12 11:30:13 warning: got unexpected signal SEGV in Worker_1:
package - main, file - assp.pl, line - 21998!
Apr-17-12 18:14:02 warning: got unexpected signal SEGV in Worker_2:
package - main, file - assp.pl, line - 21998!
Changed to 2.1.2 build 12109 and it went down a couple times again
today, with the following lines in debugSignal.txt
Apr-19-12 15:14:10 warning: got unexpected signal SEGV in Worker_1:
package - main, file - assp.pl, line - 22132!
Apr-19-12 15:51:01 warning: got unexpected signal SEGV in Worker_3:
package - main, file - assp.pl, line - 22132!
Looking in assp.pl, they are actually the same line
Build 12090
21997 if ($re ne 'bombSubjectRe' or ($re eq 'bombSubjectRe' &&
$weightsum < $bombMaxPenaltyVal)) {
21998 while (&sigoffTry(__LINE__) && $text =~ /($regex)/gs) {
Build 12109
22131 if ($re ne 'bombSubjectRe' or ($re eq 'bombSubjectRe' &&
$weightsum < $bombMaxPenaltyVal)) {
22132 while (&sigoffTry(__LINE__) && $text =~ /($regex)/gs) {
Does this give anyone a clue as to where or what I should change?
Thanks
On 04/16/2012 11:17 AM, Tim Jacob wrote:
> Actually it stopped more often with that build than the "stable" one,
> so I went back to 12090.
>
> On 04/16/2012 8:50 AM, Pascal Dreissen wrote:
>> Upgrade, there was an issue with SSLTIMEMOUT in the 12090 version!
>>
>> fixed in assp 2.1.2 build 12103:
>>
>> - the too high default value of 'SSLtimeout' caused possibly stucking
>> workers and unexpected restarts of assp
>> (read the changed section for further information)
>>
>>
>>
>> Op 16 apr. 2012, om 13:47 heeft Colin het volgende geschreven:
>>
>>> Look at what happens immediately prior to the end of the log. It isn't
>>> always the last thing logged but I have found on a couple of occasions
>>> that a particular server or message has caused ASSP to bail out. It is
>>> normally pretty obvious once you start comparing a number of different
>>> examples. I haven't had it happen for a long time though.
>>>
>>> I also have a script that polls ports 25 and 55555 every five minutes.
>>> If there is no response it restarts ASSP so something like that may be
>>> of use?
>>>
>>> All the best,
>>> Colin.
>>>
>>> On 16/04/2012 11:21, Tim Jacob wrote:
>>>> I am running version 2.1.1(12090) on two separate Linux boxes (SLES v10
>>>> sp4) using Postfix as the MTA
>>>>
>>>> ASSP just stops working 2 or 3 times a day on both - but not at the same
>>>> time, and I have to restart them manually.
>>>>
>>>> I cannot find any rhyme or reason to the stoppages. Can anyone point me
>>>> to a log file that might give me a clue?
>>>> Does not seem to be in ASSP's logs, or Postfix. Just that it was
>>>> running, and now isn't.
>>>>
>>>> Any help would be appreciated.
>>>> Thanks,
>>>> Tim Jacob
>>>>
>>>> ------------------------------------------------------------------------------
>>>> For Developers, A Lot Can Happen In A Second.
>>>> Boundary is the first to Know...and Tell You.
>>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>>> _______________________________________________
>>>> Assp-test mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>> ------------------------------------------------------------------------------
>>> For Developers, A Lot Can Happen In A Second.
>>> Boundary is the first to Know...and Tell You.
>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>> _______________________________________________
>>> Assp-test mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> Assp-test mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>
> --
> # Jolly Farmer: Tim Jacob
> # Email: [email protected] <mailto:[email protected]>
> # Website: www.jollyfarmer.com <http://www.jollyfarmer.com>
> # Phone: 506-325-3850
> <http://www.jollyfarmer.com/greenhouse/greenhousecontact.html>
> # 56 Crabbe Rd | Northampton, NB E7N 1R6
>
> "Integrity, Quality, & Reliable Service Since 1967"
>
--
# Jolly Farmer: Tim Jacob
# Email: [email protected] <mailto:[email protected]>
# Website: www.jollyfarmer.com <http://www.jollyfarmer.com>
# Phone: 506-325-3850
<http://www.jollyfarmer.com/greenhouse/greenhousecontact.html>
# 56 Crabbe Rd | Northampton, NB E7N 1R6
"Integrity, Quality, & Reliable Service Since 1967"
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
