1
0
-1

I have manually executed the deploy_vm1.sh script after the successful completion of below 2 scripts manually.

aai_install.sh and aai_vm_init.sh.

Below is the error when we execute deploy_vm1.sh in logs.


13:54:44.038 [main] DEBUG org.apache.commons.configuration.PropertiesConfiguration - FileName set to titan-realtime.properties
13:54:44.046 [main] DEBUG org.apache.commons.configuration.PropertiesConfiguration - Base path set to /opt/app/aai-resources/bundleconfig/etc/appprops
13:54:44.059 [main] DEBUG org.apache.commons.configuration.ConfigurationUtils - ConfigurationUtils.locate(): base is /opt/app/aai-resources/bundleconfig/etc/appprops, name is titan-realtime.properties
13:54:44.060 [main] DEBUG org.apache.commons.configuration.DefaultFileSystem - Could not locate file titan-realtime.properties at /opt/app/aai-resources/bundleconfig/etc/appprops: no protocol: /opt/app/aai-resources/bundleconfig/etc/appprops
13:54:44.061 [main] DEBUG org.apache.commons.configuration.ConfigurationUtils - Loading configuration from the path /opt/app/aai-resources/bundleconfig/etc/appprops/titan-realtime.properties
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.openecomp.aai.dbmap.AAIGraph.getInstance(AAIGraph.java:95)
at org.openecomp.aai.dbgen.GenTester.main(GenTester.java:105)
Caused by: java.lang.RuntimeException: Failed to instantiate graphs


Then when i checked the path for the configuration file it was missing.


root@vm1-aai-inst1:/opt/test-config# ls /opt/app/aai-resources/bundleconfig/etc/appprops/titan-realtime.properties
ls: cannot access /opt/app/aai-resources/bundleconfig/etc/appprops/titan-realtime.properties: No such file or directory
root@vm1-aai-inst1:/opt/test-config#


Kindly suggste what could be the problem.


Gaurav

    CommentAdd your comment...

    5 answers

    1.  
      1
      0
      -1

      Found the problem, the createDBSchema.sh, and some of the Java, references aai.hbase.simpledemo.openecomp.org which doesnt resolve. I added it to /etc/hosts and the createDBSchema.sh runs properly now. 


      EDIT: Root cause appears to be additions for CLAMP to the DNS zone.


      Sep 12 22:57:53 vm1-dns-server named[8186]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:123: unexpected end of line
      Sep 12 22:57:53 vm1-dns-server named[8186]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:122: unexpected end of input


      I added a semicolon before line 122 where it just says CLAMP and did a service bind9 restart.


      For clarity, SSH to DNS VM and the following:

      ubuntu@vm1-dns-server:~$ sudo su -
      root@vm1-dns-server:~# grep named /var/log/syslog | grep dns_master_load
      Sep 12 20:47:06 vm1-dns-server named[7760]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:123: unexpected end of line
      Sep 12 20:47:06 vm1-dns-server named[7760]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:122: unexpected end of input
      Sep 12 22:57:27 vm1-dns-server named[7760]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:123: unexpected end of line
      Sep 12 22:57:27 vm1-dns-server named[7760]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:122: unexpected end of input
      Sep 12 22:57:53 vm1-dns-server named[8186]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:123: unexpected end of line
      Sep 12 22:57:53 vm1-dns-server named[8186]: dns_master_load: /etc/bind/zones/db.simpledemo.openecomp.org:122: unexpected end of input
      root@vm1-dns-server:~# vi /etc/bind/zones/db.simpledemo.openecomp.org

      Change

      CLAMP
      clamp.api.simpledemo.openecomp.org.     IN      CNAME   vm1.clamp.simpledemo.openecomp.org.

      To

      ;CLAMP
      clamp.api.simpledemo.openecomp.org.     IN      CNAME   vm1.clamp.simpledemo.openecomp.org.

      Write/Quite editor


      root@vm1-dns-server:~# service bind9 restart

      1. Brian Matt

        Looks like the zone file has been fixed, run the install script on  your DNS server again and it should resolve.

      CommentAdd your comment...
    2.  
      1
      0
      -1

      You may try doing an aai_vm_init.sh on aai2, once aai1 starts it creates a graph in titan on aai2. If you restart/redeploy aai1 it'll fail because the graph already exists. By reinitializing aai2 that graph will be deleted.

      1. Gaurav Mittal

        Thanks Matt,


        I tried again and i see that AAi2 was able to complete. But the AAi1 instance is still giving the same error. I executed all the commands manually given in script aai_install.sh, aai_vm_init.sh and deploy_vm1.sh and ensured that there is no error.


        Where can i find the file.

        /opt/app/aai-resources/bundleconfig/etc/appprops/titan-realtime.properties


        Regards,

        Gaurav

      2. Gaurav Mittal

        Hi,

        I created some links where these files were there and then was able to continue. Now its failing with below reason.



        ---- NOTE --- about to open graph (takes a little while)--------;
        12:25:36.787 [main] DEBUG org.apache.commons.configuration.PropertiesConfiguration - FileName set to titan-realtime.properties
        12:25:36.788 [main] DEBUG org.apache.commons.configuration.PropertiesConfiguration - Base path set to /opt/app/aai-resources/bundleconfig/etc/appprops
        12:25:36.792 [main] DEBUG org.apache.commons.configuration.ConfigurationUtils - ConfigurationUtils.locate(): base is /opt/app/aai-resources/bundleconfig/etc/appprops, name is titan-realtime.properties
        12:25:36.793 [main] DEBUG org.apache.commons.configuration.DefaultFileSystem - Could not locate file titan-realtime.properties at /opt/app/aai-resources/bundleconfig/etc/appprops: no protocol: /opt/app/aai-resources/bundleconfig/etc/appprops
        12:25:36.794 [main] DEBUG org.apache.commons.configuration.ConfigurationUtils - Loading configuration from the path /opt/app/aai-resources/bundleconfig/etc/appprops/titan-realtime.properties
        Exception in thread "main" java.lang.ExceptionInInitializerError
        at org.openecomp.aai.dbmap.AAIGraph.getInstance(AAIGraph.java:95)
        at org.openecomp.aai.dbgen.GenTester.main(GenTester.java:105)
        Caused by: java.lang.RuntimeException: Failed to instantiate graphs
        at org.openecomp.aai.dbmap.AAIGraph.<init>(AAIGraph.java:81)
        at org.openecomp.aai.dbmap.AAIGraph.<init>(AAIGraph.java:55)
        at org.openecomp.aai.dbmap.AAIGraph$Helper.<clinit>(AAIGraph.java:86)
        ... 2 more
        Caused by: com.thinkaurelius.titan.core.TitanException: Could not open global configuration
        at com.thinkaurelius.titan.diskstorage.Backend.getStandaloneGlobalConfiguration(Backend.java:451)
        at com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration.<init>(GraphDatabaseConfiguration.java:1322)
        at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:94)
        at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:62)
        at org.openecomp.aai.dbmap.AAIGraph.loadGraph(AAIGraph.java:101)
        at org.openecomp.aai.dbmap.AAIGraph.<init>(AAIGraph.java:78)
        ... 4 more
        Caused by: com.thinkaurelius.titan.diskstorage.TemporaryBackendException: Temporary failure in storage backend
        at com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.ensureTableExists(HBaseStoreManager.java:759)
        at com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.ensureColumnFamilyExists(HBaseStoreManager.java:831)
        at com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.openDatabase(HBaseStoreManager.java:456)
        at com.thinkaurelius.titan.diskstorage.keycolumnvalue.KeyColumnValueStoreManager.openDatabase(KeyColumnValueStoreManager.java:29)
        at com.thinkaurelius.titan.diskstorage.Backend.getStandaloneGlobalConfiguration(Backend.java:449)
        ... 9 more
        Caused by: org.apache.hadoop.hbase.DoNotRetryIOException: java.lang.NoSuchMethodError: com.google.common.base.Stopwatch.elapsedMillis()J
        at org.apache.hadoop.hbase.client.RpcRetryingCaller.translateException(RpcRetryingCaller.java:229)
        at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:202)
        at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:299)
        at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:278)
        at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:140)
        at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:135)
        at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:845)
        at org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:600)
        at org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:364)
        at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:281)
        at com.thinkaurelius.titan.diskstorage.hbase.HBaseAdmin1_0.tableExists(HBaseAdmin1_0.java:70)
        at com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.ensureTableExists(HBaseStoreManager.java:753)
        ... 13 more
        Caused by: java.lang.NoSuchMethodError: com.google.common.base.Stopwatch.elapsedMillis()J
        at org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:439)
        at org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation(ZooKeeperRegistry.java:60)
        at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(ConnectionManager.java:1139)
        at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1106)
        at org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(RpcRetryingCallerWithReadReplicas.java:293)
        at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:147)
        at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:56)
        at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:200)
        ... 23 more
        root@vm1-aai-inst1:/opt/test-config# 
        





      CommentAdd your comment...
    3.  
      1
      0
      -1

      James Forsyth this seems to be new issue in AAI?

        CommentAdd your comment...
      1.  
        1
        0
        -1

        I am getting the same error for aai2 VM also for deploy_vm2.sh

          CommentAdd your comment...
        1.  
          1
          0
          -1

          I met the same problem

          I tried some different aai-resource docker versions.such as1.1.0-SNAPSHOT-LATEST-201708xxxxx??still can not solve .

            CommentAdd your comment...