. . .
My IO system (in an ESX server) for assp is designed as follows.
- LSI high performance SAS-CTL with 256 MB Cache
- 6 disks each with 10Krpm in a RAID10
--
P.P.P.S.
> We're a small business
I strongly recommend the use of virtualization ( Hyper-V / XEN / ESX / etc.) ,
especially f
Thomas
Saw the reply on the website, and for some reason, am not seeing my post
nor any replies via e-mail, so this is a quick test e-mail while I'm at it.
The system only has dual core, but should have plenty of memory, and the
local DNS server addresses, plus several remote (ie: OpenDNS) are
> ...
> Mar-20-2012 19:09:31 [Worker_1] Error: MainThread stuck for 64
> seconds after: MainLoop get the best worker = 1 (0 sockets) - last
> debug step was: servicecheck!
> ...
same here, workers seem to get "stuck" after a while; had to rollback
ASSP to "12058" to fix the issue otherwise, a
Got Assp v2 up and moving and now I've got these errors popping up
pretty regularly after a few minutes of starting
The keyfile and certfile are the same from Assp v1, so they should be
ok. and I can send mail through the SSL port, but random messages not
coming through could lead to problems
Ok, got V2 up and running, but I have errors such as in the subject (log
snippet below) showing up pretty regularly now.
The key and cert file are fine (same as from v1) and I can mail through
my Thunderbird on SSL without a problem, but I'm nervous that one of the
missed messages may actually
