You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Suresh Subbiah (JIRA)" <ji...@apache.org> on 2015/08/27 15:58:45 UTC

[jira] [Commented] (TRAFODION-1155) LP Bug: 1442777 - traf_config_setup does not get node list so install fails

    [ https://issues.apache.org/jira/browse/TRAFODION-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716704#comment-14716704 ] 

Suresh Subbiah commented on TRAFODION-1155:
-------------------------------------------

This isn't quite a valid situation. While its true the trafodion_config file would not exist on a fresh install, the trafodion userid would not also and in this case the trafodion userid exists. Does it work correctly when both the trafodion_config and trafodion userid are removed as would be the case on a fresh install?

Amanda Moran (amanda-kay-moran) on 2015-04-13
Changed in trafodion:
status:	New → Fix Committed
Joshua Liu (yao-hua-liu) wrote on 2015-04-20:	#2
test build: trafodion-20150418_0830.tar.gz
installer: installer-20150418_0830.tar.gz
server: atcsq02(n003 n004)

steps:

1. install the build and then uninstall it
2. rm trafodion_config
3. install again
[root@n003 installer]# ./trafodion_install

******************************
 TRAFODION INSTALLATION START
******************************

***INFO: testing sudo access
***INFO: Log file located at /var/log/trafodion/trafodion_install_2015-04-20-03-31-55.log
***INFO: Config directory: /etc/trafodion
***INFO: Working directory: /usr/lib/trafodion

*******************************
 Trafodion Configuration Setup
*******************************

***INFO: Please press 'Enter' to select defaults.

Enter trafodion password, default is 'traf123':
Enter list of nodes (blank separated), default '': n003 n004
***INFO: Testing sudo access on node n003
***INFO: Testing sudo access on node n004
Enter Trafodion userid's home directory prefix, default is '/home': /opt
Specify full path to EPEL RPM (including .rpm), default is None:
***INFO: Will attempt to download RPM if EPEL is not installed on all nodes.
Specify location of Java 1.7.0_65 or higher (JDK), default is : /usr/java/jdk1.7.0_67-cloudera
Enter full path (including .tar or .tar.gz) of trafodion tar file (): ../daily.tar.gz
***INFO: Detecting Hadoop distro
***INFO: Cloudera detected
***DEBUG: nameOfVersion=cdh5.3.3
Enter cloudera admin username, default is 'admin':
Enter cloudera admin password, default is 'admin':
Enter cloudera external network URL (including port), default is 'n003.cm.cluster:7180': 16.235.162.80:7180
Enter HDFS username, default is 'hdfs':
Enter HBase username, default is 'hbase':
Enter HBase group, default is 'hbase':
Enter directory to install trafodion to, default is '/opt/trafodion/daily':
Start Trafodion after install (Y/N), default is N: Y
Total number of DCS servers to start, default (2): 16
***INFO: Configuration file: /etc/trafodion/trafodion_config
***INFO: Trafodion configuration setup complete
***DEBUG: trafodionFullName=trafodion_server-1.1.0.tgz
***INFO: Trafodion version = 1.1.0
***DEBUG: HBase's java_exec=/usr/java/jdk1.7.0_09/bin/java

4. installation completed without issues

the fix is OK

Amanda Moran (amanda-kay-moran) on 2015-04-30
Changed in trafodion:
status:	Fix Committed → Fix Released


> LP Bug: 1442777 - traf_config_setup  does not get node list so install fails
> ----------------------------------------------------------------------------
>
>                 Key: TRAFODION-1155
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1155
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: installer
>            Reporter: Chris Tjepkema
>            Assignee: Amanda Moran
>            Priority: Blocker
>
> installer-20150410_0830.tar.gz
> reproduce by rm trafodion_config before running installer
> A fresh install won't have it anyway.
> [root@n001 installer]# ./trafodion_install
> ******************************
> TRAFODION INSTALLATION START
> ******************************
> ***INFO: testing sudo access
> ***INFO: Log file located at /var/log/trafodion/trafodion_install_2015-04-10-16-15-04.log
> ***INFO: Config directory: /etc/trafodion
> ***INFO: Working directory: /usr/lib/trafodion
> *******************************
> Trafodion Configuration Setup
> *******************************
> ***INFO: Please press 'Enter' to select defaults.
> Enter list of nodes (blank separated), default '': n001 n002 n003 n004
> ***INFO: Testing sudo access on node n001
> ***INFO: Testing sudo access on node n002
> ***INFO: Testing sudo access on node n003
> ***INFO: Testing sudo access on node n004
> Specify location of Java 1.7.0_65 or higher (JDK), default is /usr/jdk64/jdk1.7.0_67:
> Enter full path (including .tar or .tar.gz) of trafodion tar file (): ../daily.tar.gz
> ***INFO: Detecting Hadoop distro
> ***INFO: Hortonworks detected
> ***DEBUG: nameOfVersion=Version 0.98.4.2.2.0.0
> Enter hortonworks admin username, default is 'admin':
> Enter hortonworks admin password, default is 'admin':
> Enter hortonworks external network URL (including port), default is 'n001.cm.cluster:8080': 16.235.162.102:8000
> Enter HDFS username, default is 'hdfs':
> Enter HBase username, default is 'hbase':
> Enter HBase group, default is 'hbase':
> Enter directory to install trafodion to, default is '/opt/trafodion/daily':
> Start Trafodion after install (Y/N), default is N: Y
> Total number of DCS servers to start, default (2): 16
> ***INFO: Configuration file: /etc/trafodion/trafodion_config
> ***INFO: Trafodion configuration setup complete
> ***ERROR: Number of Trafodion nodes (0) must match number of hortonworks nodes (4)
> {
>   "href" : "http://16.235.162.102:8000/api/v1/clusters/seascape2/hosts",
>   "items" : [
>     {
>       "href" : "http://16.235.162.102:8000/api/v1/clusters/seascape2/hosts/n001.cm.cluster",
>       "Hosts" : {
>         "cluster_name" : "seascape2",
>         "host_name" : "n001.cm.cluster"
>       }
>     },
>     {
>       "href" : "http://16.235.162.102:8000/api/v1/clusters/seascape2/hosts/n002.cm.cluster",
>       "Hosts" : {
>         "cluster_name" : "seascape2",
>         "host_name" : "n002.cm.cluster"
>       }
>     },
>     {
>       "href" : "http://16.235.162.102:8000/api/v1/clusters/seascape2/hosts/n003.cm.cluster",
>       "Hosts" : {
>         "cluster_name" : "seascape2",
>         "host_name" : "n003.cm.cluster"
>       }
>     },
>     {
>       "href" : "http://16.235.162.102:8000/api/v1/clusters/seascape2/hosts/n004.cm.cluster",
>       "Hosts" : {
>         "cluster_name" : "seascape2",
>         "host_name" : "n004.cm.cluster"
>       }
>     }
>   ]
> }***ERROR: Exiting...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)