MagicSpam & Cluster configuration
Posted: Fri Aug 06, 2010 6:45 am
Hello:
I'm currently having an issue with MagicSpam and my Cluster Manager. I have Mail Enable services registered with Cluster Manager but when MagicSpam updates at intervals 0, 6, 12, and 18, it stops and starts the SMTP service which causes the registered cluster resource to fail. When Cluster Manager sees this, it tries to restart the service. Sometimes that works but other times I get an error that says Mail Enable could not bind to my ip address and the service fails altogether. I suppose this is because the Cluster is trying to bring the serivce on while other tasks are using the port. At that point, my users can't send any emails and I get the support call.
So, I have be researching a way around it and have come up with the idea that I could write a bat file that takes the resource offline, calls the magicspam updater, then brings the resource online. However, when I test the bat file and call the magicspam updater, it takes at least a minute or 2 then comes back with a "null" message. Am I doing something wrong? I see where the schedule task is just calling the same file and that's all I'm doing in the bat file.
Any suggestions? I also see where Cluster Manager has a "mainteance" option switch. I researched Cluster Manager command line tools to get my command line options.
I'm currently having an issue with MagicSpam and my Cluster Manager. I have Mail Enable services registered with Cluster Manager but when MagicSpam updates at intervals 0, 6, 12, and 18, it stops and starts the SMTP service which causes the registered cluster resource to fail. When Cluster Manager sees this, it tries to restart the service. Sometimes that works but other times I get an error that says Mail Enable could not bind to my ip address and the service fails altogether. I suppose this is because the Cluster is trying to bring the serivce on while other tasks are using the port. At that point, my users can't send any emails and I get the support call.
So, I have be researching a way around it and have come up with the idea that I could write a bat file that takes the resource offline, calls the magicspam updater, then brings the resource online. However, when I test the bat file and call the magicspam updater, it takes at least a minute or 2 then comes back with a "null" message. Am I doing something wrong? I see where the schedule task is just calling the same file and that's all I'm doing in the bat file.
Any suggestions? I also see where Cluster Manager has a "mainteance" option switch. I researched Cluster Manager command line tools to get my command line options.