Hi Warren,
I am curious when you "upgrade" to version 9. Did you really go through the
upgrade steps or you went new instance and cut over? I ask this because we
are also consider version 9. We are on 7.6.04.

On Wednesday, January 20, 2016, Warren R. Baltimore II <
warrenbaltim...@gmail.com> wrote:

> **
> Thanks for the replies everyone!  Sorry I didn't get back sooner.
>
> I spent quite a long time on the phone yesterday with Dolly from BMC.
> What we discovered was that while my email servers were coming up, the
> primary was not moving into an Active State, instead they were all in a
> Waiting state.
>
> We manually moved them to Active, and the primary one started functioning.
>
> We then made a change to the server and restarted the service, and it went
> back to waiting.  Dolly has my log files and is working with Engineering to
> find out what the cause might be.  In the meantime, I know now what is
> wrong and can take some easy steps to ensure it stays up and running until
> we find out how to fix the issue.
>
> On Tue, Jan 19, 2016 at 12:36 AM, Walunjkar, Parshuram <
> parshuram_walunj...@bmc.com
> <javascript:_e(%7B%7D,'cvml','parshuram_walunj...@bmc.com');>> wrote:
>
>> **
>>
>> Warren,
>>
>> By looking your logs your email engine is up and running correctly.
>>
>>
>>
>> After 9.0 all Email Engines are running in server group env, and
>> following the service failover i.e sharing email engine load among them.
>>
>>
>>
>> You can follow the docs for more information about service failover.
>>
>>
>> https://docs.bmc.com/docs/display/public/ars9000/Email+engine+service+failover+in+a+server+group
>>
>>
>>
>> let me  know if you required any help.
>>
>> Hope this will help you.
>>
>>
>>
>> --Parshram
>>
>>
>>
>> *From:* Action Request System discussion list(ARSList) [mailto:
>> arslist@ARSLIST.ORG <javascript:_e(%7B%7D,'cvml','arslist@ARSLIST.ORG');>]
>> *On Behalf Of *Warren R. Baltimore II
>> *Sent:* 18 January 2016 10:21 PM
>> *To:* arslist@ARSLIST.ORG
>> <javascript:_e(%7B%7D,'cvml','arslist@ARSLIST.ORG');>
>> *Subject:* Email Service is non functioning after upgrade to 9.0.01
>>
>>
>>
>> **
>>
>> First, the technical stuff.
>>
>> AREmail is running on a MS Server 2008 SP2 (Virtual)
>>
>> We upgraded from ARS 7.6.04 to 9.0.01 in a 3 app server environment.
>>
>> Email is only currently running on one of the 3 app servers
>>
>> Java JRE is 8u66
>>
>> The Email service comes up, and the email log and email.lck file is
>> created...
>>
>> And then nothing.  We've checked the email_daemon.properties file, and it
>> looks good.
>>
>> Here is the log file.
>>
>> <EML> /* Mon Jan 18 2016 11:26:09.969 */ Application has started Version:
>> 9.0.01 201508191530
>> <EML> /* Mon Jan 18 2016 11:26:09.969 */ Checking connection to server:
>> ESA-REMAPP01.[ServerDomain] ...
>> <EML> /* Mon Jan 18 2016 11:26:09.969 */ Using RMI Port xxxx
>> <EML> /* Mon Jan 18 2016 11:26:09.970 */ Using JRE: 1.8.0_66
>> <EML> /* Mon Jan 18 2016 11:26:11.843 */ Successfully connected at Jan
>> 18, 2016 11:26:11 AM
>> <EML> /* Mon Jan 18 2016 11:26:38.893 */ Email Engine asserting waiting
>> state for provider:[com.bmc.arsys.emaildaemon://incoming/AR_Incoming]
>> <EML> /* Mon Jan 18 2016 11:26:38.894 */ Email Engine asserting waiting
>> state for provider:[com.bmc.arsys.emaildaemon://outgoing/ARSystem_Out]
>>
>> I've removed the domain name and rmi port for security reasons.
>>
>> Any help you can provide would be most appreciated.  We're supposed to go
>> live this afternoon, and we have to get email up!
>>
>> --
>>
>> Warren R. Baltimore II
>> Remedy Developer
>> 410-533-5367
>>
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>>
>
>
>
> --
> Warren R. Baltimore II
> Remedy Developer
> 410-533-5367
> _ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to