Debugging the modeling process

You can run the modeler from the command line against a single device. This feature is useful when debugging issues with a plugin.

By passing the --collect command to the modeler, you can control which modeler plugins are used. For example, the following command runs only the interface plugin against the build.zenoss.loc device:

Log in to the Control Center host as a user with serviced CLI privileges.

Display the list of zenmodeler services.

serviced service list zenmodeler

On a system with multiple collectors, the result is similar to the following example:

Name            ServiceID                      DepID/Path
zenmodeler      7itut0ryz759ua77ntrm3hi8w      1/Zenoss.resmgr/Zenoss/Collection/localhost/localhost/zenmodeler
zenmodeler      e3bpfy6j6pyl8l346xq446myk      1/Zenoss.resmgr/Zenoss/Collection/localhost/collectorPool2/zenmodeler
zenmodeler      7dnmgcwexlqxjqko6nja0942y      1/Zenoss.resmgr/Zenoss/Collection/localhost/collectorPool3/zenmodeler

Select the zenmodeler service that is associated with the device to debug, and then attach to it as the zenoss user. Replace ServiceID with the container ID of a zenmodeler service. For example, 7itut0ryz759ua77ntrm3hi8w.
```
serviced service attach ServiceID su - zenoss
```

Run the zenmodeler command.

zenmodeler run -v10 --collect=IpInterface -d build.zenoss.loc

If the command returns any stack traces, forward the following details to Zenoss Support for assistance:

Command you ran
Stack trace or stack traces returned
Version of your Resource Manager instance
OS version and patch level for the remote device