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 17 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/comment/22541 (2016-01-08)
    Open archived version from archive


  • Zenoss Community - Open Source Network Monitoring and Systems Management
    Submitted by Joanypony on Fri 10 02 2015 09 24 Forums 5 x Testing Hi I m currently setting up a test enviroment with Zenoss 5 I need to be sure it can scale to pretty large numbers Traditionally we 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

    Original URL path: http://www.zenoss.org/tags/zenoss5-multiple-instances-zencommand-scale-scaling (2016-01-08)
    Open archived version from archive

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    our community Zenoss 5 install problem in centos 7 Zenoss 5 Zenoss ServiceD unable to start in centos 7 Submitted by Sunnybmv on Mon 04 20 2015 04 22 Forums 5 x Testing Hi Team Zenoss ServiceD unable to start in centos 7 Here is the output and var log messages Could you please help us to start the serviceD Not able to get which is causing the issue Read

    Original URL path: http://www.zenoss.org/tags/zenoss-5-install-problem-centos-7 (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 4 hours 27 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 20 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 20 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 4 hours 27 min ago Joined 04 20 2014

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

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    Join our community ip 5 0 6 Changing Host IPs Submitted by Ddelay on Wed 09 30 2015 15 52 Forums 5 x Testing So I ve noticed a problem with Core 5 0 6 and changing IPs Installation works like it should I can get everything up and running and monitoring just fine but when I change the IP on the host Zenoss stops being able to ping anything

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

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    Join our community core 5 5 0 6 Changing Host IPs Submitted by Ddelay on Wed 09 30 2015 15 52 Forums 5 x Testing So I ve noticed a problem with Core 5 0 6 and changing IPs Installation works like it should I can get everything up and running and monitoring just fine but when I change the IP on the host Zenoss stops being able to ping

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

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    2015 15 52 Forums 5 x Testing So I ve noticed a problem with Core 5 0 6 and changing IPs Installation works like it should I can get everything up and running and monitoring just fine but when I change the IP on the host Zenoss stops being able to ping anything at all Read more about 5 0 6 Changing Host IPs 2 comments Log in to post comments Unable To Add Resource Host Submitted by Ddelay on Fri 09 04 2015 12 57 Forums Control Center I have recently been trying to add another host to my Control Center in order to add it to a new resource pool but I have been unsuccessful so far When attempting to add the host I keep getting the same error Internal Server Error SERVICED REGISTRY is false and hostid d10a0840 does not match master d10a0f40 Read more about Unable To Add Resource Host 1 comment Log in to post comments Upgrade to Zenoss 5 0 3 Step 5 on upgrade guide am I missing something Submitted by Mdonaldson87 on Tue 07 21 2015 08 18 Forums Community Zenoss Support Hi Zenoss community I was looking into upgrading our Zenoss 5 0 2 to Zenoss 5 0 4 but I have to go to 5 0 3 first which is fine however when I get to upgrading Zenoss core I am following this guide http www zenoss com sites default files documentation Zenoss Core Upgr However I cannot see an upgrade script for 5 0 3 so when I run serviced script run root 5 0 x 5 0 3 upgrade core txt service Zenoss core Read more about Upgrade to Zenoss 5 0 3 Step 5 on upgrade guide am I missing something 6 comments Log in to post

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

  • Zenoss Community - Open Source Network Monitoring and Systems Management
    2015 15 52 Forums 5 x Testing So I ve noticed a problem with Core 5 0 6 and changing IPs Installation works like it should I can get everything up and running and monitoring just fine but when I change the IP on the host Zenoss stops being able to ping anything at all Read more about 5 0 6 Changing Host IPs 2 comments Log in to post

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