As it turns out the workaround doesn't work.
ASSP on my main relay restarted itself about an hour ago with the same
symptoms - two connections from the same IP within 1 second of each other.
When I looked in the logs to check I noticed:
2012-05-28 20:50:12 [startup] Error: calling CorrectASSPcfg.pm returned
error - Global symbol "$delaySameIPorHelo" requires explicit package
name at /usr/local/assp/lib/CorrectASSPcfg.pm line 39.
Compilation failed in require at (eval 41) line 1.
BEGIN failed--compilation aborted at (eval 41) line 1.
I presume I have either got the spelling wrong or need to declare the
variable before it takes effect.
So bad news for me getting it wrong, bad news for resolving the issue as
I am running 2.2.2(12149).
Is there anything else I can do to help track down the problem?
All the best,
Colin.
On 28/05/2012 19:22, Thomas Eckardt wrote:
> I try to fix that in every new release. Even if I do not hint in the
> change log.
>
> Colin, please do not use the workaround - it will work. Better use the
> latest version and report.
>
> Thomas
>
>
>
>
>
> Von: Colin<[email protected]>
> An: [email protected],
> Datum: 28.05.2012 17:15
> Betreff: Re: [Assp-test] Antwort: Assp crashes a cuple of times
> per day.
>
>
>
> I have a similar setup running - Ubuntu 12.04, Perl v5.14.2
>
> I have always had a couple of instances of ASSP bailing out a day and I
> posted a thread about it back in February. The issue has been brought
> back into focus with the recent upgrades addressing simultaneous
> connections and I have been meaning to post back my results.
>
> The upgraded version of ASSP that was meant to resolve the issue did not
> crash on me for approximately 24 hours but since then the crashes came
> back.
>
> I put $delaySameIPorHelo = 5; in lib/CorrectASSPcfg.pm and haven't had a
> single crash since.
>
> So, for the original poster - do your logs show two workers handling
> similar messages just prior to the crash? If so try the above workaround
> to see if your issue is the same as mine.
>
> For Thomas, the bad news at least on my part is that the fix that you
> put in the main code doesn't appear to have corrected the problem for
> me. If you have any other possible fixes I don't mind trying them out
> for you - we receive numerous frequent server monitoring alerts from our
> clients that come through the same or similar gateways so you can be
> guaranteed the problem will rear its head quickly.
>
> All the best,
> Colin Waring.
>
> On 27/05/2012 07:06, Thomas Eckardt wrote:
>>> Usally memory is all used out when it does
>> Tell me someting about the system hardware.
>>
>> Is this the case even if you
>>
>> use a database for all main hashes and lists
>> use BerkeleyDB for griplist , the internal hashes and the rebuild hashes
> ?
>> How is the memory usage? Do you use 64Bit or 32Bit Perl? Is the Perl
>> installation a distro package or self compiled from souce?
>> How many connections are handled per day?
>>
>>> Would activating "$main::enableCrashAnalyzer = 0;" give logs with
> useful
>> info?
>> This will only help if specific mails are crashing assp.
>>
>>> How do I crash-debug so I get good logs?
>> If perl gives assp the chance to get some infos about a crash, you'll
> find
>> the infos in 'exception.log'.
>>
>> Thomas
>>
>>
>>
>> Von: "Pontus Karlsson"<[email protected]>
>> An: "'ASSP development mailing list'"
>> <[email protected]>,
>> Datum: 25.05.2012 11:07
>> Betreff: [Assp-test] Assp crashes a cuple of times per day.
>>
>>
>>
>> Hi there!
>>
>> I now run ASSP version 2.2.2(12145) on Ubuntu 12.04 LTS and perl v5.14.2
>> which I would belive is the latest I can run.
>>
>> Due to reaccuring(2-3 times a day) crashes I have made upgrades on
>> everything (used to run on older Debian and older perl) but ASSP keep on
>> crashing.
>> I made a script which I run with cron every two minutes just to make
> sure
>> assp is allways running(if it's not I start it again).
>> I get no logs when it crashes it just stops running. Usally memory is
> all
>> used out when it does (but not the swap)
>> It's not really an acceptable solution to keep on restarting.
>>
>> So, question:
>> How do I crash-debug so I get good logs?
>> I have tried verbose (not debug) mode logging settings in assp. Lots of
>> logs with no useful extra info.
>> How much load would debug on all give -and- would it give the crash-info
> I
>> need?
>>
>> Would activating "$main::enableCrashAnalyzer = 0;" give logs with
> useful
>> info?
>> Or, is there a way right way to do this "hunt" to get things running
>> smooth and not crash.
>>
>> It crashes if I run it with a database or not, I have tried both to be
>> sure the database had nothing to do with it.
>>
>> Regards,
>> Pontus
>>
>>
>>
>>
> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
> Discussions
>> will include endpoint security, mobile security and the latest in
> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Assp-test mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>>
>>
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential,
> legally
>> privileged and protected in law and are intended solely for the use of
> the
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> *******************************************************
>>
>>
>>
>>
>>
> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
> Discussions
>> will include endpoint security, mobile security and the latest in
> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>
>>
>> _______________________________________________
>> Assp-test mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Assp-test mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Assp-test mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-test
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
