1
0
-1

Hi,

have some problem with an initial installation of the ONAP system..

when checking the portal machine log I find everywhere some error..

like in localhost.2017-07-31.log:

"31-Jul-2017 13:40:01.519 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: [org.springframework.boot.autoconfigure.jersey.JerseyAutoConfiguration@3c7222d8, org.openecomp.portalapp.conf.ExternalAppInitializer@689366ad]

31-Jul-2017 13:40:01.695 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'

31-Jul-2017 13:40:15.097 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: [org.springframework.boot.autoconfigure.jersey.JerseyAutoConfiguration@6ef11fdb, org.openecomp.portalapp.conf.ExternalAppInitializer@201fb131]

31-Jul-2017 13:40:15.224 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'

31-Jul-2017 13:41:17.836 SEVERE [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log StandardWrapper.Throwable

 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSourceMap' defined in class path resource [org/openecomp/portalsdk/core/conf/HibernateConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [java.util.Map]: Factory method 'dataSourceMap' threw exception; nested exception is java.sql.SQLException: Connections could not be acquired from the underlying database!

        at org.springframework.beans.factory.support.ConstructorResolver.ins...

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [java.util.Map]: Factory method 'dataSourceMap' threw exception; nested exception is java.sql.SQLException: Connections could not be acquired from the underlying database!

Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!"


So I assume there is some problem with the Database access?


But this one shows that the install is not even finished:

"./widget_ms_start.sh: 4: ./widget_ms_start.sh: source: not found Running docker image as container Unable to find image '8082:8082' locally docker: Error response from daemon: repository 8082 not found: does not exist or no pull access."


from  /PROJECT/OpenSource/UbuntuEP/log/ecompportal/error.log

the health check also shows errors.. eg cant reach "vm1-message-router"


unfortunately I'm behind proxy.. I have set the proxy settings for all the VM-s and for the docker files in yaml file, like this:

# Download and run install script

            curl -k __nexus_repo__/org.openecomp.demo/boot/__artifacts_version__/portal_install.sh -o /opt/portal_install.sh

            cd /opt

            sed -i '/service docker restart/i\

            echo -e "export http_proxy=\"<proxy_ip>\"\\nexport https_proxy=\"<proxy_ip>\"" | tee -a /etc/default/docker' portal_install.sh

            chmod +x portal_install.sh

            ./portal_install.sh


portal docker status:


53b2ceeea3b7        ep:1610-1           "/configure-and-ru..."   43 minutes ago      Up 43 minutes       0.0.0.0:8006->8005/tcp, 0.0.0.0:8010->8009/tcp, 0.0.0.0:8989->8080/tcp   onap_portal

77779be8a5b4        ecompdb:portal      "docker-entrypoint..."   43 minutes ago      Up 43 minutes                                                                                ecompdb_portal

0dc9333764d9        mariadb             "docker-entrypoint..."   43 minutes ago      Created 


does anybody have some idea, what I'm doing wrong? or what should I check first? (smile)


 

Attila Jany

Customer Solution Verification Sen Spec

Mobile Networks, Converged Core Networks

NOKIA



    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Attila Jány Verify the "docker images". 


      Looks like you have added the proxies to docker but not to shell ENV. portal_vm_init.sh also does a "git pull". Perhaps you need to pass proxies there as well. 


      Must contain following images

      root@onap-portal:~# docker images

      REPOSITORY TAG IMAGE ID CREATED SIZE
      ecompdb portal f8a76b9b2f3d 22 hours ago 398MB
      nexus3.onap.org:10001/openecomp/portaldb 1.1-STAGING-latest f8a76b9b2f3d 22 hours ago 398MB
      widget-ms latest 3d2bbbe72228 22 hours ago 246MB
      nexus3.onap.org:10001/openecomp/portalwms 1.1-STAGING-latest 3d2bbbe72228 22 hours ago 246MB
      ep 1610-1 dfa8633b2943 22 hours ago 1.4GB
      nexus3.onap.org:10001/openecomp/portalapps 1.1-STAGING-latest dfa8633b2943 22 hours ago 1.4GB
      mariadb latest 0ff2b852d8bf 2 days ago 397MB
      root@onap-portal:~#





      1. Attila Jány

        without the proxy settings I could not download the install sh .

        So that setting is OK.

        It turned out that the git pull command is failing if it is run from the sh file...

        When I run it manually than it makes the job..

      2. kranthi guttikonda

        Update the environment variables in script before git pull command and re-run

      CommentAdd your comment...