Thursday Oct 22, 2015

Ops Center Communication Issue with Some Java Versions

Some Ops Center users have run into an issue recently with certain Java versions on managed assets. Basically, if you upgrade to one of the problematic versions, it can disrupt communication between the different parts of Ops Center, causing assets to show as unreachable and jobs to fail.

The problem children are:

  • Java SE JDK and JRE 6 Update 101 or later

  • Java SE JDK and JRE 7 Update 85 or later

  • Java SE JDK and JRE 8 Update 51 or later

There's a simple workaround for this issue, which you can apply before or after you've hit the issue, which uses the OCDoctor script (by default, it's in the /var/opt/sun/xvm/OCDoctor/ directory).

On the EC, run the OCDoctor script with the --update option (the fix requires version 4.51 or later). Then run it again with the --troubleshoot and --fix options.

If you're using JDK 6, you then need to download a new Agent Controller bundle based on the version of Ops Center that you're using:

Finally, use the same OCDoctor options (--update, then --troubleshoot --fix) on the Proxy Controllers. This will either clear up the issue, or prevent it from appearing at all.

Thursday Jul 17, 2014

Java versions for Agents

I recently saw a question from the field regarding Agent installation:

"I'm trying to manage a group of servers with Ops Center. They use Java 1.5; is that going to be a problem?"

No, it shouldn't be. The Ops Center Agent uses Java 1.6, but it will install Java 1.6 if it's not already there. Java 1.5 and 1.6 can coexist on your systems. As long as Ops Center can get to Java 1.6 in the default location, it should work fine.

About

This blog discusses issues encountered in Ops Center and highlights the ways in which the documentation can help you

Search

Archives
« June 2016
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
  
       
Today