Configuration & Administration

Expand all | Collapse all

not able to add devices using zendisc command

  • 1.  not able to add devices using zendisc command

    Posted 08-09-2018 04:38 AM
    Hi,

    I am able to add devices using graphical interface but when I try to add the devices using zendisc, I am getting following error:


    [zenoss@enzenoss1 ~]$ /opt/zenoss/bin/zendisc run -v 10  --now -d enlogin4.en.desres.deshaw.com --monitor localhost --deviceclass /Server/Linux/enlogin --prod_state 1000

    2018-08-09 04:38:02,868 DEBUG zen.ZenDisc: Run in foreground, starting immediately.

    2018-08-09 04:38:02,872 DEBUG zen.pysamba: client ntlmv2 auth is now no

    2018-08-09 04:38:02,872 DEBUG zen.ZenDisc: Starting PBDaemon initialization

    2018-08-09 04:38:02,872 INFO zen.ZenDisc: Connecting to localhost:8789

    2018-08-09 04:38:02,876 DEBUG zen.pbclientfactory: Starting connection...

    2018-08-09 04:38:02,877 DEBUG zen.ZenDisc: Logging in as admin

    2018-08-09 04:38:02,878 DEBUG zen.pbclientfactory: Connected

    2018-08-09 04:38:02,878 DEBUG zen.pbclientfactory: Cancelling connect timeout

    2018-08-09 04:38:02,878 DEBUG zen.pbclientfactory: Sending credentials

    2018-08-09 04:38:02,887 DEBUG zen.pbclientfactory: Cancelling connect timeout

    2018-08-09 04:38:02,887 INFO zen.ZenDisc: Connected to ZenHub

    2018-08-09 04:38:02,887 DEBUG zen.ZenDisc: Setting up initial services: EventService, DiscoverService

    2018-08-09 04:38:02,887 DEBUG zen.ZenDisc: Chaining getInitialServices with d2

    2018-08-09 04:38:02,894 DEBUG zen.ZenDisc: Loaded service EventService from zenhub

    2018-08-09 04:38:02,894 DEBUG zen.ZenDisc: Loaded service DiscoverService from zenhub

    2018-08-09 04:38:02,895 DEBUG zen.ZenDisc: Queued event (total of 1) {'rcvtime': 1533803882.895124, 'severity': 0, 'component': 'zendisc', 'agent': 'zendisc', 'summary': 'started', 'manager': 'enzenoss1.en.desres.deshaw.com', 'device': 'localhost', 'eventClass': '/App/Start', 'monitor': 'localhost'}

    2018-08-09 04:38:02,896 DEBUG zen.ZenDisc: Sending 1 events, 0 perf events, 0 heartbeats

    2018-08-09 04:38:02,896 DEBUG zen.ZenDisc: Calling connected.

    2018-08-09 04:38:02,896 DEBUG zen.ZenDisc: fetching monitor properties

    2018-08-09 04:38:02,943 DEBUG zen.ZenDisc: Getting threshold classes...

    2018-08-09 04:38:02,983 DEBUG zen.ZenDisc: Loading classes ['Products.ZenModel.MinMaxThreshold', 'Products.ZenModel.ValueChangeThreshold']

    2018-08-09 04:38:02,984 DEBUG zen.ZenDisc: Fetching default RRDCreateCommand...

    2018-08-09 04:38:02,987 DEBUG zen.ZenDisc: Getting collector thresholds...

    2018-08-09 04:38:03,025 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))

    2018-08-09 04:38:03,025 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))

    2018-08-09 04:38:03,025 DEBUG zen.ZenDisc: Getting collector plugins for each DeviceClass

    2018-08-09 04:38:03,063 INFO zen.ZenDisc: Looking for enlogin4.en.desres.deshaw.com

    2018-08-09 04:38:03,063 DEBUG zen.ZenDisc: getHostByName

    2018-08-09 04:38:03,066 DEBUG zen.ZenDisc: Found IP 10.232.55.14 for device enlogin4.en.desres.deshaw.com

    2018-08-09 04:38:03,074 DEBUG zen.ZenDisc: Scanning device with address 10.232.55.14

    2018-08-09 04:38:03,074 DEBUG zen.ZenDisc: findRemoteDeviceInfo.inner: Doing SNMP lookup on device 10.232.55.14

    2018-08-09 04:38:03,086 ERROR zen.ZenDisc: Failed device discovery for '10.232.55.14'

    Traceback (most recent call last):

      File "/opt/zenoss/Products/DataCollector/zendisc.py", line 456, in inner

        snmp_config = driver.next()

      File "/opt/zenoss/Products/ZenUtils/Driver.py", line 63, in result

        raise ex

    RemoteException: : Traceback (most recent call last):

      File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 85, in inner

        return callable(*args, **kw)

      File "/opt/zenoss/Products/ZenHub/services/DiscoverService.py", line 253, in remote_getSnmpConfig

        devroot = self.dmd.Devices.createOrganizer(devicePath)

      File "/opt/zenoss/Products/ZenModel/Organizer.py", line 341, in createOrganizer

        path,self.__class__)

      File "/opt/zenoss/Products/ZenModel/ZenModelBase.py", line 456, in createHierarchyObj

        return createHierarchyObj(root, name, factory, relpath, alog)

      File "/opt/zenoss/Products/ZenUtils/Utils.py", line 618, in createHierarchyObj

        root._setObject(id, newobj)

      File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 128, in _setObject

        self.addRelation(object)

      File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 118, in addRelation

        ToManyRelationshipBase.addRelation(self, obj)

      File "/opt/zenoss/Products/ZenRelations/RelationshipBase.py", line 91, in addRelation

        obj.id, obj.__class__.__name__))

    ZenSchemaError: devices restricted to class Device. enlogin4.en.desres.deshaw.com is class DeviceClass

    : <no traceback>: <no traceback>

    2018-08-09 04:38:03,087 DEBUG zen.ZenDisc: Finished scanning device with address 10.232.55.14

    2018-08-09 04:38:03,087 INFO zen.ZenDisc: Result: Discovered device enlogin4.en.desres.deshaw.com.

    2018-08-09 04:38:03,087 DEBUG zen.ZenDisc: Starting collector loop...

    2018-08-09 04:38:03,087 DEBUG zen.ZenDisc: Running 0 clients

    2018-08-09 04:38:03,087 INFO zen.ZenDisc: Scan time: 0.00 seconds

    2018-08-09 04:38:03,088 DEBUG zen.collector.scheduler: In shutdown stage before

    2018-08-09 04:38:03,088 DEBUG zen.ZenDisc: Tried to stop reactor that was stopped

    2018-08-09 04:38:03,088 INFO zen.ZenDisc: Daemon ZenDisc shutting down

    2018-08-09 04:38:03,089 DEBUG zen.ZenDisc: Removing service EventService

    2018-08-09 04:38:03,089 DEBUG zen.ZenDisc: Removing service DiscoverService

    2018-08-09 04:38:03,089 DEBUG zen.pbclientfactory: Lost connection to 127.0.0.1:8789 - [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.

    ]

    2018-08-09 04:38:03,090 DEBUG zen.collector.scheduler: In shutdown stage during

    2018-08-09 04:38:03,090 DEBUG zen.collector.scheduler: In shutdown stage after



    ------------------------------
    Amit Kshirsagar
    CompanyName
    ------------------------------


  • 2.  RE: not able to add devices using zendisc command

    Posted 08-10-2018 03:49 AM
    You are saying to create the newly discovered device in the deviceClass /Server/Linux/enlogin  - /opt/zenoss/bin/zendisc run -v 10 --now -d enlogin4.en.desres.deshaw.com --monitor localhost --deviceclass /Server/Linux/enlogin --prod_state 1000 - but, looking at the log, I suspect that deviceClass does not exist.  Try creating the class first using the GUI and then rerun your discovery.

    Cheers,
    Jane

    ------------------------------
    Jane Curry
    Skills 1st United Kingdom
    jane.curry@skills-1st.co.uk
    ------------------------------



  • 3.  RE: not able to add devices using zendisc command

    Posted 08-10-2018 04:27 AM
    Hi Jane,

    The device class is there and I am able to add the devices using GUI. These are the logs:

    2018-08-10 02:03:52,273 INFO zen.Job: Job ed5c54bb-b871-40d7-86f3-cec6930d91f7 (Products.ZenModel.ZDeviceLoader.DeviceCreationJob) received
    2018-08-10 02:03:52,286 INFO zen.Job: Beginning job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob
    2018-08-10 02:03:52,828 INFO zen.Job: Running Job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob
    2018-08-10 02:03:52,828 INFO zen.Job: Spawning subprocess: /opt/zenoss/bin/zendisc run --now -d enlogin4.en.desres.deshaw.com --monitor localhost --deviceclass /Server/Linux/enlogin --prod_state 1000 --job ed5c54bb-b871-40d7-86f3-cec6930d91f7
    2018-08-10 02:03:56,069 INFO zen.ZenDisc: Connecting to localhost:8789
    2018-08-10 02:03:56,076 INFO zen.ZenDisc: Connected to ZenHub
    2018-08-10 02:03:56,273 INFO zen.ZenDisc: Looking for enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,499 INFO zen.ZenDisc: Result: Discovered device enlogin4.en.desres.deshaw.com.
    2018-08-10 02:03:57,622 INFO zen.ZenDisc: No WMI plugins found for enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,624 INFO zen.ZenDisc: No Python plugins found for enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,626 INFO zen.ZenDisc: No command plugins found for enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,629 INFO zen.ZenDisc: SNMP collection device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,629 INFO zen.ZenDisc: plugins: zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap, HPDeviceMap, DellDeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap, zenoss.snmp.IpServiceMap, zenoss.snmp.HRFileSystemMap, zenoss.snmp.HRSWRunMap, zenoss.snmp.CpuMap, HPCPUMap, DellCPUMap, DellPCIMap
    2018-08-10 02:03:57,632 INFO zen.ZenDisc: No portscan plugins found for enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,760 INFO zen.SnmpClient: snmp client finished collection for enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,760 INFO zen.ZenDisc: Processing zenoss.snmp.NewDeviceMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,760 INFO zen.ZenDisc: processing zenoss.snmp.DeviceMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,761 INFO zen.ZenDisc: processing HPDeviceMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,761 INFO zen.ZenDisc: processing DellDeviceMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,761 INFO zen.ZenDisc: Modeler zenoss.snmp.InterfaceMap processing data for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,762 INFO zen.ZenDisc: processing zenoss.snmp.RouteMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,763 INFO zen.ZenDisc: processing zenoss.snmp.IpServiceMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,763 INFO zen.ZenDisc: Modeler zenoss.snmp.HRFileSystemMap processing data for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,763 INFO zen.ZenDisc: Skipping Swap space (virtualMemory) as it matches zFileSystemMapIgnoreTypes.
    2018-08-10 02:03:57,764 INFO zen.ZenDisc: Skipping Physical memory (ram) as it matches zFileSystemMapIgnoreTypes.
    2018-08-10 02:03:57,764 INFO zen.ZenDisc: Skipping Cached memory (other) as it matches zFileSystemMapIgnoreTypes.
    2018-08-10 02:03:57,764 INFO zen.ZenDisc: Skipping Memory buffers (other) as it matches zFileSystemMapIgnoreTypes.
    2018-08-10 02:03:57,764 INFO zen.ZenDisc: Skipping Shared memory (other) as it matches zFileSystemMapIgnoreTypes.
    2018-08-10 02:03:57,765 INFO zen.ZenDisc: HRSWRunMap Processing zenoss.snmp.HRSWRunMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,771 INFO zen.ZenDisc: processing zenoss.snmp.CpuMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,771 INFO zen.ZenDisc: processing HPCPUMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,772 INFO zen.ZenDisc: processing DellCPUMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:03:57,772 INFO zen.ZenDisc: processing DellPCIMap for device enlogin4.en.desres.deshaw.com
    2018-08-10 02:04:02,565 INFO zen.ZenDisc: Changes in configuration applied
    2018-08-10 02:04:02,565 INFO zen.ZenDisc: Scan time: 5.07 seconds
    2018-08-10 02:04:02,566 INFO zen.ZenDisc: Daemon ZenDisc shutting down
    2018-08-10 02:04:02,961 INFO zen.Job: Job ed5c54bb-b871-40d7-86f3-cec6930d91f7 Finished with result 0
    2018-08-10 02:04:02,973 INFO zen.Job: Job ed5c54bb-b871-40d7-86f3-cec6930d91f7 finished with result 0


    But the when I use the command zendisc, it is failing. Very strange.

    [zenoss@enzenoss1 ~]$ /opt/zenoss/bin/zendisc run --now -d enlogin6.en.desres.deshaw.com --monitor localhost --deviceclass /Server/Linux/enlogin --prod_state 1000
    2018-08-10 05:16:25,542 INFO zen.ZenDisc: Connecting to localhost:8789
    2018-08-10 05:16:25,547 INFO zen.ZenDisc: Connected to ZenHub
    2018-08-10 05:16:25,686 INFO zen.ZenDisc: Looking for enlogin6.en.desres.deshaw.com
    2018-08-10 05:16:25,707 ERROR zen.ZenDisc: Failed device discovery for '10.232.55.16'
    Traceback (most recent call last):
    File "/opt/zenoss/Products/DataCollector/zendisc.py", line 456, in inner
    snmp_config = driver.next()
    File "/opt/zenoss/Products/ZenUtils/Driver.py", line 63, in result
    raise ex
    RemoteException: : Traceback (most recent call last):
    File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 85, in inner
    return callable(*args, **kw)
    File "/opt/zenoss/Products/ZenHub/services/DiscoverService.py", line 253, in remote_getSnmpConfig
    devroot = self.dmd.Devices.createOrganizer(devicePath)
    File "/opt/zenoss/Products/ZenModel/Organizer.py", line 341, in createOrganizer
    path,self.__class__)
    File "/opt/zenoss/Products/ZenModel/ZenModelBase.py", line 456, in createHierarchyObj
    return createHierarchyObj(root, name, factory, relpath, alog)
    File "/opt/zenoss/Products/ZenUtils/Utils.py", line 618, in createHierarchyObj
    root._setObject(id, newobj)
    File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 128, in _setObject
    self.addRelation(object)
    File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 118, in addRelation
    ToManyRelationshipBase.addRelation(self, obj)
    File "/opt/zenoss/Products/ZenRelations/RelationshipBase.py", line 91, in addRelation
    obj.id, obj.__class__.__name__))
    ZenSchemaError: devices restricted to class Device. enlogin6.en.desres.deshaw.com is class DeviceClass
    : <no traceback>: <no traceback>
    2018-08-10 05:16:25,708 INFO zen.ZenDisc: Result: Discovered device enlogin6.en.desres.deshaw.com.
    2018-08-10 05:16:25,708 INFO zen.ZenDisc: Scan time: 0.00 seconds
    2018-08-10 05:16:25,709 INFO zen.ZenDisc: Daemon ZenDisc shutting down
    [zenoss@enzenoss1 ~]$ less "/opt/zenoss/Products/DataCollector/zendisc.py"


    I wonder why it is failing here?

    2018-08-10 05:16:25,707 ERROR zen.ZenDisc: Failed device discovery for '10.232.55.16'

    ------------------------------
    Amit Kshirsagar
    CompanyName
    ------------------------------



  • 4.  RE: not able to add devices using zendisc command

    Posted 08-10-2018 04:55 AM
    Hmm...this issue was reported back in 2014  ... https://pastebin.com/BmnYb5aF

    ------------------------------
    Amit Kshirsagar
    CompanyName
    ------------------------------



  • 5.  RE: not able to add devices using zendisc command

    Posted 08-13-2018 05:34 AM
    Hmm - still looks like the deviceclass that is causing an issue.  What happens if, with the command line zendisc, you leave off the deviceclass parameter?  By default, it will go in the /Discovered device class.  Appreciate that you probably want to control this but it would help narrow down the problem.

    Cheers,
    Jane

    ------------------------------
    Jane Curry
    Skills 1st United Kingdom
    jane.curry@skills-1st.co.uk
    ------------------------------



  • 6.  RE: not able to add devices using zendisc command

    Posted 08-13-2018 05:35 AM
    What version of Zenoss are you on here?

    Cheers,
    Jane

    ------------------------------
    Jane Curry
    Skills 1st United Kingdom
    jane.curry@skills-1st.co.uk
    ------------------------------



  • 7.  RE: not able to add devices using zendisc command

    Posted 08-13-2018 09:17 AM
    same error when the command is run without --deviceclass option.

    I am using zenoss core 4.2.5

    [zenoss@enzenoss1 log]$ zendisc run -v 10 --now --monitor localhost -d enlogin6.en.desres.deshaw.com
    2018-08-13 10:14:49,232 DEBUG zen.ZenDisc: Run in foreground, starting immediately.
    2018-08-13 10:14:49,237 DEBUG zen.pysamba: client ntlmv2 auth is now no
    2018-08-13 10:14:49,237 DEBUG zen.ZenDisc: Starting PBDaemon initialization
    2018-08-13 10:14:49,237 INFO zen.ZenDisc: Connecting to localhost:8789
    2018-08-13 10:14:49,240 DEBUG zen.pbclientfactory: Starting connection...
    2018-08-13 10:14:49,240 DEBUG zen.ZenDisc: Logging in as admin
    2018-08-13 10:14:49,241 DEBUG zen.pbclientfactory: Connected
    2018-08-13 10:14:49,241 DEBUG zen.pbclientfactory: Cancelling connect timeout
    2018-08-13 10:14:49,241 DEBUG zen.pbclientfactory: Sending credentials
    2018-08-13 10:14:49,243 DEBUG zen.pbclientfactory: Cancelling connect timeout
    2018-08-13 10:14:49,243 INFO zen.ZenDisc: Connected to ZenHub
    2018-08-13 10:14:49,243 DEBUG zen.ZenDisc: Setting up initial services: EventService, DiscoverService
    2018-08-13 10:14:49,243 DEBUG zen.ZenDisc: Chaining getInitialServices with d2
    2018-08-13 10:14:49,244 DEBUG zen.ZenDisc: Loaded service EventService from zenhub
    2018-08-13 10:14:49,244 DEBUG zen.ZenDisc: Loaded service DiscoverService from zenhub
    2018-08-13 10:14:49,244 DEBUG zen.ZenDisc: Queued event (total of 1) {'rcvtime': 1534169689.244842, 'severity': 0, 'component': 'zendisc', 'agent': 'zendisc', 'summary': 'started', 'manager': 'enzenoss1.en.desres.deshaw.com', 'device': 'localhost', 'eventClass': '/App/Start', 'monitor': 'localhost'}
    2018-08-13 10:14:49,245 DEBUG zen.ZenDisc: Sending 1 events, 0 perf events, 0 heartbeats
    2018-08-13 10:14:49,245 DEBUG zen.ZenDisc: Calling connected.
    2018-08-13 10:14:49,245 DEBUG zen.ZenDisc: fetching monitor properties
    2018-08-13 10:14:49,295 DEBUG zen.ZenDisc: Getting threshold classes...
    2018-08-13 10:14:49,307 DEBUG zen.ZenDisc: Loading classes ['Products.ZenModel.MinMaxThreshold', 'Products.ZenModel.ValueChangeThreshold']
    2018-08-13 10:14:49,308 DEBUG zen.ZenDisc: Fetching default RRDCreateCommand...
    2018-08-13 10:14:49,315 DEBUG zen.ZenDisc: Getting collector thresholds...
    2018-08-13 10:14:49,391 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))
    2018-08-13 10:14:49,391 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))
    2018-08-13 10:14:49,391 DEBUG zen.ZenDisc: Getting collector plugins for each DeviceClass
    2018-08-13 10:14:49,431 INFO zen.ZenDisc: Looking for enlogin6.en.desres.deshaw.com
    2018-08-13 10:14:49,431 DEBUG zen.ZenDisc: getHostByName
    2018-08-13 10:14:49,434 DEBUG zen.ZenDisc: Found IP 10.232.55.16 for device enlogin6.en.desres.deshaw.com
    2018-08-13 10:14:49,445 DEBUG zen.ZenDisc: Scanning device with address 10.232.55.16
    2018-08-13 10:14:49,446 DEBUG zen.ZenDisc: findRemoteDeviceInfo.inner: Doing SNMP lookup on device 10.232.55.16
    2018-08-13 10:14:49,461 ERROR zen.ZenDisc: Failed device discovery for '10.232.55.16'
    Traceback (most recent call last):
    File "/opt/zenoss/Products/DataCollector/zendisc.py", line 456, in inner
    snmp_config = driver.next()
    File "/opt/zenoss/Products/ZenUtils/Driver.py", line 63, in result
    raise ex
    RemoteException: : Traceback (most recent call last):
    File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 85, in inner
    return callable(*args, **kw)
    File "/opt/zenoss/Products/ZenHub/services/DiscoverService.py", line 253, in remote_getSnmpConfig
    devroot = self.dmd.Devices.createOrganizer(devicePath)
    File "/opt/zenoss/Products/ZenModel/Organizer.py", line 341, in createOrganizer
    path,self.__class__)
    File "/opt/zenoss/Products/ZenModel/ZenModelBase.py", line 456, in createHierarchyObj
    return createHierarchyObj(root, name, factory, relpath, alog)
    File "/opt/zenoss/Products/ZenUtils/Utils.py", line 618, in createHierarchyObj
    root._setObject(id, newobj)
    File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 128, in _setObject
    self.addRelation(object)
    File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 118, in addRelation
    ToManyRelationshipBase.addRelation(self, obj)
    File "/opt/zenoss/Products/ZenRelations/RelationshipBase.py", line 91, in addRelation
    obj.id, obj.__class__.__name__))
    ZenSchemaError: devices restricted to class Device. enlogin6.en.desres.deshaw.com is class DeviceClass
    : <no traceback>: <no traceback>
    2018-08-13 10:14:49,464 DEBUG zen.ZenDisc: Finished scanning device with address 10.232.55.16
    2018-08-13 10:14:49,464 INFO zen.ZenDisc: Result: Discovered device enlogin6.en.desres.deshaw.com.
    2018-08-13 10:14:49,464 DEBUG zen.ZenDisc: Starting collector loop...
    2018-08-13 10:14:49,465 DEBUG zen.ZenDisc: Running 0 clients
    2018-08-13 10:14:49,465 INFO zen.ZenDisc: Scan time: 0.00 seconds
    2018-08-13 10:14:49,470 DEBUG zen.collector.scheduler: In shutdown stage before
    2018-08-13 10:14:49,470 DEBUG zen.ZenDisc: Tried to stop reactor that was stopped
    2018-08-13 10:14:49,470 INFO zen.ZenDisc: Daemon ZenDisc shutting down
    2018-08-13 10:14:49,472 DEBUG zen.ZenDisc: Removing service EventService
    2018-08-13 10:14:49,472 DEBUG zen.ZenDisc: Removing service DiscoverService
    2018-08-13 10:14:49,472 DEBUG zen.pbclientfactory: Lost connection to 127.0.0.1:8789 - [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
    ]
    2018-08-13 10:14:49,472 DEBUG zen.collector.scheduler: In shutdown stage during
    2018-08-13 10:14:49,472 DEBUG zen.collector.scheduler: In shutdown stage after

    ------------------------------
    Amit Kshirsagar
    CompanyName
    ------------------------------



  • 8.  RE: not able to add devices using zendisc command

    Posted 08-14-2018 12:42 AM
    we have couple of other instances of zenoss core 4.2.5 running and I tested on it too. Same error. So this is not specific to that particular node.
    I am digging more ...will update here if I find something.

    2018-08-14 01:40:04,995 DEBUG zen.ZenDisc: getHostByName
    2018-08-14 01:40:05,025 ERROR zen.ZenDisc: Error: [Failure instance: Traceback (failure with no frames): <class 'Products.ZenModel.Exceptions.NoIPAddress'>: No IP found for name dhmlogin1.en.desres.deshaw.com
    ]

    ------------------------------
    Amit Kshirsagar
    CompanyName
    ------------------------------