hopsworks login page is not coming

19 views

Skip to first unread message

vikra...@gmail.com

unread,

Jul 8, 2019, 5:47:20 AM7/8/19

to Hops

I launched hopsworks using AMI 0.9on aws ec2.

http://<public_ip>/hopsworks ..i get page
Spark up again, by going back to login page!

Is the path correct ? PLease help me on this.

ubuntu@ip-172-31-2-74:~$ ./start-services.sh
Welcome to Hopsworks!

[Legal stuff]
Logical Clocks AB will use the information you provide during the registration
to be in touch with you to provide updates and marketing.
You can opt out at any time by clicking the unsubscribe link in the
footer of any email you receive from us, or by contacting us at j...@logicalclocks.com
By continuing the registration you agree that we may process your information in
accordance with these terms.

Please enter your email address to continue:
vikra...@gmail.com
Registering hopsworks instance....
curl: (7) Failed to connect to snurran.sics.se port 8443: Connection refused
Generating a certificate for your instance...

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /srv/hops/domains/domain1/config/keystore.jks -destkeystore /srv/hops/domains/domain1/config/keystore.jks -deststoretype pkcs12".
Certificate stored in file </tmp/cert.pem>

ndb_mgmd was already running
ndbmtd was already running
mysqld was already running
zookeeper was already running
Starting kafka ....
Started kafka ....
Starting namenode ....
Started namenode ....
datanode was already running
Starting resourcemanager ....
Started resourcemanager ....
nodemanager was already running
glassfish-domain1 was already running
historyserver was already running
sparkhistoryserver was already running
elasticsearch was already running
livy was already running
Starting epipe ....
Started epipe ....
influxdb was already running
grafana was already running
logstash was already running
kibana was already running
filebeat-spark was already running
filebeat-serving was already running
kagent was already running
Starting hivemetastore ....
Started hivemetastore ....
hiveserver2 was already running
Starting hivecleaner ....
Started hivecleaner ....
sqoop was already running
Starting airflow-webserver ....
Started airflow-webserver ....

Status of all local services now:

kagent running
historyserver running
sparkhistoryserver running
elasticsearch running
livy running
epipe running
zookeeper running
kafka running
namenode running
datanode running
resourcemanager running
nodemanager running
ndb_mgmd running
ndbmtd running
mysqld running
glassfish-domain1 running
grafana running
influxdb running
logstash running
kibana running
hivemetastore running
hiveserver2 running
hivecleaner running
sqoop running
airflow-webserver running
All services are up and running!

fa...@logicalclocks.com

unread,

Jul 8, 2019, 9:04:32 AM7/8/19

to Hops

Hi!
The address is correct.

Can you check if all the services are up and running correctly? You can do that by running this script: `/srv/hops/kagent/kagent/bin/status-all-local-services.sh` as superuser.
In particular can you make sure that glassfish-domain1 is running? In case it's not, you can start it by executing `systemctl start glassfish-domain`.