This content has been marked as final. Show 15 replies
There isn't enough information here to debug the issue. Can you please file a Service Request(SR) with Oracle Support and send us the SR number?
We are having the same problem. Have you already found a solution for that?
I'm planning to open SR. But temporaly we don't have privilege to create SR, only knowledge base & patches. Oracle can't sell it for us because of their updates and changes
Thinking about using another system...
Which system do you think about? ;)
Seems as if the problem is related to sparc installations. Will open a SR soon.
Zabbix. It's open source & FREE!
We are having the same problem now too, also on SPARC Solaris, 64 bit
Can anyone confirm if the issue persists even after using the steps in Note 1427773.1: The Cloud Control Agent 12c Status Timeout / Connection refused / "security.pkcs11.P11SecureRandom.implNextBytes" ?
We are using Solaris 10 patch level 10 with the same problem. But I tried note 1427773.1 anyway. Maybe the bug still exists. Takes a couple of hours until the agent times out/crashes. I will report as soon as the problem occours again.
The agents have been running fine now for a about 5 hours. Maybe someone else could give it a try
I had to install 11g Grid Infrastructure to install ASM. So, i updated Solaris to latest release a week before and went to vacation.
I was really suprised when i saw this morning, than EM was still running.
Now it looks that the old Solaris release was the reason and the solution to update it really works.
Jim, which version of Solaris are you using?
Solaris 10 8/11
It was patched by latest patch cluster + latest 10_Recommended.
$ cat /etc/release
Solaris 10 8/07 s10s_u4wos_12b SPARC
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007
Solaris 10 8/11 (Update 10) Patchset applied.
$ uname -a
SunOS E29 5.10 Generic_147440-26 sun4u sparc SUNW,Netra-T12
On the one server with patch cluster + 10_Recomended problem was solved, but on another one - still exists.
I've got notifications
Agent is Unreachable (REASON = unable to connect to http server at https://dssinvdb01:3872/emd/main/. [peer not authenticated]). Host is unreachable (REASON = Unknown Error pinging the host of URL https://dssinvdb01:3872/emd/main/.1).
3 times per day. Agent is restarted ( emctl status agent > Started at is refreshed regulary )
This server has also Solaris 10 update 10 installed but i'm not sure that latest 10_recommended was aplied as on the first host.
You need to apply workaround 1505059.1
The problem is still there in some solaris 10 Update 10 releases. Applied the workaround on all of our servers and the agent is still running stable.