Opscenter 6.0 Start up issue

Question

Yesterday, I tried to install opscenter and initiated import of existing DSE 5.0 cluster. It failed with certain errors which pointed out that installed version was not opscent

Answer 1

I also met the same problem. But opscenter 6.0 cannot start using the solution above.

Checking out the support platfrom list, I think it is because my os is CentOS 6.2, which is not in the support list.

So I just use version 5.2 and it works fine.

Answer 2

I have found the root cause and resolution to opscenter 6.0 startup problem.

Root Cause - /tmp folder of My RHEL machine is mounted witn noexec permissions.
----------

Logs were not providing any clue around this. I installed opscenter 6.0 on a virtual machine and its all working so it encouraged me to find the difference between two env. I zeroed down on /tmp folder is noexec and permission issues causing opscenter terminating at startup.

Solution - Setting explicitly a tmp directory for opscenter.

---

Set explicitly java temp directory for opscenter in JVM arguments e.g. Set -Djava.io.tmpdir=/usr/share/opscenter/tmp.

For RPM based installation
1. sudo vi /usr/share/opscenter/bin/opscenter
2. Add java temp directory parameter to JVM options
OPSC_JVM_OPTS="-server -Xmx1024m -Xms1024m -XX:MaxPermSize=128m -Dpython.cachedir.skip=false -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC
-XX:+CMSParallelRemarkEnabled -XX:+ScavengeBeforeFullGC -XX:+CMSScavengeBeforeRemark -verbose:gc
-XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCCause
-XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5
-XX:GCLogFileSize=1M -Xloggc:$OPSC_GC_LOG_PATH/gc.log
-Djava.io.tmpdir=/usr/share/opscenter/tmp
$OPSC_JVM_OPTS"