Comments on: Strange behavior when patching GI/ASM https://www.dbi-services.com/blog/strange-behavior-when-patching-giasm/ Fri, 17 May 2024 12:41:37 +0000 hourly 1 By: Clemens Bleile https://www.dbi-services.com/blog/strange-behavior-when-patching-giasm/#comment-3264 Fri, 17 May 2024 12:41:37 +0000 https://www.dbi-services.com/blog/strange-behavior-when-patching-giasm/#comment-3264 In reply to Seb.

Thanks Seb, appreciate your info.
Regards
Clemens

]]> By: Seb https://www.dbi-services.com/blog/strange-behavior-when-patching-giasm/#comment-3221 Tue, 23 Apr 2024 09:45:59 +0000 https://www.dbi-services.com/blog/strange-behavior-when-patching-giasm/#comment-3221 Hi,
I’ve encountered this behaviour too, when applying fix for 36114443: at some point opatchauto runs following command:
/bin/ssh -o FallBackToRsh=no -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o […] ls

When /root/.ssh/know_hosts on other node does not exist or contains no reference to the other node part of the cluster, it returns failure code 1, but *also and at the same time* updates known_hosts (msg “Warning: permanently added ‘host,IP address’ to the list of known hosts” is displayed), so re-running opatchauto again right away works…

To anticipate and prevent further opatchauto failures we’ve updated all our .ssh/known_hosts files under /root on machines that are cluster members, and since then didn’t meet this problem any longer.

]]>