I'm using EM12cR2 on Solaris SPARC. EM agent 18.104.22.168.0 became to crash after 2 days network subnet was changed.
How occurs the problem:
1. I started agent
2. After few hours i got a notification
Message=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. After 10..30 mins i got notification that agent became up again.
4. steps 2-3 occured few times per day.
5. After few hours or days agent became unreachable for keeps and didn't restart
./emctl status agent gets the following:
Status agent Failure:unable to connect to http server at https://dssinvdb01:3872/emd/lifecycle/main/. [peer not authenticated]
Agent is Not Running
$ps -ef | grep agent
oracle 21236 1 0 окт. 25 ? 0:53 /u01/app/oracle/agent12c/core/22.214.171.124.0/perl/bin/perl /u01/app/oracle/agent12c
oracle 24472 21236 0 окт. 28 ? 11:34 /u01/app/oracle/agent12c/core/126.96.36.199.0/jdk/bin/sparcv9/java -Xmx128M -XX:MaxP
Others agents on other hosts don't have such issue.
I checked logs of EM agent and didn't found any essential errors.
I totally cleared (deinstalled & removed all files) and installed fresh agent binaries on that host. But it also didn't help.
Ntp clients configured...
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...
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.
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.
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.