0% found this document useful (0 votes)
112 views2 pages

Cluvfy Fails When Non-Default SSH Port Used PRVF-4007 User Equivalence Check Failed For User (Doc ID 1533668.1)

The document describes an issue where the CVU command cluvfy fails when SSH is running on a non-default port. The cause is that the SSH config file is missing the port number that SSHD is running on. The solution is to add the port number to the .ssh/config file to resolve the user equivalence check failure.

Uploaded by

selfrit
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
112 views2 pages

Cluvfy Fails When Non-Default SSH Port Used PRVF-4007 User Equivalence Check Failed For User (Doc ID 1533668.1)

The document describes an issue where the CVU command cluvfy fails when SSH is running on a non-default port. The cause is that the SSH config file is missing the port number that SSHD is running on. The solution is to add the port number to the .ssh/config file to resolve the user equivalence check failure.

Uploaded by

selfrit
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Copyright (c) 2018, Oracle. All rights reserved.

cluvfy Fails When non-Default SSH port used: PRVF-4007 : User equivalence check failed for user
(Doc ID 1533668.1)

In this Document

Symptoms
Changes
Cause
Solution

APPLIES TO:

Oracle Database - Standard Edition - Version 11.2.0.1 and later


Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

SYMPTOMS

CVU command fails:

Checking user equivalence...


PRVF-4007 : User equivalence check failed for user "grid"
Check failed on nodes:
Node1

clucfy trace shows

[28919@Node1] [Thread-7] [ 2013-01-09 11:38:21.731 GMT ] [StreamReader.run:65] ERROR>ssh: connect to host


Node2 port 22: Connection refused
[28919@Node1] [Worker 3] [ 2013-01-09 11:38:21.731 GMT ] [RuntimeExec.runCommand:144] runCommand: process
returns 255

SSH is running on non default port number

CHANGES

Likely to be a new installation

CAUSE

SSHD is running on non-default port but SSH config file missing port number

SOLUTION

Add the port number to the .ssh/config file


Example here for port 2020
Host *
ForwardX11 no
Port 2020
Didn't find what you are looking for?

You might also like