Hello Everyone,

I've installed Zenoss 5.0.10 on Centos 7 (minimal install) using https://github.com/monitoringartist/zenoss5-core-autodeploy auto-deploy script. The installation was fine, no issues, Zenoss was up and running and was able to add devices to it.

Yesterday, this Zenoss installation triggered two DNS zone transfer requests (same time stamp). Here are the details:

03/01/2016 08:08:43 PM
EventCode=6004 EventType=3 Type=Warning ComputerName=DNS.mydomain.com
Message=The DNS server received a zone transfer request from 10.10.10.10 for a non-existent or non-authoritative zone com

The zone transfer request only happened once, the server has been up and running for the last 5 days.

Anybody know why this happened or how I can find out more information on why it happened?
I've looked through the Zenoss logs on Control Center > Logs but could not see anything related.

Thank you,
Max

Hello All,

I am looking for a way to graph and alert on http latency.

I would Zenoss to do an HTTPGET on a url and record the time (latency)

How do I do this?

Thanks!

I did a clean insteall of the latest version of Zenoss 5 today on CentOS 7.2.  Everything was working well on it until I tried to install my first zenpack.  I followed the admin guide to the letter and am receiveing an error when I run the command "serviced service run zope zenpack install <zenpack name.egg>".  This command returns the error listed below.  Any help with this would be greatly appreciated. 

unkown zenpack sub-command: "install"
usage:
      zenpack help
      zenpack list
Command returned non-zero exit code 1.

Hey there,

I'm just about to test zenoss to get a better impression of its functionalities. After preparing an Ubuntu installation yesterday the autodeploy install script was exchanged over night, not supporting Ubuntu for Version 5.1 any more.

Bummer. Anyway so I downloaded the .ova file, as I said I just want to test zenoss to get a better impression. But now I cannot login via the normal console to find out on the IP the machine has.

The combination of user/password -> ccuser / zenoss is not working in the console.

Any help is greatly appreciated.

Hello.

Question about table object_state stored in zodb database.

What information is stored is this table.

Mysql is configured with innodb_file_per_table

and this table object_state in zodb grow fast, per day about 1~1.5GB

Thanks

Can anyone point me in the right direction as to how to debug tansforms in ZenOSS 5. I followed this document:

http://wiki.zenoss.org/Debugging_Event_Transforms

But when connecting to the ZenOSS container shell, and running /opt/zenoss/bin/zeneventd run -v10, I get the message /bin/zenfunctions: No such file or directory. True. So I'm guessing the method has changed now under Docker...anyone know what that is?

We recently replaced a server that was doing smtp relay for zenoss (as well as other things). I've repointed the smtp settings in the advanced settings on zenoss, but for some reason it's still sending to the old server. Strangly, if I send a test message from the user setting page, the email headers show that it's coming from the new server, but if an actual event is triggered, it flows through the old server. Is there some cache somewhere that needs to be cleared, or something like that. Tried a reboot of the server but that didn't help. Thanks in advance. 

We're running 4.2.3 and we pretty much only are using it for checking to see if the switch/server/etc. is up or down.  We would like to do more with it but no one is taking the bull by the horns and becoming THE Zenoss Admin.

Is there any overriding reason to upgrade to 5.0?  I understand it has a feature to find devices and whatever SNMP info that can be pulled from these devices but is that the only big upgrade?

Thanks.

I am having a strange issue with Zenoss5, where it is not allowing me to access the server web UI from any more than 2 PC's.  On my everyday PC I use for work, I can access Zenoss5 web UI just fine, but when I try to access from my laptop or a VM, I get a "Server not found" error.

Is there a limit to the number of PC's that are allowed to access the Zenoss server web interface?

I try to access at ++resource++ files directly in browser without zenoss login and i see the file code...

(example : http://xxx.xxx.xxx.xxx:8080/++resource++extjs/resources/css/ext-all.css)

there is a way to bind the ++resource++ files under zenoss authenticated session?

thanks,

Hello. I'm new to zenoss 5. I installed zenpack which need installation of some prerequisits and change in config file. Base on documentation I installed prerequisited on Zope. Is it enough (looks like not since I still getting alerts about unmitted dependencies)? I noticed that after zenpack installation files of zenpack was propagated to almost all containers... on which one should I edit it?

Is there any way to disable eavent clearing? I wan't to be informed when some event occure, event if clearing event come

I'm tring to install ACASUserFolder and CAS4PAS plugin using ZMI and successed,

but....the next?

once I login SSO server and redirect to Zenoss,

but Zenoss do nothing, and still redirect to default login page(thats means login failed.)

any one has solution about Zenoss+CAS plugin?

Hi

Did anybody was able to install http://wiki.zenoss.org/ZenPack:Dell_Monitor_%28Community%29 on zenoss 5? I know that last mentioned version in zenpack catalog is 4, but I hope it's still work in zenoss 5 (it's look like almost all zenpacks for dell are outdated :( ). I'm getting error:

ZopeXMLConfigurationError: File "/opt/zenoss/etc/site.zcml", line 16.2-16.23
    ZopeXMLConfigurationError: File "/opt/zenoss/ZenPacks/ZenPacks.community.deviceAdvDetail-2.9.0.egg/ZenPacks/community/deviceAdvDetail/configure.zcml", line 9.8-12.19
    ImportError: No module named rrdtool

I installed python-setuptools, python-devel and tried to install rrdtool but it's complainig about:

Downloading https://pypi.python.org/packages/source/r/rrdtool/rrdtool-0.1.4.tar.gz#md5=60244b8384513d81d472a68564326653
Processing rrdtool-0.1.4.tar.gz
Writing /tmp/easy_install-TkYAgg/rrdtool-0.1.4/setup.cfg
Running rrdtool-0.1.4/setup.py -q bdist_egg --dist-dir /tmp/easy_install-TkYAgg/rrdtool-0.1.4/egg-dist-tmp-dwp1UC
rrdtoolmodule.c:27:17: fatal error: rrd.h: No such file or directory
 #include <rrd.h>
                 ^
compilation terminated.
error: Setup script exited with error: command 'gcc' failed with exit status 1

Do I really need to install rrdtool-devel with all dependencies?

This page has all the things I want on it:

https://web.archive.org/web/20150109151930/http://community.zenoss.org/community/documentation/official_documentation/api%3Fview=documents

I cannot get to these files. Also, This sort of information and styling is exactly what I've been looking for and zenoss seems to be missing. I do have the 5.02 api docs, but it was a hike to find them. 

I'm having issues upgrading from Zenoss core 5.0.10 to 5.1.1. I am running on CentOS 7 with 32GB of memory and 4vCPUs. The system has been running and monitoring ~250-300 devices for 9-10 months. I have two issues: one, metricshipper will not start; two, I cannot login to Zenoss after the upgrade.

I followed the upgrade guide. I was able to change both btrfs partitions to devicemapper and upgrade control center from 1.0.10 to 1.1.2. Zenoss was running just fine during each "phase" of the upgrade process until I upgraded Zenoss core.

I've attempted three upgrades this week and all have failed. The second and third upgrades show the same issues, so I am hoping someone can shed some light on the issues. Both metricshipper processes fail health checks with this error code: "W0310 18:47:43.354601 00001 controller.go:833] Health check "store_answering" failed.%!(EXTRA *exec.ExitError=exit status 1)". I don't see any recommendations in the upgrade guide about how to proceed. I can't find a place to upload a log file, so here it is:

I0310 18:47:22.170208 00001 vif.go:58] vif subnet is: 10.3
I0310 18:47:22.170328 00001 lbClient.go:77] ControlPlaneAgent.GetServiceInstance()
I0310 18:47:22.272618 00001 controller.go:296] Allow container to container connections: true
I0310 18:47:22.297938 00001 controller.go:229] Wrote config file /opt/zenoss/etc/metricshipper/metricshipper.yaml
I0310 18:47:22.306807 00001 controller.go:200] Successfully ran command:'&{/usr/bin/chown [chown zenoss:zenoss /opt/zenoss/etc/metricshipper/metricshipper.yaml] []  <nil>   [] <nil> 0xc2080e5c80 exit status 0 <nil> true [0xc208036048 0xc2080360b8 0xc2080360b8] [0xc208036048 0xc2080360b8] [0xc2080360a0] [0x53e840] 0xc2080425a0}' output: 
I0310 18:47:22.317484 00001 controller.go:200] Successfully ran command:'&{/usr/bin/chmod [chmod 0644 /opt/zenoss/etc/metricshipper/metricshipper.yaml] []  <nil>   [] <nil> 0xc2080e5de0 exit status 0 <nil> true [0xc2080360e0 0xc208036100 0xc208036100] [0xc2080360e0 0xc208036100] [0xc2080360f8] [0x53e840] 0xc2080426c0}' output: 
I0310 18:47:22.323467 00001 logstash.go:55] Using logstash resourcePath: /usr/local/serviced/resources/logstash
I0310 18:47:22.324824 00001 controller.go:229] Wrote config file /etc/logstash-forwarder.conf
I0310 18:47:22.324984 00001 controller.go:385] pushing network stats to: http://localhost:22350/api/metrics/store
I0310 18:47:22.325101 00001 instance.go:87] about to execute: /usr/local/serviced/resources/logstash/logstash-forwarder , [-idle-flush-time=5s -old-files-hours=26280 -config /etc/logstash-forwarder.conf][4]
I0310 18:47:22.326858 00001 endpoint.go:131]  c.zkInfo: {ZkDSN:{"Servers":["10.209.8.12:2181"],"Timeout":15000000000} PoolID:default}
2016/03/10 18:47:22 publisher init
2016/03/10 18:47:22 
			{
				"network": {
					"servers": [ "127.0.0.1:5043" ],
					"ssl certificate": "/usr/local/serviced/resources/logstash/logstash-forwarder.crt",
					"ssl key": "/usr/local/serviced/resources/logstash/logstash-forwarder.key",
					"ssl ca": "/usr/local/serviced/resources/logstash/logstash-forwarder.crt",
					"timeout": 15
				},
				"files": [
					
		{
			"paths": [ "/opt/zenoss/log/metricshipper.log" ],
			"fields": {"instance":"0","service":"7fhb0p5uqjof9stbvitno6f8k","type":"metricshipper"}
		}
				]
			}
2016/03/10 18:47:22.331233 Launching harvester on new file: /opt/zenoss/log/metricshipper.log
2016/03/10 18:47:22.331293 Loading client ssl certificate: /usr/local/serviced/resources/logstash/logstash-forwarder.crt and /usr/local/serviced/resources/logstash/logstash-forwarder.key
2016/03/10 18:47:22.334636 Starting harvester: /opt/zenoss/log/metricshipper.log
2016/03/10 18:47:22.334668 Current file offset: 2061
I0310 18:47:22.337790 00001 endpoint.go:172] getting service state: 7fhb0p5uqjof9stbvitno6f8k 0
I0310 18:47:22.340636 00001 endpoint.go:270]   cached imported endpoint[chzv9aasqaqwbifwju30sjm8c_redis]: {endpointID:redis instanceID:0 virtualAddress: purpose:import port:6379}
I0310 18:47:22.340684 00001 endpoint.go:270]   cached imported endpoint[chzv9aasqaqwbifwju30sjm8c_zproxy]: {endpointID:zproxy instanceID:0 virtualAddress: purpose:import port:8080}
I0310 18:47:22.340704 00001 controller.go:398] command: [su - zenoss -c "cd /opt/zenoss && /bin/supervisord -n -c etc/metricshipper/supervisord.conf"] [1]
I0310 18:47:22.392720 00001 controller.go:913] Got service endpoints for 7fhb0p5uqjof9stbvitno6f8k: map[tcp:5043:[{ServiceID:controlplane_logstash_lumberjack InstanceID:0 Application:controlplane_logstash_lumberjack Purpose: HostID: HostIP:10.209.8.12 HostPort:5043 ContainerID: ContainerIP:127.0.0.1 ContainerPort:5043 Protocol:tcp VirtualAddress: ProxyPort:5043}] tcp:8444:[{ServiceID:controlplane_consumer InstanceID:0 Application:controlplane_consumer Purpose: HostID: HostIP:10.209.8.12 HostPort:8443 ContainerID: ContainerIP:127.0.0.1 ContainerPort:8443 Protocol:tcp VirtualAddress: ProxyPort:8444}] tcp:443:[{ServiceID:controlplane InstanceID:0 Application:controlplane Purpose: HostID: HostIP:10.209.8.12 HostPort:443 ContainerID: ContainerIP:127.0.0.1 ContainerPort:443 Protocol:tcp VirtualAddress: ProxyPort:443}] tcp:5042:[{ServiceID:controlplane_logstash_tcp InstanceID:0 Application:controlplane_logstash_tcp Purpose: HostID: HostIP:10.209.8.12 HostPort:5042 ContainerID: ContainerIP:127.0.0.1 ContainerPort:5042 Protocol:tcp VirtualAddress: ProxyPort:5042}]]
I0310 18:47:22.392942 00001 controller.go:925] changing key from tcp:443 to chzv9aasqaqwbifwju30sjm8c_controlplane: {ServiceID:controlplane InstanceID:0 Application:controlplane Purpose: HostID: HostIP:10.209.8.12 HostPort:443 ContainerID: ContainerIP:127.0.0.1 ContainerPort:443 Protocol:tcp VirtualAddress: ProxyPort:443}
I0310 18:47:22.393016 00001 controller.go:925] changing key from tcp:5042 to chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_tcp: {ServiceID:controlplane_logstash_tcp InstanceID:0 Application:controlplane_logstash_tcp Purpose: HostID: HostIP:10.209.8.12 HostPort:5042 ContainerID: ContainerIP:127.0.0.1 ContainerPort:5042 Protocol:tcp VirtualAddress: ProxyPort:5042}
I0310 18:47:22.393047 00001 controller.go:925] changing key from tcp:5043 to chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_lumberjack: {ServiceID:controlplane_logstash_lumberjack InstanceID:0 Application:controlplane_logstash_lumberjack Purpose: HostID: HostIP:10.209.8.12 HostPort:5043 ContainerID: ContainerIP:127.0.0.1 ContainerPort:5043 Protocol:tcp VirtualAddress: ProxyPort:5043}
I0310 18:47:22.393082 00001 controller.go:925] changing key from tcp:8444 to chzv9aasqaqwbifwju30sjm8c_controlplane_consumer: {ServiceID:controlplane_consumer InstanceID:0 Application:controlplane_consumer Purpose: HostID: HostIP:10.209.8.12 HostPort:8443 ContainerID: ContainerIP:127.0.0.1 ContainerPort:8443 Protocol:tcp VirtualAddress: ProxyPort:8444}
I0310 18:47:22.393140 00001 endpoint.go:585] Attempting port map for: chzv9aasqaqwbifwju30sjm8c_controlplane -> {ServiceID:controlplane InstanceID:0 Application:controlplane Purpose: HostID: HostIP:10.209.8.12 HostPort:443 ContainerID: ContainerIP:127.0.0.1 ContainerPort:443 Protocol:tcp VirtualAddress: ProxyPort:443}
I0310 18:47:22.393236 00001 endpoint.go:605] Success binding port: chzv9aasqaqwbifwju30sjm8c_controlplane -> proxy[{controlplane 0 controlplane   10.209.8.12 443  127.0.0.1 443 tcp  443}; &{%!s(*net.netFD=&{{0 0 0} 10 2 1 false tcp4 0xc20818a3f0 <nil> {140633420050960}})}]=>[]
I0310 18:47:22.393461 00001 endpoint.go:270]   cached imported endpoint[chzv9aasqaqwbifwju30sjm8c_controlplane]: {endpointID:controlplane instanceID:0 virtualAddress: purpose:import port:443}
I0310 18:47:22.393501 00001 endpoint.go:585] Attempting port map for: chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_tcp -> {ServiceID:controlplane_logstash_tcp InstanceID:0 Application:controlplane_logstash_tcp Purpose: HostID: HostIP:10.209.8.12 HostPort:5042 ContainerID: ContainerIP:127.0.0.1 ContainerPort:5042 Protocol:tcp VirtualAddress: ProxyPort:5042}
I0310 18:47:22.393578 00001 endpoint.go:605] Success binding port: chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_tcp -> proxy[{controlplane_logstash_tcp 0 controlplane_logstash_tcp   10.209.8.12 5042  127.0.0.1 5042 tcp  5042}; &{%!s(*net.netFD=&{{0 0 0} 11 2 1 false tcp4 0xc20818a870 <nil> {140633420050768}})}]=>[]
I0310 18:47:22.393706 00001 endpoint.go:270]   cached imported endpoint[chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_tcp]: {endpointID:controlplane_logstash_tcp instanceID:0 virtualAddress: purpose:import port:5042}
I0310 18:47:22.393745 00001 endpoint.go:585] Attempting port map for: chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_lumberjack -> {ServiceID:controlplane_logstash_lumberjack InstanceID:0 Application:controlplane_logstash_lumberjack Purpose: HostID: HostIP:10.209.8.12 HostPort:5043 ContainerID: ContainerIP:127.0.0.1 ContainerPort:5043 Protocol:tcp VirtualAddress: ProxyPort:5043}
I0310 18:47:22.393853 00001 endpoint.go:605] Success binding port: chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_lumberjack -> proxy[{controlplane_logstash_lumberjack 0 controlplane_logstash_lumberjack   10.209.8.12 5043  127.0.0.1 5043 tcp  5043}; &{%!s(*net.netFD=&{{0 0 0} 12 2 1 false tcp4 0xc20818ac30 <nil> {140633420050576}})}]=>[]
I0310 18:47:22.394652 00001 endpoint.go:270]   cached imported endpoint[chzv9aasqaqwbifwju30sjm8c_controlplane_logstash_lumberjack]: {endpointID:controlplane_logstash_lumberjack instanceID:0 virtualAddress: purpose:import port:5043}
I0310 18:47:22.394701 00001 endpoint.go:585] Attempting port map for: chzv9aasqaqwbifwju30sjm8c_controlplane_consumer -> {ServiceID:controlplane_consumer InstanceID:0 Application:controlplane_consumer Purpose: HostID: HostIP:10.209.8.12 HostPort:8443 ContainerID: ContainerIP:127.0.0.1 ContainerPort:8443 Protocol:tcp VirtualAddress: ProxyPort:8444}
I0310 18:47:22.394791 00001 endpoint.go:605] Success binding port: chzv9aasqaqwbifwju30sjm8c_controlplane_consumer -> proxy[{controlplane_consumer 0 controlplane_consumer   10.209.8.12 8443  127.0.0.1 8443 tcp  8444}; &{%!s(*net.netFD=&{{0 0 0} 13 2 1 false tcp4 0xc20818aff0 <nil> {140633420050384}})}]=>[]
I0310 18:47:22.394924 00001 endpoint.go:270]   cached imported endpoint[chzv9aasqaqwbifwju30sjm8c_controlplane_consumer]: {endpointID:controlplane_consumer instanceID:0 virtualAddress: purpose:import port:8443}
I0310 18:47:22.395011 00001 controller.go:722] No prereqs to pass.
I0310 18:47:22.416856 00001 endpoint.go:376] Starting watch for tenantEndpointKey chzv9aasqaqwbifwju30sjm8c_zproxy: <nil>
I0310 18:47:22.416930 00001 endpoint.go:376] Starting watch for tenantEndpointKey chzv9aasqaqwbifwju30sjm8c_redis: <nil>
I0310 18:47:22.425347 00001 endpoint.go:585] Attempting port map for: chzv9aasqaqwbifwju30sjm8c_zproxy -> {ServiceID:chzv9aasqaqwbifwju30sjm8c InstanceID:0 Application:zproxy Purpose:export HostID:d10a0c08 HostIP:10.209.8.12 HostPort:33757 ContainerID:20df2a99b04b2b283984479d6b6ad55db8d1243abd8802164f4ddbf4c7d87127 ContainerIP:172.17.0.35 ContainerPort:8080 Protocol:tcp VirtualAddress: ProxyPort:8080}
I0310 18:47:22.425478 00001 endpoint.go:605] Success binding port: chzv9aasqaqwbifwju30sjm8c_zproxy -> proxy[{chzv9aasqaqwbifwju30sjm8c 0 zproxy export d10a0c08 10.209.8.12 33757 20df2a99b04b2b283984479d6b6ad55db8d1243abd8802164f4ddbf4c7d87127 172.17.0.35 8080 tcp  8080}; &{%!s(*net.netFD=&{{0 0 0} 14 2 1 false tcp4 0xc208a85890 <nil> {140633420050192}})}]=>[]
I0310 18:47:22.425705 00001 endpoint.go:585] Attempting port map for: chzv9aasqaqwbifwju30sjm8c_redis -> {ServiceID:2s87lenozczborbz01kbs9fke InstanceID:0 Application:redis Purpose:export HostID:d10a0c08 HostIP:10.209.8.12 HostPort:33751 ContainerID:ad6d2631e2399a12afafea1ace676734056c286835f9647fa7733eeda5396f4a ContainerIP:172.17.0.31 ContainerPort:6379 Protocol:tcp VirtualAddress: ProxyPort:6379}
I0310 18:47:22.425801 00001 endpoint.go:605] Success binding port: chzv9aasqaqwbifwju30sjm8c_redis -> proxy[{2s87lenozczborbz01kbs9fke 0 redis export d10a0c08 10.209.8.12 33751 ad6d2631e2399a12afafea1ace676734056c286835f9647fa7733eeda5396f4a 172.17.0.31 6379 tcp  6379}; &{%!s(*net.netFD=&{{0 0 0} 15 2 1 false tcp4 0xc208a85bf0 <nil> {140633420050000}})}]=>[]
I0310 18:47:22.475228 00001 controller.go:777] Kicking off health check redis_answering.
I0310 18:47:22.475288 00001 controller.go:778] Setting up health check: /opt/zenoss/bin/healthchecks/redis_answering
I0310 18:47:22.475304 00001 controller.go:777] Kicking off health check running.
I0310 18:47:22.475315 00001 controller.go:778] Setting up health check: pgrep -u zenoss metricshipper
I0310 18:47:22.475326 00001 controller.go:777] Kicking off health check store_answering.
I0310 18:47:22.475336 00001 controller.go:778] Setting up health check: /opt/zenoss/bin/healthchecks/MetricShipper/store_answering
I0310 18:47:22.480751 00001 controller.go:664] Starting service process for service 7fhb0p5uqjof9stbvitno6f8k
I0310 18:47:22.480822 00001 instance.go:87] about to execute: /bin/sh , [-c exec su - zenoss -c "cd /opt/zenoss && /bin/supervisord -n -c etc/metricshipper/supervisord.conf"][2]
2016/03/10 18:47:22.694006 Setting trusted CA from file: /usr/local/serviced/resources/logstash/logstash-forwarder.crt
2016/03/10 18:47:22.694497 Connecting to 127.0.0.1:5043 (127.0.0.1) 
2016/03/10 18:47:22.789613 Connected to 127.0.0.1
Trying to connect to logstash server... 127.0.0.1:5042
Connected to logstash server.
2016-03-10 18:47:24,766 WARN Included extra file "/opt/zenoss/etc/metricshipper/metricshipper_supervisor.conf" during parsing
2016-03-10 18:47:24,919 INFO RPC interface 'supervisor' initialized
2016-03-10 18:47:24,919 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-03-10 18:47:24,920 INFO supervisord started with pid 37
2016-03-10 18:47:25,924 INFO spawned: 'metricshipper' with pid 40
2016/03/10 18:47:27.345029 Registrar received 3 events
2016-03-10 18:47:31,284 INFO success: metricshipper entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
W0310 18:47:33.154986 00001 controller.go:833] Health check "store_answering" failed.%!(EXTRA *exec.ExitError=exit status 1)
2016/03/10 18:47:34.836647 Registrar received 7 events
2016/03/10 18:47:37 200 6.28856ms POST /api/metrics/store
2016/03/10 18:47:42.340250 Registrar received 7 events
W0310 18:47:43.354601 00001 controller.go:833] Health check "store_answering" failed.%!(EXTRA *exec.ExitError=exit status 1)
2016/03/10 18:47:49.835728 Registrar received 8 events
2016/03/10 18:47:52 200 3.532288ms POST /api/metrics/store
W0310 18:47:53.450854 00001 controller.go:833] Health check "store_answering" failed.%!(EXTRA *exec.ExitError=exit status 1)
2016/03/10 18:47:54.835128 Registrar received 4 events
2016/03/10 18:47:59.839456 Registrar received 5 events

The other issue is I can't login to Zenoss, not even with the two local accounts I created when I built the server. Both of these accounts worked before upgrading Zenoss core to 5.1.1.

Any help would be appreciated.

Well, folks, if you're planning to upgrade to v5.1.1, be sure that you've got no snapshots inadvertently lying around before you begin. I installed a ZenPack and didn't remove the snapshot, and by page 34 of the upgrade guide for v5.1.1, the upgrade script can't run due to serviced being unable to access the Core container any longer. Pity the MariaDB instance wasn't separate.

Rebuild time for me. Make sure you commit and remove all auto-generated snapshots before you start.

I can't get the timezone right for the email body, maintenance windows and also logs in the control center, however the events tab has the correct time. 

I have set the timezone correctly in both the OS and container for EDT but it still shows as UTC in the mentioned areas.

as title,

any information about Zenoss's websso?

does any one has solution about that?

many thanks!

I have been referred to the ova demo. I'm trying to track down a tutorial regarding how to get it installed and then what I can do with it.

Is anyone aware of any web posts, blogs, magazine articles, etc. that walk one through a basic intro to Zenoss from installing the ova to getting results on the screen?

If everyone is faced with starting from scratch, then so be it. But if I can find tips to avoid common problems, I'm all for that.

Thank you.