Zenoss 5 Beta 2 bringup issues.

Zenoss 5 Beta 2 bringup issues.

a) Installed Zenoss 5 beta 2 on a VM.
Ubuntu 14.04 with 16 core, 32GB RAM.

b) Looked at /var/log/kern.log
--> Found there is an apparmor denial for some request. The apparmor docker profile seems incomplete.
So modified, apparmor to complain mode for docker.
With this, denials are allowed.
Oct 7 05:37:03 zen5 kernel: [ 5663.176439] type=1400 audit(1412674623.429:364969): apparmor="ALLOWED" operation="ptrace" profile="docker-default" pid=16426 comm="ps" requested_mask="trace" denied_mask="trace" peer="docker-default"

c) tail -f /var/log/upstart/serviced.log
Watched and waited, till all is okay.
--> Has no errors.. all up and running okay.

d) GUI has access to the following.
Control center - is available, but has ! markers for health status on
some services, though i do not see any errors being thrown in the logs.
Zenoss UI - very very slow..
Hbase - is available
opentsdb - is available.
zookeeper exhibitor - http://zen5:12181/exhibitor/v1/ui/index.html
was available too.

So, now I have a zenoss 5 beta 2 system, that is installed, but not operational because of the UI. Below are the abnormalities i saw.

a) After a fresh install, the UI did not ask for configuring users and monitoring devices,
during first time login. It directly requested user/passwd credentials.
Luckily, admin/password seems to have got me through this page.

b) But the UI is agonizingly slow. I have not moved past the first login page.

Have been trying to understand why the UI is so very slow.
Attached into zope container.
Luckily only 3 files touched same day as installation, and see failures reported in the logs.

File: event.log within zope container.
2014-10-07T09:39:45 ERROR Zope.SiteErrorLog 1412674785.330.701302557061 https://127.0.0.1:8080/authorization/validate
Traceback (innermost last):
Module Zope2.App.startup, line 197, in __call__
Module ZPublisher.Publish, line 134, in publish
Module Zope2.App.startup, line 301, in commit
Module transaction._manager, line 89, in commit
Module transaction._transaction, line 329, in commit
Module transaction._transaction, line 446, in _commitResources
Module ZODB.Connection, line 781, in tpc_vote
Module relstorage.storage, line 794, in tpc_vote
Module relstorage.storage, line 841, in _vote
Module relstorage.storage, line 754, in _finish_store
Module ZODB.ConflictResolution, line 277, in tryToResolveConflict
ConflictError: database conflict error (oid 0x0849, class BTrees.OOBTree.OOBTree, serial this txn started with 0x03aa1663a3d184bb 2014-10-07 09:39:38.394945, serial currently committed 0x03aa1663aeebe399 2014-10-07 09:39:40.997213)

Error from Zope, probably related to UI
Please help resolve UI slowness and startup page failure issues

================================
As a second part, I tried opening up port 8080 on the zope directly instead of using zproxy.
From zenoss documentation, I was supposed to do the following.
edit service template for zenoss.core (serviced service edit Zenoss.core)
--> Modify AddressConfig for "Port" = 8080 and "Protocol" = "tcp".
After I do the above, AddressAssignment is needed error message comes, and does not allow service to be deployed at all.

And for disabling zope.conf, i understand i need to update /opt/zenoss/etc/zope.conf within zope container,
and make HTTPS OFF.
Can I do both of these while the service is already deployed
I do not see these changes persistent and is lost on service restart.
And how to get the address assignment error away.
Can I modify the json file under /opt/serviced/templates/zenoss-xxx.json and will it work, if i just reboot the machine.
====================================

Your help on the above is much appreciated.

==========================================
Additional debugging inputs:
a) Attached into zenoss.core container.
I run "curl http://localhost:8080/zport/dmd", I get no output at all.
But I see the following ports were open, and https port, did give some output for curl request.
PORT STATE SERVICE
443/tcp open https
8080/tcp open http-proxy
8443/tcp open https-alt
8888/tcp open sun-answerbook
9080/tcp open glrpc

b) So then I attach to zope container again.
PORT STATE SERVICE
443/tcp open https
3306/tcp open mysql
8080/tcp open http-proxy
8084/tcp open unknown
9080/tcp open glrpc

So invoking "curl http://localhost:8080" frmo within zope container did not give any results, curl just hung there,
waiting for data from the other end. So the zope server seems definitely to be hosed.

Also, in the CC GUI, Zope has all health checks passed, except zproxy_answering.

Is my earlier error related to this behavior How to recover from this

Thanks,
LN