Post-check for hardware and operating system setup was unsuccessful on all the nodes.
[grid@oel01 sshsetup]$ ./sshUserSetup.sh -user grid -hosts "oel01 oel02" -noPromptPassphrase
The output of this script is also logged into /tmp/sshUserSetup_2018-02-18-00-41-56.log
Hosts are oel01 oel02
user is grid
Platform:- Linux
Checking if the remote hosts are reachable
PING oel01.oracle.com (192.168.52.1) 56(84) bytes of data.
64 bytes from oel01.oracle.com (192.168.52.1): icmp_seq=1 ttl=64 time=0.065 ms
64 bytes from oel01.oracle.com (192.168.52.1): icmp_seq=2 ttl=64 time=0.075 ms
64 bytes from oel01.oracle.com (192.168.52.1): icmp_seq=3 ttl=64 time=0.065 ms
64 bytes from oel01.oracle.com (192.168.52.1): icmp_seq=4 ttl=64 time=0.061 ms
64 bytes from oel01.oracle.com (192.168.52.1): icmp_seq=5 ttl=64 time=0.062 ms
--- oel01.oracle.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.061/0.065/0.075/0.010 ms
PING oel02.oracle.com (192.168.52.2) 56(84) bytes of data.
64 bytes from oel02.oracle.com (192.168.52.2): icmp_seq=1 ttl=64 time=1.43 ms
64 bytes from oel02.oracle.com (192.168.52.2): icmp_seq=2 ttl=64 time=0.796 ms
64 bytes from oel02.oracle.com (192.168.52.2): icmp_seq=3 ttl=64 time=0.644 ms
64 bytes from oel02.oracle.com (192.168.52.2): icmp_seq=4 ttl=64 time=0.668 ms
64 bytes from oel02.oracle.com (192.168.52.2): icmp_seq=5 ttl=64 time=0.417 ms
--- oel02.oracle.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 0.417/0.791/1.432/0.343 ms
Remote host reachability check succeeded.
The following hosts are reachable: oel01 oel02.
The following hosts are not reachable: .
All hosts are reachable. Proceeding further...
The script will setup SSH connectivity from the host oel01.oracle.com to all
the remote hosts. After the script is executed, the user can use SSH to run
commands on the remote hosts or copy files between this host oel01.oracle.com
and the remote hosts without being prompted for passwords or confirmations.
NOTE 1:
As part of the setup procedure, this script will use ssh and scp to copy
files between the local host and the remote hosts. Since the script does not
store passwords, you may be prompted for the passwords during the execution of
the script whenever ssh or scp is invoked.
NOTE 2:
AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORY
AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TO THESE
directories.
Do you want to continue and let the script make the above mentioned changes (yes/no)?
yes
The user chose yes
User chose to skip passphrase related questions.
Creating .ssh directory on local host, if not present already
Creating authorized_keys file on local host
Changing permissions on authorized_keys to 644 on local host
Creating known_hosts file on local host
Changing permissions on known_hosts to 644 on local host
Creating config file on local host
If a config file exists already at /home/grid/.ssh/config, it would be backed up to /home/grid/.ssh/config.backup.
Removing old private/public keys on local host
Running SSH keygen on local host with empty passphrase
Generating public/private rsa key pair.
Your identification has been saved in /home/grid/.ssh/id_rsa.
Your public key has been saved in /home/grid/.ssh/id_rsa.pub.
The key fingerprint is:
da:96:e7:db:d8:74:4b:74:de:07:c1:db:89:9b:82:9a grid@oel01.oracle.com
The key's randomart image is:
+--[ RSA 1024]----+
| |
| . |
| o |
| .+.|
| S .+.o|
| o .. .o+.|
| . +....oo +|
| .oo =.o ..|
| E +.o . |
+-----------------+
Creating .ssh directory and setting permissions on remote host oel01
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR grid. THIS IS AN SSH REQUIREMENT.
The script would create ~grid/.ssh/config file on remote host oel01. If a config file exists already at ~grid/.ssh/config, it would be backed up to ~grid/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host oel01.
Warning: Permanently added 'oel01,192.168.52.1' (RSA) to the list of known hosts.
grid@oel01's password:
Done with creating .ssh directory and setting permissions on remote host oel01.
Creating .ssh directory and setting permissions on remote host oel02
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR grid. THIS IS AN SSH REQUIREMENT.
The script would create ~grid/.ssh/config file on remote host oel02. If a config file exists already at ~grid/.ssh/config, it would be backed up to ~grid/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host oel02.
Warning: Permanently added 'oel02,192.168.52.2' (RSA) to the list of known hosts.
grid@oel02's password:
Done with creating .ssh directory and setting permissions on remote host oel02.
Copying local host public key to the remote host oel01
The user may be prompted for a password or passphrase here since the script would be using SCP for host oel01.
grid@oel01's password:
Done copying local host public key to the remote host oel01
Copying local host public key to the remote host oel02
The user may be prompted for a password or passphrase here since the script would be using SCP for host oel02.
grid@oel02's password:
Done copying local host public key to the remote host oel02
cat: /home/grid/.ssh/known_hosts.tmp: No such file or directory
cat: /home/grid/.ssh/authorized_keys.tmp: No such file or directory
SSH setup is complete.
------------------------------------------------------------------------
Verifying SSH setup
===================
The script will now run the date command on the remote nodes using ssh
to verify if ssh is setup correctly. IF THE SETUP IS CORRECTLY SETUP,
THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH SHOULD NOT ASK FOR
PASSWORDS. If you see any output other than date or are prompted for the
password, ssh is not setup correctly and you will need to resolve the
issue and set up ssh again.
The possible causes for failure could be:
1. The server settings in /etc/ssh/sshd_config file do not allow ssh
for user grid.
2. The server may have disabled public key based authentication.
3. The client public key on the server may be outdated.
4. ~grid or ~grid/.ssh on the remote host may not be owned by grid.
5. User may not have passed -shared option for shared remote users or
may be passing the -shared option for non-shared remote users.
6. If there is output in addition to the date, but no password is asked,
it may be a security alert shown as part of company policy. Append the
additional text to the <OMS HOME>/sysman/prov/resources/ignoreMessages.txt file.
------------------------------------------------------------------------
--oel01:--
Running /usr/bin/ssh -x -l grid oel01 date to verify SSH connectivity has been setup from local host to oel01.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Sun Feb 18 00:42:50 IST 2018
------------------------------------------------------------------------
--oel02:--
Running /usr/bin/ssh -x -l grid oel02 date to verify SSH connectivity has been setup from local host to oel02.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Sun Feb 18 00:42:50 IST 2018
------------------------------------------------------------------------
SSH verification complete.
[grid@oel01 sshsetup]$
