TECHZEN Zenoss User Community ARCHIVE  
FORUMS / Installation & Getting Started / DISCUSSION

Total noob, need help with access to web UI

Subject: Total noob, need help with access to web UI
Author: H T
Posted: 2017-12-13 06:57

Hi there, I'm a total noob and I need some help on how to access the web UI. I've installed this (on my home network to test out) on proxmox using the iso image (zenoss-core-5.3.0-1-master.x86_64.iso). I can access it via the IP address on the network through ssh and I'm able to ping the server on the network.

I've login as root and gone through the steps in the TUI and the correct network is active but when I try to access through a web browser using it's IP address (https://IP) I get connection refused.

I have read that I'm not using the current version of zenoss-core but I'm not sure where to download the latest version as I got this version from the email download link when I had to sign up to gain access to download the iso files.

Could someone point me in the right direction or tell me what I'm doing wrong.
Please remember I'm a total noob so go easy on me :)
thanks.

------------------------------
H T
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: Vimal Koshy
Posted: 2017-12-14 01:18

​Hi H,

If you have already installed the zenoss core app and are able to access it via SSH then the web interface should also be up and running. What are you entering in your address line? Are you using the https protocol?

------------------------------
Vimal Koshy
IT Engineer
dans
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: H T
Posted: 2017-12-14 09:25

Hi Vimal, thanks for getting back to me.
Yes I'm using the https protocol like so (https://192.168.1.111)
and when I ping the server (ping -c 5 192.168.1.111) it responses

Please see screenshot with browser error message and shh connection -

?
H


------------------------------
H T
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: Arthur
Posted: 2017-12-14 13:39

Hi H

Looks like serviced is not running and not listeing on port 80/443. Please poste the following output:

# docker ps
# systemctl  status docker
# systemctl  status serviced

​​​​

------------------------------
Arthur
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: H T
Posted: 2017-12-14 14:24

Hi Arthur,
here ya go ->
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

That's it for docker ps command

# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/docker.service.d
└─docker.conf
Active: active (running) since Tue 2017-12-12 17:24:04 GMT; 2 days ago
Docs: https://docs.docker.com
Main PID: 865 (dockerd)
Memory: 59.5M
CGroup: /system.slice/docker.service
├─ 865 /usr/bin/dockerd -s devicemapper --storage-opt dm.basesize=45G --storage...
└─1193 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-contain...

Dec 12 17:24:04 zenoss-core-master.lan systemd[1]: Starting Docker Application Container.....
Dec 12 17:24:04 zenoss-core-master.lan systemd[1]: Started Docker Application Container ...e.
Hint: Some lines were ellipsized, use -l to show in full.

And finally
# systemctl status serviced
serviced.service - Zenoss ServiceD
Loaded: loaded (/usr/lib/systemd/system/serviced.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-12-12 17:24:06 GMT; 2 days ago
Process: 1390 ExecStopPost=/opt/serviced/bin/serviced-systemd.sh post-stop (code=exited, status=0/SUCCESS)
Process: 1368 ExecStart=/opt/serviced/bin/serviced $SERVICED_OPTS server (code=exited, status=1/FAILURE)
Process: 1359 ExecStartPre=/opt/serviced/bin/serviced-systemd.sh pre-start (code=exited, status=0/SUCCESS)
Main PID: 1368 (code=exited, status=1/FAILURE)

Dec 12 17:24:06 zenoss-core-master.lan systemd[1]: Started Zenoss ServiceD.
Dec 12 17:24:06 zenoss-core-master.lan systemd[1]: serviced.service: main process exited, code=exited, st...URE
Dec 12 17:24:06 zenoss-core-master.lan serviced[1368]: Unable to validate server options: Use of devicema...rue
Dec 12 17:24:06 zenoss-core-master.lan serviced-systemd.sh[1390]: Tue Dec 12 17:24:06 UTC 2017: post-stopp...op
Dec 12 17:24:06 zenoss-core-master.lan serviced-systemd.sh[1390]: Tue Dec 12 17:24:06 UTC 2017: waiting fo...op
Dec 12 17:24:06 zenoss-core-master.lan serviced-systemd.sh[1390]: Tue Dec 12 17:24:06 UTC 2017: waiting fo...ng
Dec 12 17:24:06 zenoss-core-master.lan serviced-systemd.sh[1390]: Tue Dec 12 17:24:06 UTC 2017: waiting fo...op
Dec 12 17:24:06 zenoss-core-master.lan systemd[1]: Unit serviced.service entered failed state.
Dec 12 17:24:06 zenoss-core-master.lan serviced-systemd.sh[1390]: Tue Dec 12 17:24:06 UTC 2017: serviced i...op
Dec 12 17:24:06 zenoss-core-master.lan systemd[1]: serviced.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

?
H

------------------------------
H T
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: Arthur
Posted: 2017-12-16 04:39

Hi H

Based on the systemctl status serviced serviced failed to start.

Process: 1368 ExecStart=/opt/serviced/bin/serviced $SERVICED_OPTS server (code=exited, status=1/FAILURE)

Main PID: 1368 (code=exited, status=1/FAILURE)

This is often caused by a wrong option statement in the serviced configuration file.

Unfortunately I can't read the whole message as the lines are snipped.

Dec 12 17:24:06 zenoss-core-master.lan systemd[1]: serviced.service: main process exited, code=exited, st...URE
Dec 12 17:24:06 zenoss-core-master.lan serviced[1368]: Unable to validate server options: Use of devicema...rue

It looks like you face the same issue as in

https://community.zenoss.com/forum/all-discussions/printmessage?MessageKey=401e6389-f62e-4594-b28e-a574e621be01&Printable=1

 

Try to set the SERVICED_ALLOW_LOOP_BACK variable  in /etc/default/serviced to true.

# Set to true to allow use of loopback files (instead of thin pools) with devicemapper for serviced storage.
# NOTE: This is not recommended for production use.
# SERVICED_ALLOW_LOOP_BACK=false
SERVICED_ALLOW_LOOP_BACK=true

 

Cheers

 



------------------------------
Arthur
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: H T
Posted: 2017-12-18 11:22

Thanks Arthur,
I'll try what you suggest and report back.

Based on the systemctl status serviced serviced failed to start.

Process: 1368 ExecStart=/opt/serviced/bin/serviced $SERVICED_OPTS server (code=exited, status=1/FAILURE)

Main PID: 1368 (code=exited, status=1/FAILURE)

This is often caused by a wrong option statement in the serviced configuration file.

Unfortunately I can't read the whole message as the lines are snipped.

Dec 12 17:24:06 zenoss-core-master.lan systemd[1]: serviced.service: main process exited, code=exited, st...URE
Dec 12 17:24:06 zenoss-core-master.lan serviced[1368]: Unable to validate server options: Use of devicema...rue

It looks like you face the same issue as in

https://community.zenoss.com/forum/all-discussions/printmessage?MessageKey=401e6389-f62e-4594-b28e-a574e621be01&Printable=1

 

Try to set the SERVICED_ALLOW_LOOP_BACK variable  in /etc/default/serviced to true.

# Set to true to allow use of loopback files (instead of thin pools) with devicemapper for serviced storage.
# NOTE: This is not recommended for production use.
# SERVICED_ALLOW_LOOP_BACK=false
SERVICED_ALLOW_LOOP_BACK=true

 

Cheers

 



------------------------------
Arthur
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: H T
Posted: 2017-12-19 10:21

Hi there Arthur,
tried out what you had suggested but  it didn't work -

Try to set the SERVICED_ALLOW_LOOP_BACK variable in /etc/default/serviced to true.

# Set to true to allow use of loopback files (instead of thin pools) with devicemapper for serviced storage.
# NOTE: This is not recommended for production use.
# SERVICED_ALLOW_LOOP_BACK=false
SERVICED_ALLOW_LOOP_BACK=true

Thanks so much for all you help but I'm feeling a bit defeated  and think I should just move on and see if I can find something else that works.
Thankyou all for your help.
H

------------------------------
H T
------------------------------

Subject: RE: Total noob, need help with access to web UI
Author: Arthur
Posted: 2017-12-19 13:24

Hi H

No problem, I hope you at least didn't had the same failure message as before. I'll try the iso installation also and see if I'm running into the same issue as you, because most of the people are comming to this point and then give up.

Cheers

------------------------------
Arthur
------------------------------


< Previous
serviced-1.4.2-1.x86_64.rpm 		  Next
Which zenoss version (4.x, 5.x) is more stable! 		>