OK, I had a look through the assp.pl code to see what could cause the
"not healthy" state, and saw it was related to threads. So I watched
my thread monitor and saw that threads are getting taken out one by
one by attempts by ASSP to work with database tables. An example, I see this:
Worker loop age current action
3 307s Whitelist
[email protected],[email protected],delete (stuck)
Looking at my whitelist table, I see an entry for
"[email protected],[email protected]" with a pvalue of
11336758832. There are no issues with the database, I'm able to
manipulate data with no problems or delays. I'm not quite sure why
the threads are getting stuck trying work with the database, but it
seems to be happening quite regularly.
Where do I go from here?
At 01:32 PM 5/11/2012, Scott MacLean wrote:
>12130 is exhibiting the same behavior, I've gone back to 12126 to see
>if it fixes it. However, looking at my watchdog process I see that
>after several minutes of operation, it starts reporting itself as
>"not healthy" - what state/error causes this?
>
>ASSP Proxy Uptime | 0.005 days | 70.675 days
>Messages Processed | 215 (41006.6 per day) | 1369039 (19371.0 per day)
>Non-Local Mail Blocked | 28.2% | 46.7%
>CPU Usage | 43.41% (11.55% avg) | 100.02% avg
>Concurrent SMTP Sessions | 1 (10 max) | 131 max
>Current healthy status | not healthy
>
>While watching the status, it suddenly stopped responding to any port
>again, it has locked up again - CPU usage is at 0%. Obviously the
>problem is not related to specific versions, as it's now happening on
>three different versions. I'm at a bit of a loss, and my users are
>screaming, as I can't keep the SMTP up and running for more than 10
>minutes at a time.
>
>
>At 12:48 PM 5/11/2012, Scott MacLean wrote:
>
> >I installed 2.1.2(12131) this morning. I had a notification of people
> >having problems sending mail, so I had a look to see what was going
> >on. Every 10-15 minutes, ASSP was locking up. There was nothing
> >consistently logged before the lockups (just normal operation), and
> >when it stopped functioning, it stopped responding on every port -
> >SMTP, stat, health, etc. My watchdog process would reset ASSP after
> >two minutes of no response, and it would run for another 10-15
> >minutes before locking up again.
> >
> >I've reverted to build 12130 for now.
> >
> >
> >
> >-------------------------------------------------------------------
> -----------
> >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
------------------------------------------------------------------------------
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
