TECHZEN Zenoss User Community ARCHIVE  

Problem while executing plugin zenoss.winrm.Software

Subject: Problem while executing plugin zenoss.winrm.Software
Author: Paul Giordano
Posted: 2018-08-23 11:12

I'm getting this traceback on a remodel. It's a new device, Windows 2008 R2. This doesn't happen anywhere else. Anyone see this before or have any ideas?
2018-08-23 15:09:22,011 INFO zen.ZenModeler: Connecting to localhost:8789
2018-08-23 15:09:22,038 INFO zen.ZenModeler: Connected to the zenhub/0 instance
2018-08-23 15:09:22,040 INFO zen.ZenModeler: Getting configuration from ZenHub...
2018-08-23 15:09:22,260 INFO zen.ZenModeler: Starting modeling in 0 seconds.
2018-08-23 15:09:22,261 INFO zen.ZenModeler: Starting collector loop #001...
2018-08-23 15:09:22,261 INFO zen.ZenModeler: Collecting for device fufwdap01.zethcon.com
2018-08-23 15:09:22,261 INFO zen.ZenModeler: Got 1 devices to be scanned during collector loop #001
2018-08-23 15:09:22,379 INFO zen.ZenModeler: Filled collection slots for 1 of 1 devices during collector loop #001
2018-08-23 15:09:22,380 INFO zen.ZenModeler: skipping WMI-based collection, PySamba zenpack not installed
2018-08-23 15:09:22,380 INFO zen.ZenModeler: Collect on device fufwdap01.zethcon.com for collector loop #001
2018-08-23 15:09:22,387 INFO zen.ZenModeler: Python collection device fufwdap01.zethcon.com
2018-08-23 15:09:22,387 INFO zen.ZenModeler: plugins: zenoss.winrm.OperatingSystem, zenoss.winrm.CPUs, zenoss.winrm.FileSystems, zenoss.winrm.Interfaces, zenoss.winrm.Services, zenoss.winrm.Processes, zenoss.winrm.Software, zenoss.winrm.HardDisks
2018-08-23 15:09:22,394 INFO zen.ZenModeler: No command plugins found for fufwdap01.zethcon.com
2018-08-23 15:09:22,395 INFO zen.ZenModeler: SNMP monitoring off for fufwdap01.zethcon.com
2018-08-23 15:09:22,395 INFO zen.ZenModeler: No portscan plugins found for fufwdap01.zethcon.com
2018-08-23 15:09:52,013 INFO zen.ZenModeler: Counter eventCount, value 8
2018-08-23 15:10:09,396 INFO zen.PythonClient: Python client finished collection for fufwdap01.zethcon.com
2018-08-23 15:10:09,397 INFO zen.ZenModeler: Modeler zenoss.winrm.Software processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,404 ERROR zen.ZenModeler: Problem while executing plugin zenoss.winrm.Software
2018-08-23 15:10:09,406 ERROR zen.ZenModeler: Traceback (most recent call last):
File "/opt/zenoss/Products/DataCollector/zenmodeler.py", line 669, in processClient
datamaps = plugin.process(device, results, self.log)
File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.Microsoft.Windows-2.9.0.egg/ZenPacks/zenoss/Microsoft/Windows/utils.py", line 498, in dumper
return f(self, *args, **kwargs)
File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.Microsoft.Windows-2.9.0.egg/ZenPacks/zenoss/Microsoft/Windows/modeler/plugins/zenoss/winrm/Software.py", line 97, in process
installDate = DateTime(softwareDict['InstallDate'])
File "/opt/zenoss/lib/python2.7/site-packages/DateTime/DateTime.py", line 351, in __init__
return self._parse_args(*args, **kw)
File "/opt/zenoss/lib/python2.7/site-packages/DateTime/DateTime.py", line 653, in _parse_args
raise DateError, 'Invalid date: %s' % arg
DateError: Invalid date: 201889
2018-08-23 15:10:09,406 INFO zen.ZenModeler: Modeler zenoss.winrm.Services processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,413 INFO zen.ZenModeler: Modeler zenoss.winrm.CPUs processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,414 INFO zen.ZenModeler: Modeler zenoss.winrm.Processes processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,932 INFO zen.ZenModeler: Modeler zenoss.winrm.FileSystems processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,932 INFO zen.ZenModeler: Ignoring D: on fufwdap01.zethcon.com because it matches zFileSystemMapIgnoreTypes
2018-08-23 15:10:09,933 INFO zen.ZenModeler: Modeler zenoss.winrm.OperatingSystem processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,935 INFO zen.ZenModeler: Modeler zenoss.winrm.HardDisks processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:09,935 INFO zen.ZenModeler: Modeler zenoss.winrm.Interfaces processing data for device fufwdap01.zethcon.com
2018-08-23 15:10:19,143 INFO zen.ZenModeler: Changes in configuration applied
2018-08-23 15:10:19,144 INFO zen.ZenModeler: Finished processing client within collector loop #001
2018-08-23 15:10:19,144 INFO zen.ZenModeler: Scan time: 56.88 seconds for collector loop #001
2018-08-23 15:10:19,144 INFO zen.ZenModeler: Scanned 1 of 1 devices during collector loop #001

2018-08-23 15:10:19,146 INFO zen.ZenModeler: Daemon ZenModeler shutting down



------------------------------
Paul Giordano
Senior Systems Engineer
Zethcon Corporation
------------------------------


Subject: RE: Problem while executing plugin zenoss.winrm.Software
Author: Jason Olson
Posted: 2018-08-23 17:07

Does the user that Zenoss uses to connect to the server use the US regional settings? We had a similar issue, and had to log in *as* that user on the server, change the regional settings for that user to US and US English. The modeling worked after that.

------------------------------
Jason Olson
------------------------------


Subject: RE: Problem while executing plugin zenoss.winrm.Software
Author: Paul Giordano
Posted: 2018-09-06 16:00

Sounded like a good check, but the user we connect with is set up for USA English regional settings. Really stumped, this isn't any different than the other 40-some servers we're monitoring.

------------------------------
Paul Giordano
Senior Systems Engineer
Zethcon Corporation
------------------------------


Subject: RE: Problem while executing plugin zenoss.winrm.Software
Author: Jason Olson
Posted: 2018-09-11 10:39

How about the server itself? That error looks for all the world like an issue with the regional settings somewhere on the system, and Zenoss has a real problem with servers that aren't US English both in regional settings and language.

------------------------------
Jason Olson
------------------------------


Subject: RE: Problem while executing plugin zenoss.winrm.Software
Author: Paul Giordano
Posted: 2018-09-18 09:55

So I ended up searching the windows registry on the machines in question, and found a bad install date on one of the printer drivers. I corrected that and all is well. Kind of a goofy way around it, but it works.

------------------------------
Paul Giordano
Senior Systems Engineer
Zethcon Corporation
------------------------------


< Previous
Login page came_from parameter problems
  Next
heartbeat failure
>