6 Troubleshooting the Private Cloud Appliance
Oracle ZFS Storage Appliance Error Message
Problem: You may encounter a warning message in the agent log file about the Oracle ZFS Storage Appliance.
Resolution: This is a known issue. The warning message can be ignored. Typically, the message will look like this:
2015-05-15 13:06:04,896 [87:75FBA055] WARN - Can not evaluate push properties for target
oracle_si_zfssa_diskshelf_server_akcli.zfs1.example.com/akcli/1/diskshelf/chassis-001_akcli
for metric ComponentFaults - skipping this metric oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException:
Can't resolve a non-optional query descriptor property [MatchAgentAddr] (StorageServerIpAddress) at
oracle.sysman.gcagent.metadata.impl.PropertiesEvaluatorImpl$QueryPropsComputer.compute(PropertiesEvaluatorImpl.java:1013) at
oracle.sysman.gcagent.metadata.impl.PropertiesEvaluatorImpl$QueryPropsComputer.<init>(PropertiesEvaluatorImpl.java:859) at
oracle.sysman.gcagent.metadata.impl.PropertiesEvaluatorImpl.init(PropertiesEvaluatorImpl.java:346) at
oracle.sysman.gcagent.metadata.impl.PropertiesEvaluatorImpl.<init>(PropertiesEvaluatorImpl.java:210) at
oracle.sysman.gcagent.metadata.impl.TargetInstanceImpl.getPropertiesEvaluator(TargetInstanceImpl.java:1255) at
oracle.sysman.gcagent.target.interaction.execution.ReceiveletManager.addMetric(ReceiveletManager.java:344) at
oracle.sysman.gcagent.target.interaction.execution.ReceiveletInteractionMgr.addMetric(ReceiveletInteractionMgr.java:1446)
Targets Still Appear as Pending
Problem: After discovering the Oracle Private Cloud Appliance Rack, you may still see all SI targets are in Pending state.
Resolution: You must kill the stuck availability job in the OMS:
$ sqlplus sysman/sysman
SQL> SELECT job_subname, elapsed_time, cpu_used FROM dba_scheduler_running_jobs WHERE job_name = 'EM_REPOS_SEV_EVAL';
SQL> BEGIN dbms_scheduler.stop_job('EM_REPOS_SEV_EVAL'); COMMIT; END;
Import Component Step Failed for New VM Request
Problem: Import Component step failed for new VM request.
Resolution: In the OMS setup, determine the upload port, and update /etc/tinyproxy/tinyproxy.conf
file on both management nodes.
-
Get the
"HTTPS Upload Port"
for the OMS-
On OMS host, login using the OMS install user. Example:
oracle
-
$ emctl status oms -details -sysman_pwd <Sysman Password> | grep "HTTPS Upload Port"
-
-
Below the existing block of
ConnectPort
lines, add the following line by replacing the<yyyy>
with actual"HTTPS Upload Port"
to/etc/tinyproxy/tinyproxy.conf
file.=== ConnectPort <yyyy> ===
-
Restart tinyproxy (service tinyproxy restarts).
-
If you have a firewall enabled, add this port to the list of ports enabled using iptables and restart iptables service.
Error in Kubernetes as a Service Cluster Creation for Private Cloud Appliance 2.4.4 and Above
Problem: When creating a Kubernetes as a Service cluster the following error message appears: Error occurred while submitting your request. Contact your System Administrator for help.
- On the active management node enter the following command using the
oracle
user:/nfs/shared_storage/oemagent/agent_inst/bin/emctl setproperty agent -name preferIPv6Addresses -value false
- Restart the Agent.