I'm seeing this as well. Here are a couple of tests I ran from the zenoss server:
Code: [EMAIL PROTECTED] etc]$ time wmic -U domain/user%passwd //server "SELECT RegisteredUser FROM Win32_OperatingSystem" CLASS: Win32_OperatingSystem Name|RegisteredUser Microsoft Windows Server 2003 Standard Edition|C:\WINDOWS|\Device\Harddisk0\Partition1|James Madison University real 0m18.250s user 0m0.000s sys 0m0.000s It takes 18 seconds to query one property in one WMI class. I repeated this test multiple times and it never happened in less than 18 seconds. Contrast this with a test I did in PowerShell from a Windows desktop (querying the same server): Code: PS C:\Windows\System32> date ;; gwmi -Class "Win32_OperatingSystem" -Property RegisteredUser -ComputerName hbatch1 | select RegisteredUser ;; date Mon Jun 30 17:30:21 Eastern Daylight Time 2008 RegisteredUser -------------- James Madison University Mon Jun 30 17:30:21 Eastern Daylight Time 2008 If you look at the output of the two 'date' commands surrounding the query you'll notice it returned in less than a second. I'm thinking something's broken in this latest build of wmic--which would explain all the timeouts for zeneventlog and possibly zenwin as well (in fact, anywhere that wmic is used). FYI: I tested the above commands against multiple Windows servers and with multiple WMI queries. Also, it even takes 18 seconds to tell me that it couldn't find a certain property (spelled one wrong the first time)....for what that's worth. --seth -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21998#21998 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
