default shell error

dheeraj_thampy · December 2013

Hi ,
I am tryng to install vertica 7
os is RH 6.4
3 nodes

when i run the install_vertica script, it throws the following error

Error: Default shell on the following nodes are not bash. Default shell must be set to bash.
<ip> for <user>:
<ip2> for <user>:
Exiting...
Installation FAILED with errors.

Installation stopped before any changes were made.

I double checked the bash details..the users in both nodes have /bin/bash as their default shell
anything else i need to check

kindly help

Rahul_Choudhary · December 2013

Hi Dheeraj

In order to fix this issue kindly perform below changes

Note: Please perform below action on all the nodes.

# We run sudo commands over ssh, comment out the requirement that user needs to have a tty in order to run sudo commands # in /etc/sudoers, comment out the following line Defaults requiretty # or add the following line and exempt the dbadmin from tty Defaults:dbadmin !requiretty

# This may also be necessary, configure sudo to either # (a) not ask for password, in /etc/sudoers dbadmin ALL=(ALL) NOPASSWD: ALL #OR (b) be prompted for a password dbadmin ALL=(ALL) PASSWD: ALL

Kindly restart database installation afresh once again after making the above changes.

Regards
Rahul Choudhary

Daniel_Leybovic · December 2013

Hi!

What is output of:

 echo $SHELL

dheeraj_thampy · December 2013

Hi Rahul..
thanks for the quick reply , but that dint work out fr me ...

@Daniel
it gives me /bin/bash on all the nodes

dheeraj_thampy · December 2013

Hi Rahul,
It worked for me...actually u wer right,..
i had to give the username of the sudo user instead of the dbadmin user (the second solution)

in /etc/sudoers

<sudo user> ALL=(ALL) NOPASSWD: ALL

Thanks a lot friend

Andrew_1 · January 2014

Hi,

I have a similar issue on Ubunutu 12.04.

Do you have a fix please?

Cheers
Andy

Daniel_Leybovic · January 2014

Check this: https://community.vertica.com/vertica/topics/vertica_7_nonetype_object_is_not_subscriptable_on_creat...

Check that loopback address defined as 127.0.0.1 and not 127.0.1.1

Andrew_1 · January 2014

Thanks but I don't even get that far, I am installing a 3 node cluster and get the following when running the install_vertica script

when i run the install_vertica script, it throws the following error

Error: Default shell on the following nodes are not bash. Default shell must be set to bash.
<ip> for <user>:
<ip2> for <user>:
Exiting...
Installation FAILED with errors.

Installation stopped before any changes were made.

Cheers

[Deleted User] · January 2014

Hi Andrew,

Did Rahul's fix work for you? (Did you test it to make sure that sudo is working properly if you ssh into those nodes manually?)

If not, are you sure you have your shell set to bash? Check both your dotfiles and the default in /etc/passwd .

If it's still not working, take a look at the installer log (in /opt/vertica/log/) and see if there's any more detail there.

Adam

Andrew_1 · January 2014

Thanks Adam,

Yes I have tried Rahul's fix and can confirm that sudo is working properly when I ssh onto the nodes.

I have set default in /etc/passwd on all nodes, which dotfiles are you refering to?

Cheers
Andy

[Deleted User] · January 2014

I was thinking of ~/.bashrc, ~/.profile, etc.; the dotfiles that get run at login and that might set up the environment in a strange way in some cases.

That does seem somewhat unlikely, though... I'd also suggest checking the installer log file to see if it says anything interesting.

Adam

Andrew_1 · January 2014

Have checked the dotfiles and nothing looks out of place.

Also have checked through the logs, there is no message log and cant see anything syslog, is there a log that the installation of vertica writes to?

Something must be causing the default shell to be changed when the installer runs......

Cheers
Andy

[Deleted User] · January 2014

Per my previous comment, check out /opt/vertica/log/ . Let us know if there's anything interesting there.

Thanks,
Adam

Andrew_1 · January 2014

Sorry, yes you did say and I did look before, there is nothing that I can see to be honest.

Any other ideas.

Thanks
Andy

Andrew_1 · January 2014

Just if it help, here are the details from the log

Jan 15 17:28:32 [adminExec.__init__] Unique Ports: False

Jan 15 17:28:32 <BashAdapter: dbadmin@10.0.0.8 sudo>: <command hidden>

Jan 15 17:28:32 <PexpectAdapter: dbadmin@10.0.0.4>: login start: ssh -oConnectTimeout=30 -o TCPKeepAlive=no -o ServerAliveInterval=15 -o ServerAliveCountMax=2 -l dbadmin 10.0.0.4

Jan 15 17:28:39 <PexpectAdapter: dbadmin@10.0.0.5>: login start: ssh -oConnectTimeout=30 -o TCPKeepAlive=no -o ServerAliveInterval=15 -o ServerAliveCountMax=2 -l dbadmin 10.0.0.5

Jan 15 17:28:42 <PexpectAdapter: dbadmin@10.0.0.5>: [ -f /etc/fedora-release ]

Jan 15 17:28:42 <PexpectAdapter: dbadmin@10.0.0.4>: [ -f /etc/fedora-release ]

Jan 15 17:28:42 <BashAdapter: dbadmin@10.0.0.8 sudo>: ['[ -f /etc/fedora-release ]']