Re: Itm 6.3 FP 2

John Alvord <jalvord-r/[email protected]> Thu, 26 Sep 2013 07:24:40 -0700
Newsgroups gmane.comp.sysutils.tivoli.general,gmane.comp.sysutils.tivoli.tme10
Message-ID <OF9C04AF7D.726D7188-ON88257BF2.004EF672-88257BF2.004F2A0E@us.ibm.com>
You can speed the diagnostic process by getting a core for the TEMS 
failure and sending pdcollect and core [if AIX snapcore].

There are an amazing number of times where customers started the PMR with 
that data and gotten a rapid resolution. 

Regards, 
______________________________________________


John Alvord
Advisory Engineer
IBM Tivoli Monitoring 6 Platform
Customer Support 
Office: 1-720-396-2788 
Mobile: none 
jalvord-r/[email protected]

Cloud & Smarter Infrastructure
IBM Support Portal
Open a New Service Request
Update your PMR via Email
Escalate your PMR
My Blog: Wonderful World of Situations
Secure upload to ECUREP







From:   kalpesh parmar <[email protected]>
To:     "Discussion list for Tivoli product and Tivoli Ready products." 
<[email protected]>, 
Date:   09/26/2013 07:09 AM
Subject:        Re: [TME10] Itm 6.3 FP 2
Sent by:        [email protected]




Julius,

Below lines from install capture ? upgrading TEMS using installer ? Seed 
option is selected and TEMS was started by installer script before seeding 
but it crashed and all the seeding failed.
??
Following Tivoli Enterprise Monitoring Server product support were 
installed:
*) Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint
*) Warehouse Proxy
*) Monitoring Agent for i5/OS
*) Monitoring Agent for UNIX OS
*) Monitoring Agent for Windows OS
*) Tivoli Performance Analyzer
*) Tivoli Enterprise Monitoring Server
*) Summarization and Pruning Agent
*) Monitoring Agent for UNIX Logs
*) Universal Agent
*) Agentless Monitoring for Windows Operating Systems
*) Monitoring Agent for Linux OS
*) Agentless Monitoring for AIX Operating Systems
*) Agentless Monitoring for Linux Operating Systems
*) Agentless Monitoring for HP-UX Operating Systems
*) Agentless Monitoring for Solaris Operating Systems
 
Note: This operation causes the monitoring server to restart.
Do you want to seed product support on the Tivoli Enterprise Monitoring 
Server? [ 1=Yes, 2=No ; default is "1" ] ? 1
Starting TEMS...
TEMS started...
 
[TEMS Crashed after 10 Seconds] and subsequent seeding failed.

Thanks and Regards
Kalpesh Parmar



Thanks and Regards
Kalpesh parmar



On Thu, Sep 26, 2013 at 6:58 PM, Julius Loman <[email protected]> wrote:
I have one here (32-bit standalone, RHEL 6), that does not crash (or does 
not seem to
be crasing), but it's a lab environment only. It's already running fine 
for few days.
When does your TEMS crash? any special circumstances?

On Thu, Sep 26, 2013 at 05:24:27PM +0530, kalpesh parmar <
[email protected]> wrote:
> Mine on RHEL 5.3 32 bit and it is standalone.
>
> Thanks and regards
> Kalpesh Parmar
>
>
> On Thu, Sep 26, 2013 at 4:52 PM, Julius Loman <[email protected]> wrote:
>
> > On Thu, Sep 26, 2013 at 07:19:08AM -0400, Jay Slay <[email protected]>
> > wrote:
> > > I haven't actually.  It is my test environment and I haven't had the
> > time to track it down as of yet.  My logs look similar to yours.  Its
> > probably worth a PMR.
> > Which platform is your tems running on?
> > > On Sep 26, 2013, at 7:14 AM, kalpesh parmar <
[email protected]>
> > wrote:
> > >
> > > > Hello jay,
> > > >
> > > > Did you manage to get solution of the TEMS crashing. My TEMS is 
also
> > crashing after upgrade to ITM 6.3.0 FP 02 from ITM 6.3.0.
> > > >
> > > > Last words from TEMS before it dies...
> > > >
> > > > Thu Sep 26 06:20:56 2013 KO4SRV017  Tivoli Enterprise Monitoring
> > Server (TEMS) shutdown in progress.
> > > > Thu Sep 26 06:20:56 2013 KO4SRV018  Stopping Tivoli Enterprise
> > Monitoring Server (TEMS) situation monitor.
> > > > Thu Sep 26 06:20:56 2013 KO4SRV105  Send to ksmoms failed.
> > > > Thu Sep 26 06:20:56 2013 KO4SRV020  Stopping Tivoli Enterprise
> > Monitoring Server (TEMS) data collection server.
> > > > Thu Sep 26 06:20:56 2013 KO46263    Tivoli Enterprise Monitoring
> > Server (TEMS) data queue error was detected.
> > > > Thu Sep 26 06:20:56 2013 KO4SRV033  Tivoli Enterprise Monitoring
> > Server (TEMS) no longer active.
> > > >
> > > >
> > > > Thanks and regards
> > > > Kalpesh Parmar
> > > >
> > > >
> > > >
> > > > On Sat, Sep 21, 2013 at 1:06 AM, Jay Slay <[email protected]> 
wrote:
> > > > Anyone upgrade yet?   I upgraded yesterday and haven't been able 
to
> > keep the TEMS alive.  Just wondering if anyone else is sailing smooth
> > before I look around.
> > > >
> > > > -JKS
> > > >
> > > >
> > > > _______________________________________________
> > > > TME10 mailing list
> > > > [email protected]
> > > > Unsubscribe:[email protected]
> > > >
> > > >
> > > > _______________________________________________
> > > > TME10 mailing list
> > > > [email protected]
> > > > Unsubscribe:[email protected]
> > >
> >
> > > _______________________________________________
> > > TME10 mailing list
> > > [email protected]
> > > Unsubscribe:[email protected]
> >
> >
> > --
> >
> > [ Julius Loman ][ [email protected] ][ http://lomo.kyberia.net ][
> > icq:35732873 ]
> >
> >
> > _______________________________________________
> > TME10 mailing list
> > [email protected]
> > Unsubscribe:[email protected]
> >
> >

> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]


--

[ Julius Loman ][ [email protected] ][ http://lomo.kyberia.net ][ 
icq:35732873 ]


_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]