6.1.2 fails to install on 2 node setup redhat 6

DwayneBerry

6.1.2 fails to install on 2 node setup Getting following error when trying to install the 6.1.2 installation (vertica-6.1.2-0.x86_64.RHEL5.rpm) the previous vertica-ce-6.0.1-0.x86_64.RHEL5.rpm installed just fine the error I am seeing is : [root@cnode1 Downloads]# /opt/vertica/sbin/install_vertica -s cnode2 -r /home/user/Downloads/vertica-6.1.2-0.x86_64.RHEL5.rpm Vertica Analytic Database 6.1.2-0 Installation Tool NOTICE: Adding previously-defined cluster host(s) to update check: 203.18.18.111 Starting installation tasks... Getting system information for cluster (this may take a while).... backing up admintools.conf on 203.18.18.111 Default shell on nodes: 203.18.18.112 /bin/bash 203.18.18.111 /bin/bash Installing rpm on 1 hosts.... installing node.... 203.18.18.112 Error: invalid literal for int() with base 10: '8%' Traceback (most recent call last): File "/opt/vertica/bin/verticaInstall.py", line 1232, in code, result = SSH.installNode( installerSSH, host, rootPassword, options.rpm_file_name, localhost, running_as ) File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/network/SSH.py", line 1986, in installNode if int(data[1][0]) < sz: ValueError: invalid literal for int() with base 10: '8%' Installation failed. [root@cnode1 Downloads] thanks

Jason_Blais

you've stumbled over a bug in that the df command used in the test ended up line wrapping because of the length of volume group where /tmp is located. I've filed a issue internally. Fortunately, the file /opt/vertica/oss/python/lib/python2.7/site-packages/vertica/network/SSH.py is readable and you can apply a workaround manually to move forward until we are able to push out the fix. The workaround is to simply add the POSIX output flag for portability to the df command in the test. Edit /opt/vertica/oss/python/lib/python2.7/site-packages/vertica/network/SSH.py on cnode1 and goto line 1982. Change the command: df /tmp | tail -1 | awk '{print $4}' to df -P /tmp | tail -1 | awk '{print $4}' save and rerun the installer from cnode1.

DwayneBerry

thank you That fixed the problem nicely

Venkat_Penmetsa

Is this issue fixed in any of the latest releases of Vertica?

Jason_Blais

This issue was fixed in versions of vertica 6.1.X and higher released after June 2013