Hi there, After a successful install using vagrant centos 1 VM, 48GB Ram,500GB I was able to log in a start spark tour…or is what I think because was spinning for a long time, afterward the spinning icon back the static and when i click on it again got this message
" Project with the same name already exists.
project: demo_spark_admin000" however is not showing anything in the project search tool, still showing 0 projects.
how can we verify it was created or open the project?
Regards
If you login as admin, you can navigate to the admin UI from the top right menu and look under projects management. There you can force remove the project if it’s listed.
But this behavior would indicate that some of the services have not been installed correctly or are down. Which cluster definition did you use to install hopsworks? Which version?
You can also have a look in the app server logs, /srv/hops/domains/domain1/logs/server.log when creating the project as there will probably be a more specific error message.
Thank for the tip Theo, i sorted that out creating a new user and connecting with that account, as hops user was able to create the tour project and resources, not the problem is starting the jupyter server, after click on “jupyterLab” button got a “generic error occured”. following the log you mentioned i found this at then of the file
[#|2020-05-08T18:42:00.003+0000|SEVERE|Payara 4.1|io.hops.hopsworks.common.kafka.ZookeeperTopicCleanerTimer|_ThreadID=85;_ThreadName=__ejb-thread-pool12;_TimeMillis=1588963320003;_LevelValue=1000;|java.io.IOException: com.logicalclocks.servicediscoverclient.exceptions.ServiceNotFoundException: Error: host not found Could not find service ServiceQuery(name=client.zookeeper.service.consul, tags=[])
** at io.hops.hopsworks.common.kafka.KafkaBrokers.getBrokerEndpoints(KafkaBrokers.java:121)**
** at sun.reflect.GeneratedMethodAccessor488.invoke(Unknown Source)**
** at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)**
** at java.lang.reflect.Method.invoke(Method.java:498)**
** at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1081)**
** at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1153)**
** at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:4836)**
** at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:656)**
** at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:836)**
** at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:608)**
** at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)**
My question is if this still provisioning /installing some software?
reviewing things done,noted jupyter project settings has not assigned HIVE and FEATURESTORE, i went a head selecting and the error now is “Could not create HiveDB for project” so back to the admin module and HDFS shows UPGRADE IN PROGRESS
kind of confused if the previous problem may be related with this service not assigned and still pending
How did you install Hopsworks? Did you define allocated 48GB in the vagrant file? Just to check if the installation process was actually completed before starting creating projects, although from the screenshot above with all the services things seem fine
Can you try dig client.zookeeper.service.consul and see if it returns the machine IP?
i used Vagrant(VirtualBox) approach, previous modification of the VM definition for more RAM and Cores
the host is able to reach the service. not the same from the guest host(hopsworks) …it does not have the dig command… would affect any configuration if i install dig command?
Thank you, you installed it correctly but this process installs the nightly snapshot build which means things are not as stable as a release build and something might be off in this VM. For example Cannot launch Jupyter notebook
One option would be to restart all services in the VM. vagrant ssh to get a session, then sudo /srv/hops/kagent/kagent/bin/shutdown-all-local-services.sh, and then sudo /srv/hops/kagent/kagent/bin/start-all-local-services.sh.