archive-org.com » ORG » Z » ZENOSS.ORG

Total: 955

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Zenoss Community - Open Source Network Monitoring and Systems Management
    42 2 Rcocchiararo Offline Last seen 1 month 4 weeks ago Joined 03 26 2015 16 00 Posts 72 have you restarted zenoss have you restarted zenoss after commiting Also for a zenpack wmware esxi monitor i had to attach to zenhub container dunno if that might make a difference Top Log in to post comments Thu 06 18 2015 13 00 3 Trojahn Offline Last seen 1 week 3 days ago Joined 01 30 2015 08 57 Posts 21 Yep I did it now I should have come here and posted how to solve it Thanks for the time to answer it anyway Top Log in to post comments Mon 12 28 2015 05 33 4 Bcmonitor Offline Last seen 1 day 16 hours ago Joined 10 12 2015 01 06 Posts 4 Same Issue Hello Trojahn I m facing same issue Installation is exaclty same as yours Restarted zenoss Still getting same error Executing command usr sbin fping args omitted against 10 10 254 224 bin sh usr sbin fping No such file or directory My Zenoss 5 installation can t execute the command fping which is installed on the system I understand that the container may not have access to the outside but how can I add fping to it I already did this as I found on another post serviced service shell s Fping i Zope bash wget ftp fr2 rpmfind net linux dag redhat el7 en x86 64 dag RPMS fping 3 10 rpm ivh fping 3 10 1 el7 rf x86 64 rpm exit serviced snapshot commit Fping serviced service shell i Zope bash fping 10 10 254 224 10 10 254 224 is alive Even though the command is accessible from the container if I run it from the Zenoss web interface I get the following Preparing Command Executing command usr sbin fping args omitted against 10 10 254 224 bin sh usr sbin fping No such file or directory DONE in 0 seconds So my conclusion is that the command should be installed elsewhere not in the Zope container Where do I install it Top Log in to post comments Mon 12 28 2015 07 25 5 Trojahn Offline Last seen 1 week 3 days ago Joined 01 30 2015 08 57 Posts 21 Can t help you What I did Can t help you What I did is already on my initial post After that I completelly gave up on Zenoss 5 and went back to 4x After a UPS fail my Zenoss instalation was LOST docker couldn t find any containers to start and since I wasted too much time trying to figure out this whole Docker thing just to get Zenoss installed I decided to go back to 4x I think Zenoss and Docker either were a bad move or just too alpha for my use As IT sometimes we are just too busy to add another point of failure to our infrastructure and time is money I hope

    Original URL path: http://www.zenoss.org/forum/9481 (2016-01-08)
    Open archived version from archive


  • Zenoss Community - Open Source Network Monitoring and Systems Management
    have used Zenoss Core 3 2 1 and have always had issues with zencommand saturation We use a combination of extra logical collectors and remote collectors to deal with the load and zencommand saturation While researching we found this article http wiki zenoss org Zenoss Core 5 Scaling We set up 3 instances of zencommand but we still only have a single collector Then we wanted to test if the work was being shared between the 3 zencommand instances or just being done in triplicate I set zencommand to log in debug mode tailed the zencommand log from each docker container then searched for a particular check on a particular host This check only polls every 5 minutes Unfortunately I see the test being done every 5 minutes on each zencommand instance Does anyone have any ideas on how to make the instances share the work I ve have a screenshot which shows the same test on the same host being polled at 5 minute intervals by each zencommand instance Not sure how to attach it though or if they re allowed on this forum Thanks Joan Tags Zenoss5 multiple instances zencommand scale scaling Top Log in to post comments Fri 10 02 2015 09 32 2 Joanypony Offline Last seen 2 weeks 6 days ago Joined 05 27 2014 03 58 Posts 24 Meh I m trying to add logs Meh I m trying to add logs but I keep triggering the spam filter I ll try and get them up at some point Top Log in to post comments Thu 12 17 2015 14 16 3 Ddelay Offline Last seen 12 hours 37 min ago Joined 04 17 2015 09 24 Posts 14 Any update on this I m Any update on this I m running into the

    Original URL path: http://www.zenoss.org/forum/135606 (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    Device Prepare scheduled Apr 20 05 25 34 hostname avahi daemon 809 Withdrawing address record for fe80 742d 49ff fe4d a662 on veth9a97538 Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 1 of 5 Device Prepare started Apr 20 05 25 34 hostname NetworkManager 818 info veth9a97538 device state change disconnected prepare reason none 30 40 0 Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 2 of 5 Device Configure scheduled Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 1 of 5 Device Prepare complete Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 2 of 5 Device Configure starting Apr 20 05 25 34 hostname NetworkManager 818 info veth9a97538 device state change prepare config reason none 40 50 0 Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 2 of 5 Device Configure successful Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 3 of 5 IP Configure Start scheduled Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 2 of 5 Device Configure complete Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 3 of 5 IP Configure Start started Apr 20 05 25 34 hostname NetworkManager 818 info veth9a97538 device state change config ip config reason none 50 70 0 Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Beginning DHCPv4 transaction timeout in 45 seconds Apr 20 05 25 34 hostname NetworkManager 818 info dhclient started with pid 12586 Apr 20 05 25 34 hostname NetworkManager 818 info Activation veth9a97538 Stage 3 of 5 IP Configure Start complete Apr 20 05 25 34 hostname dhclient 12586 Internet Systems Consortium DHCP Client 4 2 5 Apr 20 05 25 34 hostname dhclient 12586 Copyright 2004 2013 Internet Systems Consortium Apr 20 05 25 34 hostname dhclient 12586 All rights reserved Apr 20 05 25 34 hostname dhclient 12586 For info please visit https www isc org software dhcp Apr 20 05 25 34 hostname dhclient 12586 Apr 20 05 25 34 hostname NetworkManager Internet Systems Consortium DHCP Client 4 2 5 Apr 20 05 25 34 hostname NetworkManager Copyright 2004 2013 Internet Systems Consortium Apr 20 05 25 34 hostname NetworkManager All rights reserved Apr 20 05 25 34 hostname NetworkManager For info please visit https www isc org software dhcp Apr 20 05 25 34 hostname dhclient 12586 Listening on LPF veth9a97538 76 2d 49 4d a6 62 Apr 20 05 25 34 hostname dhclient 12586 Sending on LPF veth9a97538 76 2d 49 4d a6 62 Apr 20 05 25 34 hostname dhclient 12586 Sending on Socket fallback Apr 20 05 25 34 hostname dhclient 12586 DHCPDISCOVER on veth9a97538 to 255 255 255 255 port 67 interval 4 xid 0x7c5157b9 Apr 20 05 25 34 hostname NetworkManager 818 info veth9a97538 DHCPv4 state changed nbi preinit Apr 20 05 25 34 hostname NetworkManager Listening on LPF veth9a97538 76 2d 49 4d a6 62 Apr 20 05 25 34 hostname NetworkManager Sending on LPF veth9a97538 76 2d 49 4d a6 62 Apr 20 05 25 34 hostname NetworkManager Sending on Socket fallback Apr 20 05 25 34 hostname NetworkManager DHCPDISCOVER on veth9a97538 to 255 255 255 255 port 67 interval 4 xid 0x7c5157b9 Apr 20 05 25 35 hostname ntpd 1239 Deleting interface 14 veth9a97538 fe80 742d 49ff fe4d a662 123 interface stats received 0 sent 0 dropped 0 active t ime 43 secs Apr 20 05 25 35 hostname avahi daemon 809 Registering new address record for fe80 742d 49ff fe4d a662 on veth9a97538 Apr 20 05 25 37 hostname ntpd 1239 Listen normally on 15 veth9a97538 fe80 742d 49ff fe4d a662 UDP 123 Apr 20 05 26 13 hostname docker time 2015 04 20T05 26 13 04 00 level info msg job release interface 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc09 0a6233c73e8 OK 0 Apr 20 05 26 13 hostname docker time 2015 04 20T05 26 13 04 00 level info msg job log stop 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c7 3e8 zenoss serviced isvcs v26 Apr 20 05 26 13 hostname docker time 2015 04 20T05 26 13 04 00 level info msg job log stop 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c7 3e8 zenoss serviced isvcs v26 OK 0 Apr 20 05 26 13 hostname docker time 2015 04 20T05 26 13 04 00 level info msg job stop 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c73e8 OK 0 Apr 20 05 26 13 hostname docker write unix broken pipe Apr 20 05 26 13 hostname docker time 2015 04 20T05 26 13 04 00 level info msg job events ERR 1 Apr 20 05 26 14 hostname docker time 2015 04 20T05 26 13 04 00 level error msg Handler for GET events returned error write unix broken pipe Apr 20 05 26 14 hostname docker time 2015 04 20T05 26 13 04 00 level error msg HTTP Error statusCode 500 write unix broken pipe Apr 20 05 26 14 hostname docker 2015 04 20 05 26 13 http multiple response WriteHeader calls Apr 20 05 26 14 hostname serviced systemd sh 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c73e8 Apr 20 05 26 14 hostname docker time 2015 04 20T05 26 14 04 00 level info msg POST v1 17 containers c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb 97892015059 stop t 10 Apr 20 05 26 14 hostname docker time 2015 04 20T05 26 14 04 00 level info msg job stop c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 Apr 20 05 26 16 hostname dhclient 12586 DHCPDISCOVER on veth9a97538 to 255 255 255 255 port 67 interval 12 xid 0x7c5157b9 Apr 20 05 26 16 hostname NetworkManager DHCPDISCOVER on veth9a97538 to 255 255 255 255 port 67 interval 12 xid 0x7c5157b9 Apr 20 05 26 19 hostname NetworkManager 818 warn veth9a97538 DHCPv4 request timed out Apr 20 05 26 19 hostname NetworkManager 818 info veth9a97538 canceled DHCP transaction DHCP client pid 12586 Apr 20 05 26 19 hostname NetworkManager 818 info Activation veth9a97538 Stage 4 of 5 IPv4 Configure Timeout scheduled Apr 20 05 26 19 hostname NetworkManager 818 info Activation veth9a97538 Stage 4 of 5 IPv4 Configure Timeout started Apr 20 05 26 19 hostname NetworkManager 818 info veth9a97538 device state change ip config failed reason ip config unavailable 70 120 5 Apr 20 05 26 19 hostname NetworkManager 818 info Disabling autoconnect for connection Wired connection 2 Apr 20 05 26 19 hostname NetworkManager 818 warn Activation veth9a97538 failed for connection Wired connection 2 Apr 20 05 26 19 hostname NetworkManager 818 info Activation veth9a97538 Stage 4 of 5 IPv4 Configure Timeout complete Apr 20 05 26 19 hostname NetworkManager 818 info veth9a97538 device state change failed disconnected reason none 120 30 0 Apr 20 05 26 19 hostname NetworkManager 818 info veth9a97538 deactivating device reason none 0 Apr 20 05 26 19 hostname avahi daemon 809 Withdrawing address record for fe80 742d 49ff fe4d a662 on veth9a97538 Apr 20 05 26 20 hostname ntpd 1239 Deleting interface 15 veth9a97538 fe80 742d 49ff fe4d a662 123 interface stats received 0 sent 0 dropped 0 active t ime 43 secs Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg Container c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 f ailed to exit within 10 seconds of SIGTERM using the force Apr 20 05 26 24 hostname kernel docker0 port 3 veth9a97538 entered disabled state Apr 20 05 26 24 hostname NetworkManager 818 info veth9a97538 device state change disconnected unmanaged reason removed 30 10 36 Apr 20 05 26 24 hostname avahi daemon 809 Withdrawing workstation service for veth9a97538 Apr 20 05 26 24 hostname kernel device veth9a97538 left promiscuous mode Apr 20 05 26 24 hostname kernel docker0 port 3 veth9a97538 entered disabled state Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg job log die c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb978920150 59 zenoss serviced isvcs v26 Apr 20 05 26 24 hostname NetworkManager 818 info docker0 link disconnected deferring action for 4 seconds Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg job release interface c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 OK 0 Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg job log stop c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 zenoss serviced isvcs v26 Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg job log stop c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 zenoss serviced isvcs v26 OK 0 Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg job stop c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 OK 0 Apr 20 05 26 24 hostname serviced systemd sh c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg POST v1 17 containers dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab stop t 10 Apr 20 05 26 24 hostname docker time 2015 04 20T05 26 24 04 00 level info msg job stop dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab Apr 20 05 26 28 hostname NetworkManager 818 info docker0 link disconnected calling deferred action Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg Container dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab failed to exit within 10 seconds of SIGTERM using the force Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg job log die dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab zenoss serviced isvcs v26 Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg job log die dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab zenoss serviced isvcs v26 OK 0 Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg job log stop dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab zenoss serviced isvcs v26 Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg job log stop dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab zenoss serviced isvcs v26 OK 0 Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg job stop dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab OK 0 Apr 20 05 26 34 hostname serviced systemd sh dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg POST v1 17 containers 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa stop t 10 Apr 20 05 26 34 hostname docker time 2015 04 20T05 26 34 04 00 level info msg job stop 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa Apr 20 05 26 42 hostname docker time 2015 04 20T05 26 42 04 00 level info msg job log die 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa zenoss serviced isvcs v26 Apr 20 05 26 42 hostname docker time 2015 04 20T05 26 42 04 00 level info msg job log die 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa zenoss serviced isvcs v26 OK 0 Apr 20 05 26 42 hostname docker time 2015 04 20T05 26 42 04 00 level info msg job log stop 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa zenoss serviced isvcs v26 Apr 20 05 26 42 hostname docker time 2015 04 20T05 26 42 04 00 level info msg job log stop 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa zenoss serviced isvcs v26 OK 0 Apr 20 05 26 42 hostname docker time 2015 04 20T05 26 42 04 00 level info msg job stop 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa OK 0 Apr 20 05 26 42 hostname serviced systemd sh 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa Apr 20 05 26 42 hostname serviced systemd sh Mon Apr 20 09 26 42 UTC 2015 serviced is now stopped done with post stop Apr 20 05 26 42 hostname systemd Unit serviced service entered failed state Top Log in to post comments Mon 04 20 2015 04 51 3 Jan garaj Offline Last seen 3 hours 47 min ago Joined 04 20 2014 16 23 Posts 380 You have provided short log Apr 20 05 15 19 hostname NetworkManager 818 error 1429521319 061616 platform nm linux platform c 1841 link change Netlink error changing link invalid link 0x7f50cea4e730 No such device Apr 20 05 16 31 hostname serviced E0420 09 16 31 400054 10901 manager go 293 Error starting isvc docker registry could not startup docker registry container maybe some network issue Did you follow installation guide See Grafana 2 for Zenoss 5 Zenoss 4 soon Contact Devops Monitoring zExpert for paid Zenoss support www jangaraj com Top Log in to post comments Mon 04 20 2015 06 37 4 Sunnybmv Offline Last seen 3 days 19 hours ago Joined 04 20 2015 04 03 Posts 22 Hi I followed the Hi I followed the installation guide Not sure how to fix this https beta zenoss io Core 5 Beta 3 Documentation Zenoss Core Beta Inst when i started serviced its creating the below interfaces veth2229db8 flags 67 UP BROADCAST RUNNING mtu 1500 ether 22 ab 8f b8 59 da txqueuelen 0 Ethernet RX packets 8 bytes 648 648 0 B RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 1728 1 6 KiB TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth38957f3 flags 67 UP BROADCAST RUNNING mtu 1500 ether 02 59 f4 4b 7f 8c txqueuelen 0 Ethernet RX packets 8 bytes 648 648 0 B RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13 bytes 1010 1010 0 B TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth68bcab8 flags 67 UP BROADCAST RUNNING mtu 1500 ether 7a d8 b3 12 f2 7d txqueuelen 0 Ethernet RX packets 12 bytes 840 840 0 B RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 1660 1 6 KiB TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth8ab841b flags 4163 UP BROADCAST RUNNING MULTICAST mtu 1500 inet6 fe80 58af 6cff fe7d 82c1 prefixlen 64 scopeid 0x20 link ether 5a af 6c 7d 82 c1 txqueuelen 0 Ethernet RX packets 8 bytes 648 648 0 B RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14 bytes 1884 1 8 KiB TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Getting the error incmd journalctl u serviced f E0420 11 33 31 087346 18872 manager go 293 Error starting isvc docker registry could not start ontainer can you help me to fix this Regards Satya Top Log in to post comments Mon 04 20 2015 07 27 5 Sunnybmv Offline Last seen 3 days 19 hours ago Joined 04 20 2015 04 03 Posts 22 I tried to install through I tried to install through Autodeploy script Getting the errors any idea Output of Autodeploy script 3 9 Start the Control Center service systemctl enable serviced systemctl start serviced Done 4 Zenoss Core 5 deployement Mon 20 Apr 2015 08 11 19 0400 4 1 Adding current host to the default resource pool Please be patient because docker image zenoss serviced isvcs must be downloaded before first start You can check progress in new console journalctl u serviced f a Script is trying to check status every 10s Timeout for this step is 15 minutes serviced host list 2 1 could not create a client to the master dial tcp X X X X 4979 connection refused 1 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 2 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 3 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 4 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 5 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 6 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts rpc can t find service Master GetHosts 64 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 65 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds rpc can t find service Master GetHosts 66 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused 67 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused 68 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused 69 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused 70 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused 71 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused 72 This is not a problem because Control Centre service is not fully started I m trying in 10 seconds could not create a client to the master dial tcp X X X X 4979 connection refused Top Log in to post comments Mon 04 20 2015 08 23 6 Jan garaj Offline Last seen 3 hours 47 min ago Joined 04 20 2014

    Original URL path: http://www.zenoss.org/forum/8811 (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    network 3 edit etc hosts to update the IP 4 systemctl start serviced 5 Add the new IP to the hosts tab in control center and make sure RabbitMQ zenmail zensyslog and zentrap are all pointing to the new host All the processes then start fine and are running and passing the health check However when I add or ping any device other than the host itself Zenoss cannot ping anything I can ping from the CentOS command line but once I attach to Zenoss core I can t ping anything other than the host IP Anyone seen this before Is there another config file I might need to adjust I ve been messing around in Zenoss core but have yet to find a fix Tags ip core 5 zenoss 5 zenoss core 5 0 6 ip change add host Host host change Top Log in to post comments Wed 10 21 2015 13 58 2 Ddelay Offline Last seen 12 hours 37 min ago Joined 04 17 2015 09 24 Posts 14 Since nobody has offered any Since nobody has offered any insight and this is also occurring on 5 0 7 I have created a ticket on jira

    Original URL path: http://www.zenoss.org/forum/135566 (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    DeviceSearch 1 2 0 py2 7 egg ZenPacks zenoss DigMonitor opt zenoss ZenPacks ZenPacks zenoss DigMonitor 1 1 0 py2 7 egg ZenPacks zenoss DnsMonitor opt zenoss ZenPacks ZenPacks zenoss DnsMonitor 2 1 0 py2 7 egg ZenPacks zenoss FtpMonitor opt zenoss ZenPacks ZenPacks zenoss FtpMonitor 1 1 0 py2 7 egg ZenPacks zenoss HPMonitor opt zenoss ZenPacks ZenPacks zenoss HPMonitor 2 1 0 py2 7 egg ZenPacks zenoss HttpMonitor opt zenoss ZenPacks ZenPacks zenoss HttpMonitor 2 1 0 py2 7 egg ZenPacks zenoss LDAPMonitor opt zenoss ZenPacks ZenPacks zenoss LDAPMonitor 1 4 1 py2 7 egg ZenPacks zenoss LinuxMonitor opt zenoss ZenPacks ZenPacks zenoss LinuxMonitor 1 3 0 py2 7 egg ZenPacks zenoss Microsoft Windows opt zenoss ZenPacks ZenPacks zenoss Microsoft Windows 2 3 1 py2 7 egg ZenPacks zenoss MySqlMonitor opt zenoss ZenPacks ZenPacks zenoss MySqlMonitor 3 0 5 py2 7 egg ZenPacks zenoss NtpMonitor opt zenoss ZenPacks ZenPacks zenoss NtpMonitor 2 2 1 py2 7 egg ZenPacks zenoss PythonCollector opt zenoss ZenPacks ZenPacks zenoss PythonCollector 1 6 4 py2 7 egg ZenPacks zenoss ZenJMX opt zenoss ZenPacks ZenPacks zenoss ZenJMX 3 11 0 py2 7 egg Top Log in to post comments Wed 06 10 2015 12 33 3 Rbeyers Offline Last seen 1 day 9 hours ago Joined 04 07 2015 19 53 Posts 21 found issue I found the dump rdb under opt serviced var volumes 69fv54vci7vkzdrbtw61yr80u localhost localhost collectorredis I moved it to another folder and restarted the collectorredis successfully Checking on the Windows update now to see if that remains broken but wanted to update on the fix Top Log in to post comments Wed 06 17 2015 08 12 4 Danielezenoss Offline Last seen 6 months 1 day ago Joined 05 28 2015 23 23 Posts 8 Redis server failed to start HI I ve a similar problem but is Redis server that fails to start The reason why it doesn t start is about the metrics health check failure Below the Redis log Connected to logstash server 2015 06 15 04 32 01 911023 Registrar received 21 events I0615 04 32 06 934667 00001 controller go 612 Starting service process I0615 04 32 06 934794 00001 instance go 79 about to execute bin sh c exec usr bin redis server etc redis conf 2 I0615 04 32 06 953254 00001 controller go 606 Restarting service process in 10 seconds 2015 06 15 04 32 09 410892 Registrar received 21 events 2015 06 15 04 32 11 200 2 104299ms POST api metrics store W0615 04 32 11 985135 00001 controller go 777 Health check metrics failed I0615 04 32 16 953504 00001 controller go 612 Starting service process I0615 04 32 16 953628 00001 instance go 79 about to execute bin sh c exec usr bin redis server etc redis conf 2 I0615 04 32 16 972532 00001 controller go 606 Restarting service process in 10 seconds 2015 06 15 04 32 19 409330 Registrar received 21 events 2015 06 15

    Original URL path: http://www.zenoss.org/forum/9456 (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    performance graphs like in version 4 x Specifically I m looking to get data point rates and the total number data points I can t seem to find it in the documentation or from clicking around In zenoss 4x it was under Advanced Collectors Performance Im currently running 5 0 8 in a test environment and I think I found where it would be located Advanced Control Center then in

    Original URL path: http://www.zenoss.org/forum/136661 (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    01 39 1 Jen c Offline Last seen 1 month 2 weeks ago Joined 09 20 2015 21 24 Posts 18 Deploying application template failed Internal Server Error could not look up image zenoss core 5 0 5 0 8 1 docker no such i I receive this error everytime I try to start zenoss core application Top Log in to post comments Mon 11 30 2015 13 14 2

    Original URL path: http://www.zenoss.org/forum/136446 (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    just about any data request can take up to a minute or more It seems that actions that interact with the DB are horribly slow because the screen draws quickly but returned data takes forever What can I do to improve the performance and why is it so slow Top Log in to post comments Thu 11 12 2015 15 19 2 Trelane Offline Last seen 6 hours 23 min ago Joined 12 28 2013 12 43 Posts 971 Go into Control Center add 2 Go into Control Center add 2 3 ZenHub workers and 2 3 Zope instances Hi I m Andrew Kirch the Community Manager at Zenoss Top Log in to post comments Thu 11 19 2015 06 08 3 Ejlorson Offline Last seen 1 month 2 weeks ago Joined 11 04 2015 07 21 Posts 10 I added 3 of each and it I added 3 of each and it really did not help I only have 18 devices in the system I am really struggling because I have not found any good sizing docs for 5 Where is realistic sizing information Top Log in to post comments Mon 11 30 2015 10 32 4 Trelane Offline

    Original URL path: http://www.zenoss.org/forum/136381 (2016-01-08)
    Open archived version from archive